I am having trouble deploying an application that uses Hibernate to a WebSphere 5.1.1 server. It was developed on WSAD 5.1 (Windows) and tested using the WebSphere test environment, which worked perfectly. But when I deploy it to the WebSphere server on AIX and run the app, I get the following problem:

InvocationTargetException:
Caused by: java.lang.VerifyError: (class: package/name/PersistentClassVO$$EnhancerByCGLIB$$7f0dd9cb, method: CGLIB$STATICHOOK1 signature: ()V) Inconsistent stack height 2 != 1

Has anyone seen anything like this before? I have been unable to recreate it on my development environment, and it is difficult to diagnose while running on the server.

I am using Hibernate 3.1.3, with CGLIB 2.1.3 and ASM 1.5.3 provided by the Hibernate distribution. I also tried switching to CGLIB 2.2-b1 and ASM 2.2.1, and got the same problem. The target deployment environment (where the problem occurs) is:

WebSphere 5.1.1 build a0426.01
J2RE 1.4.2 IBM AIX build ca142-20050929a (SR3) (JIT enabled: jitc)
AIX 5.3

Any advice would be appreciated!

Mike Clemens

Are you able to test it with a Sun JVM ? I'm making the presumption you are using an IBM one.

Can you confirm exactly which JVM implementation and version you are using within each environment, Live and Test ?

I have run it in test (Windows) with the Sun JDK 1.4.2_08-b03 and it also worked with that. And on the server, I am using J2RE 1.4.2 IBM AIX build ca142-20050929a (SR3) (JIT enabled: jitc) running on AIX 5.3.

I won't be able to change the JVM on the server, so in this case I'm stuck with an IBM JDK 1.4.x. I am able to adjust anything within the application, however, such as versions of Hibernate, CGLIB, ASM, etc.

thanks,
Mike Clemens.

Is there any other JVM vendor for AIX you could try. I've no idea what is available on that platform.

If the JVM is indeed the problem I'm sure IBM would be interested in a test case for the problem.

try to run it with -noverify option and try find better ASM version if it does not help (stack height is calculated by ASM library)

I added -noverify to the jvm startup and it is working on the integration server now. However, I also deployed the same app to the QA server, which I understand to be the identical configuration, and it worked there, without the -noverify option.

I understand that -noverify is just masking the problem, but based on my short-term circumstances, it at least allows the app to run there for the time being, and it should give our server team time to find the real problem, because clearly the problem isn't Hibernate or the app. And I'll try to switch in and out different versions of ASM as well.

Unfortunately, since I can only recreate this problem on our integration server, I get one shot a day to try to fix it before people start testing :)

Thanks for the help,

Mike Clemens.