Hugo Theme MemE

本地测试可以运行，但是环境上 mockito java.lang.VerifyError

 502  3 mins

问题描述

org.mockito.exceptions.base.MockitoException: 

Mockito cannot mock this class: class com.digiwin.athena.datamap.service.inner.DataMapPickService.

If you're not sure why you're getting this error, please open an issue on GitHub.


Java               : 1.8
JVM vendor name    : Oracle Corporation
JVM vendor version : 25.11-b03
JVM name           : Java HotSpot(TM) 64-Bit Server VM
JVM version        : 1.8.0_11-b12
JVM info           : mixed mode
OS name            : Mac OS X
OS version         : 10.16


You are seeing this disclaimer because Mockito is configured to create inlined mocks.
You can learn about inline mocks and their limitations under item #39 of the Mockito class javadoc.

Underlying exception : java.lang.IllegalArgumentException: Could not create type
Caused by: java.lang.IllegalArgumentException: Could not create type
Caused by: java.lang.VerifyError

一直报错，但是本地却没有。

调查过程

查询发现 Caused by: java.lang.VerifyError 可能是由于 jvm 验证到内存和class 可能不同，报出来的问题。

于是下载对应版本，本地复现，确实能复现该问题。

那么是哪个类不一致呢。

org.mockito.exceptions.base.MockitoException: 
Mockito cannot mock this class: class org.springframework.data.mongodb.core.MongoTemplate.

If you're not sure why you're getting this error, please open an issue on GitHub.


Java               : 1.8
JVM vendor name    : Oracle Corporation
JVM vendor version : 25.11-b03
JVM name           : Java HotSpot(TM) 64-Bit Server VM
JVM version        : 1.8.0_11-b12
JVM info           : mixed mode
OS name            : Mac OS X
OS version         : 10.16


You are seeing this disclaimer because Mockito is configured to create inlined mocks.
You can learn about inline mocks and their limitations under item #39 of the Mockito class javadoc.

Underlying exception : java.lang.IllegalArgumentException: Could not create type

	at org.mockito.junit.jupiter.MockitoExtension.beforeEach(MockitoExtension.java:153)
	at java.util.ArrayList.forEach(ArrayList.java:1234)
	at java.util.ArrayList.forEach(ArrayList.java:1234)
	Suppressed: java.lang.NullPointerException
		at org.mockito.junit.jupiter.MockitoExtension.afterEach(MockitoExtension.java:184)
		... 2 more
Caused by: java.lang.IllegalArgumentException: Could not create type
	at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:170)
	at net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:399)
	at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:190)
	at net.bytebuddy.TypeCache$WithInlineExpunction.findOrInsert(TypeCache.java:410)
	at org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.mockClass(TypeCachingBytecodeGenerator.java:40)
	at org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMockType(InlineDelegateByteBuddyMockMaker.java:396)
	at org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.doCreateMock(InlineDelegateByteBuddyMockMaker.java:355)
	at org.mockito.internal.creation.bytebuddy.InlineDelegateByteBuddyMockMaker.createMock(InlineDelegateByteBuddyMockMaker.java:334)
	at org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.createMock(InlineByteBuddyMockMaker.java:56)
	at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:99)
	at org.mockito.internal.MockitoCore.mock(MockitoCore.java:88)
	at org.mockito.Mockito.mock(Mockito.java:2037)
	at org.mockito.internal.configuration.MockAnnotationProcessor.processAnnotationForMock(MockAnnotationProcessor.java:74)
	at org.mockito.internal.configuration.MockAnnotationProcessor.process(MockAnnotationProcessor.java:28)
	at org.mockito.internal.configuration.MockAnnotationProcessor.process(MockAnnotationProcessor.java:25)
	at org.mockito.internal.configuration.IndependentAnnotationEngine.createMockFor(IndependentAnnotationEngine.java:44)
	at org.mockito.internal.configuration.IndependentAnnotationEngine.process(IndependentAnnotationEngine.java:72)
	at org.mockito.internal.configuration.InjectingAnnotationEngine.processIndependentAnnotations(InjectingAnnotationEngine.java:73)
	at org.mockito.internal.configuration.InjectingAnnotationEngine.process(InjectingAnnotationEngine.java:47)
	at org.mockito.MockitoAnnotations.openMocks(MockitoAnnotations.java:81)
	at org.mockito.internal.framework.DefaultMockitoSession.<init>(DefaultMockitoSession.java:43)
	at org.mockito.internal.session.DefaultMockitoSessionBuilder.startMocking(DefaultMockitoSessionBuilder.java:83)
	... 3 more
Caused by: java.lang.VerifyError
	at sun.instrument.InstrumentationImpl.retransformClasses0(Native Method)
	at sun.instrument.InstrumentationImpl.retransformClasses(InstrumentationImpl.java:144)
	at org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.triggerRetransformation(InlineBytecodeGenerator.java:280)
	at org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.mockClass(InlineBytecodeGenerator.java:217)
	at org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator.lambda$mockClass$0(TypeCachingBytecodeGenerator.java:47)
	at org.mockito.internal.creation.bytebuddy.TypeCachingBytecodeGenerator$$Lambda$342/1424439581.call(Unknown Source)
	at net.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
	... 24 more

debug 也没有太多的发现。

如果去掉这个依赖，就可以规避这个问题。

    <dependency>
      <groupId>org.mockito</groupId>
      <artifactId>mockito-inline</artifactId>
      <version>${mockito.version}</version>
      <scope>test</scope>
    </dependency>

在 mockito github 上也找到了类似的 issue

https://github.com/mockito/mockito/issues/2079

不过没有后续了。

我理解上应该是 mockito 会修改 class 对应的字节文件，但是这样的修改没能通过 jvm 的检测，但是如何拿到修改后的字节码文件呢。

暂时结论

先去掉 mockito-inline jar 包了，不用 mockStatic 方式。

定位起来这个问题比较麻烦，盲点比较多，mockito 框架可以进入我的待贡献清单了。

进一步定位

通过 ai 的帮忙，我试图找到 verifyError 的原因。 需要定位执行 mockito 前后的字节码差异。

需要利用 java agent 技术来获取执行后的文件字节码

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

package org.example;

import java.io.FileOutputStream;
import java.io.IOException;
import java.lang.instrument.ClassFileTransformer;
import java.lang.instrument.Instrumentation;
import java.security.ProtectionDomain;

public class BytecodeSaverAgent {

public static void premain(String agentArgs, Instrumentation inst) {
    inst.addTransformer(new ClassFileTransformer() {
        @Override
        public byte[] transform(ClassLoader loader, String className, Class<?> classBeingRedefined, ProtectionDomain protectionDomain, byte[] classfileBuffer) {
            if (className.equals("org/springframework/data/mongodb/core/MongoTemplate")) {
                try (FileOutputStream fos = new FileOutputStream("transformed_MongoTemplate.class")) {
                    fos.write(classfileBuffer);
                } catch (IOException e) {
                    e.printStackTrace();
                }
            }
            return classfileBuffer;
        }
    });
}

看起来是类加载时候会调用它。 于是我终于通过如下命令获取了对应的字节码

javap -c -p -v /Users/chenchuxin/Documents/dgw/data_map/datamap_backend/develop/transformed_MongoTemplate.class> MongoTemplate_bytecode_after.txt

diff 后发现没有什么不同啊。

 diff MongoTemplate_bytecode.txt MongoTemplate_bytecode_after.txt
1,2c1,2
< Classfile /Users/chenchuxin/.m2/repository/org/springframework/data/spring-data-mongodb/2.0.6.RELEASE/spring-data-mongodb-2.0.6.RELEASE/org/springframework/data/mongodb/core/MongoTemplate.class
<   Last modified 04-Apr-2018; size 105592 bytes
---
> Classfile /Users/chenchuxin/Documents/dgw/data_map/datamap_backend/develop/transformed_MongoTemplate.class
>   Last modified 07-Nov-2024; size 105592 bytes

通过进一步 debug 发现这个 agnet 打出来的类并不是转换之后的字节码文件。

算了，不太好搞了。

告一段落

这个问题确实比较棘手。一个时 mocktio 框架还不太了解细节。

二是定位字节码转换前后的差异比较麻烦。

不过定位过程比较有趣。 mocktio 和 agent 技术确实值得进一步了解。

updatedupdated2024-11-072024-11-07