openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <>
Subject [jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload
Date Thu, 28 Dec 2006 14:52:21 GMT
    [ ] 
Kevin Sutter commented on OPENJPA-91:

Not sure if this is the same problem or not, but we're hitting a similar problem when attempting
to re-load an application that has been modified.  Our problem exists with the WebSphere Feature
Pack v6.1 Alpha for EJB3/JPA (
 What we are finding is that the unloading of an application doesn't completely clean out
the directory structure where the jar files exist (due to locks not properly cleaned up).
 Then, when the application is re-installed, these jar files get overlayed, but it causes
some "corruption" that produces errors similar to the one posted.  Sometimes we get a jar
file corruption exception, sometimes we get a class loading error, and other similar exceptions
have been produced.

We will continue to pursue this problem, but resources are light at this time due to the holidays.
 A possible workaround is to re-start the application server.  This seems to release the locks
and allows the re-installation of the application possible.  Something to try anyway...


> 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