openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <>
Subject [jira] Closed: (OPENJPA-1093) Class not found warning in KODO 4.x
Date Mon, 18 May 2009 17:04:45 GMT


Michael Dick closed OPENJPA-1093.

    Resolution: Invalid

I don't think this is the right place to post your question. While Kodo and OpenJPA share
some implementation code the stack you've provided doesn't contain any openjpa code. Anything
we can say about it would be guesswork. 

You'll probably have more luck raising the issue with WebLogic support - they have access
to the source code for the kodo classes and can accurately diagnose the problem. 

Some current and former kodo developers are on the mailing lists though, so they might have
some guesses, but this doesn't appear to be an issue with OpenJPA. 

> Class not found warning in KODO 4.x
> -----------------------------------
>                 Key: OPENJPA-1093
>                 URL:
>             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
> pmf-config.xml
> ============
> <kodo-DataCache value="true(CacheSize=2000, SoftReferenceSize=0)"/> //if we remove
this line we dont get 													  //classnotfound exception warning
> package.jdo
> ============
> <class name="DemSummary" objectid-class="DemSummaryId">
>   <extension vendor-name="kodo" key="data-cache" value="false"/>
>   <field name="demSummaryId" primary-key="true"/>
> </class>
> 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: 
> java.lang.ClassNotFoundException:
> 		 at java.lang.Class.forName0(Native Method)
> 		 at java.lang.Class.forName(
> 		 at kodo.datacache.Caches.addTypesByName(
> 		 at kodo.datacache.AbstractQueryCache.afterCommit(
> 		 at kodo.event.RemoteCommitEventManager.fireEvent(
> 		 at com.solarmetric.util.AbstractEventManager.fireEvent(
> 		 at kodo.event.AbstractRemoteCommitProvider.fireEvent(
> 		 at kodo.event.SingleJVMRemoteCommitProvider.broadcast(
> 		 at kodo.event.RemoteCommitEventManager.afterCommit(
> 		 at kodo.event.TransactionEventManager.fireEvent(
> 		 at com.solarmetric.util.AbstractEventManager.fireEvent(
> 		 at kodo.kernel.BrokerImpl.endTransaction(
> 		 at kodo.kernel.BrokerImpl.afterCompletion(
> 		 at weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(
> 		 at weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(
> 		 at weblogic.transaction.internal.ServerTransactionImpl.afterCommittedStateHousekeeping(
> 		 at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(
> 		 at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(
> 		 at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(
> 		 at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(
> 		 at weblogic.transaction.internal.ServerTransactionImpl.commit(
> 		 at weblogic.ejb20.internal.MDListener.execute(
> 		 at weblogic.ejb20.internal.MDListener.transactionalOnMessage(
> 		 at weblogic.ejb20.internal.MDListener.onMessage(
> 		 at weblogic.jms.client.JMSSession.onMessage(
> 		 at weblogic.jms.client.JMSSession.execute(
> 		 at weblogic.kernel.ExecuteThread.execute(
> 		 at

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message