openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Prud'hommeaux (JIRA)" <>
Subject [jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload
Date Fri, 22 Dec 2006 20:10:21 GMT
    [ ] 
Marc Prud'hommeaux commented on OPENJPA-91:

It sounds like a number of other people have experienced this sort of error with various other
packages (see
). Sadly, there doesn't appear to be a resolution in there.

How are you deploying OpenJPA? Is it in the system classpath? If not, can you try putting
it in the system classpath and restarting Websphere, and see if it still happens?

> java.lang.VerifyError on websphere after application reload
> -----------------------------------------------------------
>                 Key: OPENJPA-91
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>         Environment: Using OpenJPA (openjpa-all-0.9.6-incubating.jar) in Rational Developer
7 ( Websphere 6.1 test environment ) connected to Oracle 9.2 database.
> OS: WinXP SP2
>            Reporter: Anders Monrad
>            Priority: Minor
> Hi ..
> Not sure if this is a bug or just the way websphere reacts to openjpa. 
> I have a small test program using OpenJPA against an Oracle database. I am running this
program in the Websphere 6.1 test environment included with Rational Developer 7. This is
all working just fine. But when I make changes to some ressource in the application, the chagnes
are automatically published to the test environment and the app is restarted. After this I
get the Exception below, whenever I try to access an EntityManager. 
> If I restart the entire server, the app is running fine again. So I guess this is related
to restarting the application.
> Caused by: java.lang.VerifyError: class loading constraint violated (class: org/apache/openjpa/kernel/BrokerImpl
method: newQueryImpl(Ljava/lang/String;Lorg/apache/openjpa/kernel/StoreQuery;)Lorg/apache/openjpa/kernel/QueryImpl;)
at pc: 0
> 	at java.lang.J9VMInternals.verifyImpl(Native Method)
> 	at java.lang.J9VMInternals.verify(
> 	at java.lang.J9VMInternals.initialize(
> 	at java.lang.Class.forNameImpl(Native Method)
> 	at java.lang.Class.forName(
> 	at org.apache.openjpa.conf.OpenJPAConfigurationImpl.class$(
> 	at org.apache.openjpa.conf.OpenJPAConfigurationImpl.<init>(
> 	at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.<init>(
> 	at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.<init>(
> 	at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.<init>(
> 	at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newInstance(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.apache.openjpa.kernel.Bootstrap.invokeFactory(
> 	at org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(
> 	at org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(
> 	at org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(
> 	at javax.persistence.Persistence.createEntityManagerFactory(
> 	at javax.persistence.Persistence.createEntityManagerFactory(
> 	at util.EntityManagerFactoryHelper.getEntityManagerFactory(

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message