Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2011-03-24T13:22:03Z by SystemAdmin
Inampudi
Inampudi
1 Post
ACCEPTED ANSWER

Pinned topic MQFTE V7.0.3 J2EE database logger exception on WebSphere AppServer V7

‏2011-03-23T16:21:27Z |
Hi

I have configured and deployed WMQFTE J2EE DB logger and started the application; soon after starting the application I am getting exception from JPA stack.
Is any one able to configure J2EE DB Logger and make it working? Thank in advance.
Arun

3/22/11 15:23:07:891 EDT 00000029 LocalExceptio E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "onMessage" on
bean "BeanId(WebSphere MQ File Transfer Edition database logger#*com.ibm.wmqfte.databaselogger.jee.ejb.jar*#DatabaseLoggerMDB, null)". Exception data: java.lan
g.IllegalStateException: Exception caught during message processing!
at com.ibm.wmqfte.databaselogger.jee.ejb.DatabaseLoggerMDB.onMessage(DatabaseLoggerMDB.java:286)
at com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod(MessageEndpointHandler.java:1092)
at com.ibm.ejs.container.MessageEndpointHandler.invoke(MessageEndpointHandler.java:777)
at $Proxy73.onMessage(Unknown Source)
at com.ibm.mq.connector.inbound.MessageEndpointWrapper.onMessage(MessageEndpointWrapper.java:131)
at com.ibm.mq.jms.MQSession$FacadeMessageListener.onMessage(MQSession.java:147)
at com.ibm.msg.client.jms.internal.JmsSessionImpl.run(JmsSessionImpl.java:2598)
at com.ibm.mq.jms.MQSession.run(MQSession.java:862)
at com.ibm.mq.connector.inbound.WorkImpl.run(WorkImpl.java:229)
at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
Caused by: <openjpa-1.2.2-SNAPSHOT-r422266:821449 fatal general error> org.apache.openjpa.persistence.PersistenceException: This operation failed for some in
stances. See the nested exceptions array for details.
at org.apache.openjpa.kernel.BrokerImpl.throwNestedExceptions(BrokerImpl.java:2352)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2051)
at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1909)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1680)
at org.apache.openjpa.kernel.DelegatingBroker.flush(DelegatingBroker.java:989)
at org.apache.openjpa.persistence.EntityManagerImpl.flush(EntityManagerImpl.java:592)
at com.ibm.ws.jpa.management.JPATxEmInvocation.flush(JPATxEmInvocation.java:243)
at com.ibm.ws.jpa.management.JPAEntityManager.flush(JPAEntityManager.java:211)
at com.ibm.wmqfte.databaselogger.jee.ejb.DatabaseLoggerMDB.onMessage(DatabaseLoggerMDB.java:270)
... 10 more
Caused by: <openjpa-1.2.2-SNAPSHOT-r422266:821449 nonfatal user error> org.apache.openjpa.persistence.ArgumentException: Attempt to assign id "com.ibm.wmqfte
.web.jpa.Metadata-0" to new instance "com.ibm.wmqfte.web.jpa.Metadata@20b420b4" failed; there is already an object in the L1 cache with this id. You must del
ete this object (in a previous transaction or the current one) before reusing its id. This error can also occur when a horizontally or vertically mapped cla
sses uses auto-increment application identity and does not use a hierarchy of application identity classes.
FailedObject: com.ibm.wmqfte.web.jpa.Metadata@20b420b4
at org.apache.openjpa.kernel.ManagedCache.assignObjectId(ManagedCache.java:193)
at org.apache.openjpa.kernel.BrokerImpl.assignObjectId(BrokerImpl.java:4744)
at org.apache.openjpa.kernel.BrokerImpl.setStateManager(BrokerImpl.java:3843)
at org.apache.openjpa.kernel.StateManagerImpl.assertObjectIdAssigned(StateManagerImpl.java:551)
at org.apache.openjpa.kernel.StateManagerImpl.afterFlush(StateManagerImpl.java:995)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2034)
... 17 more
Updated on 2011-03-24T13:22:03Z at 2011-03-24T13:22:03Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    64 Posts
    ACCEPTED ANSWER

    Re: MQFTE V7.0.3 J2EE database logger exception on WebSphere AppServer V7

    ‏2011-03-24T13:22:03Z  in response to Inampudi
    I've asked around and this looks very similar to an existing problem with WAS 7. You should raise a PMR with IBM Service and give this information to them. It may be the same problem as PM32318 - but I can't be certain.