[jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload
[ https://issues.apache.org/jira/browse/OPENJPA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487950 ] Patrick Linskey commented on OPENJPA-91: > Hi, Patrick, what kind of DB2 driver info we should put into the config? > DB2 connection pool driver class name? It depends on how you want the configuration to be structured. If you already have a data source defined within the application server, then you should provide its JNDI name. Otherwise, you can either provide direct connection URL / driver name / user credential information to OpenJPA, or provide a pooling data source configuration. > java.lang.VerifyError on websphere after application reload > --- > > Key: OPENJPA-91 > URL: https://issues.apache.org/jira/browse/OPENJPA-91 > 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 > Fix For: 0.9.8 > > > 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(J9VMInternals.java:59) > at java.lang.J9VMInternals.initialize(J9VMInternals.java:120) > at java.lang.Class.forNameImpl(Native Method) > at java.lang.Class.forName(Class.java:131) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.class$(OpenJPAConfigurationImpl.java:65) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:182) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:110) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:100) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:91) > at > org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newInstance(JDBCBrokerFactory.java:55) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:615) > at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:117) > at > org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:57) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:70) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:78) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60) > at > util.EntityManagerFactoryHelper.getEntityManagerFactory(EntityManagerFactoryHelper.java:22) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload
This has been commented on before. You need to rerun the Enhancer on any Entity classes that are re-published and stop and start WebSphere. It is best to turn off automatic publishing in WebSphere/RAD. You can still run it in debug mode under RAD and change anything other than Entities without needing to restart. I do this all the time. 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(J9VMInternals.java:59) at java.lang.J9VMInternals.initialize(J9VMInternals.java:120) at java.lang.Class.forNameImpl(Native Method) at java.lang.Class.forName(Class.java:131) at org.apache.openjpa.conf.OpenJPAConfigurationImpl.class$(OpenJPAConfigurationImpl.java:65) at org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:182) at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:110) at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:100) at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:91) at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newInstance(JDBCBrokerFactory.java:55) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:117) at org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:57) at org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:70) at org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:78) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60) at util.EntityManagerFactoryHelper.getEntityManagerFactory(EntityManagerFactoryHelper.java:22)
[jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload
[ https://issues.apache.org/jira/browse/OPENJPA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487819 ] david zhang commented on OPENJPA-91: Hi, Patrick, what kind of DB2 driver info we should put into the config? DB2 connection pool driver class name? > java.lang.VerifyError on websphere after application reload > --- > > Key: OPENJPA-91 > URL: https://issues.apache.org/jira/browse/OPENJPA-91 > 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 > Fix For: 0.9.8 > > > 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(J9VMInternals.java:59) > at java.lang.J9VMInternals.initialize(J9VMInternals.java:120) > at java.lang.Class.forNameImpl(Native Method) > at java.lang.Class.forName(Class.java:131) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.class$(OpenJPAConfigurationImpl.java:65) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:182) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:110) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:100) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:91) > at > org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newInstance(JDBCBrokerFactory.java:55) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:615) > at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:117) > at > org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:57) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:70) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:78) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60) > at > util.EntityManagerFactoryHelper.getEntityManagerFactory(EntityManagerFactoryHelper.java:22) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload
[ http://issues.apache.org/jira/browse/OPENJPA-91?page=comments#action_12461200 ] 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 (https://www14.software.ibm.com/iwm/web/cc/earlyprograms/websphere/was61ejb3/). 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... Kevin > java.lang.VerifyError on websphere after application reload > --- > > Key: OPENJPA-91 > URL: http://issues.apache.org/jira/browse/OPENJPA-91 > 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(J9VMInternals.java:59) > at java.lang.J9VMInternals.initialize(J9VMInternals.java:120) > at java.lang.Class.forNameImpl(Native Method) > at java.lang.Class.forName(Class.java:131) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.class$(OpenJPAConfigurationImpl.java:65) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:182) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:110) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:100) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:91) > at > org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newInstance(JDBCBrokerFactory.java:55) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:615) > at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:117) > at > org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:57) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:70) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:78) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60) > at > util.EntityManagerFactoryHelper.getEntityManagerFactory(EntityManagerFactoryHelper.java:22) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload
[ http://issues.apache.org/jira/browse/OPENJPA-91?page=comments#action_12460593 ] Igor Fedorenko commented on OPENJPA-91: --- Also, how do you configure database connection? Do you use WAS datasource or tell OpenJPA driver/connection details? In the latter case, are you using type2 or type4 driver (hint: switching to type4 might help). > java.lang.VerifyError on websphere after application reload > --- > > Key: OPENJPA-91 > URL: http://issues.apache.org/jira/browse/OPENJPA-91 > 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(J9VMInternals.java:59) > at java.lang.J9VMInternals.initialize(J9VMInternals.java:120) > at java.lang.Class.forNameImpl(Native Method) > at java.lang.Class.forName(Class.java:131) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.class$(OpenJPAConfigurationImpl.java:65) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:182) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:110) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:100) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:91) > at > org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newInstance(JDBCBrokerFactory.java:55) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:615) > at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:117) > at > org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:57) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:70) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:78) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60) > at > util.EntityManagerFactoryHelper.getEntityManagerFactory(EntityManagerFactoryHelper.java:22) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload
[ http://issues.apache.org/jira/browse/OPENJPA-91?page=comments#action_12460576 ] 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 http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?forum=275&thread=31014&cat=9 ). 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: http://issues.apache.org/jira/browse/OPENJPA-91 > 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(J9VMInternals.java:59) > at java.lang.J9VMInternals.initialize(J9VMInternals.java:120) > at java.lang.Class.forNameImpl(Native Method) > at java.lang.Class.forName(Class.java:131) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.class$(OpenJPAConfigurationImpl.java:65) > at > org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:182) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:110) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:100) > at > org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.(JDBCConfigurationImpl.java:91) > at > org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newInstance(JDBCBrokerFactory.java:55) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:615) > at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:117) > at > org.apache.openjpa.kernel.Bootstrap.newBrokerFactory(Bootstrap.java:57) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:70) > at > org.apache.openjpa.persistence.PersistenceProviderImpl.createEntityManagerFactory(PersistenceProviderImpl.java:78) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) > at > javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:60) > at > util.EntityManagerFactoryHelper.getEntityManagerFactory(EntityManagerFactoryHelper.java:22) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
