Help! I've been fighting a nasty VerifyError exception for the last day. I guess it has nothing to do with JBoss, but you guys have more experience than most!
I have code that used to run fine in a session bean under JBoss 3.0.0 alpha. I have now migrated to JBoss 3.0.0 RC3 and suddenly I get a very strange error. My guess is it has something to do with the java VM. I use Sun's 1.3 jdk version.
The weird thing is, that when I run the code in a small test program it works fine - no VerifyError. It looks as if it should have been caught by the compiler.
Has anyone seen this before? Does JBoss 3.0.0 use a different Java VM? Could it be happening because I'm running out of main memory?
2002-05-31 12:53:11,807 DEBUG [xcom.traxbahn.bproc.authsys.ejb.AuthorisationSystemBean] About to create Authorisation Response object
2002-05-31 12:53:11,807 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackException, causedBy:
java.lang.VerifyError: (class: xcom/traxbahn/util/messages/AuthorisationResponse, method: <init> signature: (Lxcom/traxbahn/util/messages/AuthorisationMsg;)V) Bad access to protected data
at xcom.traxbahn.bproc.authsys.ejb.AuthorisationSystemBean.handleMessage(AuthorisationSystemBean.java:150)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:664)
All advice appreciated,
Jonathan O'Connor
Ph: +353 1 872 3305
Mob: +353 86 824 9736
Fax: +353 1 873 3612
