Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 50793 invoked from network); 18 May 2009 15:43:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 May 2009 15:43:08 -0000 Received: (qmail 67580 invoked by uid 500); 18 May 2009 15:43:08 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 67554 invoked by uid 500); 18 May 2009 15:43:08 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 67544 invoked by uid 99); 18 May 2009 15:43:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2009 15:43:08 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 May 2009 15:43:06 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 26239234C044 for ; Mon, 18 May 2009 08:42:46 -0700 (PDT) Message-ID: <1775620219.1242661366155.JavaMail.jira@brutus> Date: Mon, 18 May 2009 08:42:46 -0700 (PDT) From: "Abinash Samal (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Created: (OPENJPA-1093) Class not found warning in KODO 4.x MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Class not found warning in KODO 4.x ----------------------------------- Key: OPENJPA-1093 URL: https://issues.apache.org/jira/browse/OPENJPA-1093 Project: OpenJPA Issue Type: Question Components: jpa Reporter: Abinash Samal Priority: Critical As part of migration from KODO3.x to KODO4.x, I am facing a kodo related issue. We are gettting a classnotfoundexception warning with the below settings, but if we remove the kodo-DataCache tag from pmf-config.xml it doesnt throw an classnotfoundexception warning pmf-config.xml ============ //if we remove this line we dont get //classnotfound exception warning package.jdo ============ Could any one please suggest why I am getting this KODO warning with above setting and why it doesnt throw this warning when I remove kodo-DataCache tag from pmf-config.xml. Below is the excerpt from the log which shows the warning of classnotfoundexception: log (Log4j) ======== [18/05/09 13:37:17] [] [WARN ][Log4JLogFactory$LogAdapter] java.lang.ClassNotFoundException: com.db.dcf.docs.dem.jdo.beans.DemSummary java.lang.ClassNotFoundException: com.db.dcf.docs.dem.jdo.beans.DemSummary at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:219) at kodo.datacache.Caches.addTypesByName(Caches.java:33) at kodo.datacache.AbstractQueryCache.afterCommit(AbstractQueryCache.java:211) at kodo.event.RemoteCommitEventManager.fireEvent(RemoteCommitEventManager.java:120) at com.solarmetric.util.AbstractEventManager.fireEvent(AbstractEventManager.java:109) at kodo.event.AbstractRemoteCommitProvider.fireEvent(AbstractRemoteCommitProvider.java:56) at kodo.event.SingleJVMRemoteCommitProvider.broadcast(SingleJVMRemoteCommitProvider.java:48) at kodo.event.RemoteCommitEventManager.afterCommit(RemoteCommitEventManager.java:135) at kodo.event.TransactionEventManager.fireEvent(TransactionEventManager.java:104) at com.solarmetric.util.AbstractEventManager.fireEvent(AbstractEventManager.java:109) at kodo.kernel.BrokerImpl.endTransaction(BrokerImpl.java:2560) at kodo.kernel.BrokerImpl.afterCompletion(BrokerImpl.java:2182) at weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(ServerSCInfo.java:887) at weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(ServerTransactionImpl.java:2765) at weblogic.transaction.internal.ServerTransactionImpl.afterCommittedStateHousekeeping(ServerTransactionImpl.java:2670) at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(ServerTransactionImpl.java:2702) at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2500) at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2429) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:262) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228) at weblogic.ejb20.internal.MDListener.execute(MDListener.java:430) at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:333) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:298) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2698) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2610) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.