Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 82860 invoked from network); 22 Dec 2006 21:07:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Dec 2006 21:07:42 -0000 Received: (qmail 88249 invoked by uid 500); 22 Dec 2006 21:07:50 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 88215 invoked by uid 500); 22 Dec 2006 21:07:49 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 88206 invoked by uid 99); 22 Dec 2006 21:07:49 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Dec 2006 13:07:49 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Dec 2006 13:07:41 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9D723714289 for ; Fri, 22 Dec 2006 13:07:21 -0800 (PST) Message-ID: <14512241.1166821641620.JavaMail.jira@brutus> Date: Fri, 22 Dec 2006 13:07:21 -0800 (PST) From: "Igor Fedorenko (JIRA)" To: open-jpa-dev@incubator.apache.org Subject: [jira] Commented: (OPENJPA-91) java.lang.VerifyError on websphere after application reload In-Reply-To: <13536552.1166789300978.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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