Distributed Environment - Exception during commit of transact

The Application is deployed in 3 machines (Win2K) in Weblogic 6.1 SP2 with Oracle
8i as the Database - Presentation EAR file in one machine, Business Logic EAR
file in second machine and Persistence EAR file in the third machine. The Database
is also in the third machine. Tx Datasource is configured in all the 3 weblogic
instances to point to the Database.
The application has a 'Save' operation in which case the EJB in the Business Logic
Layer connects to the Datasource of the Persistence Layer. The following error
is seen in the console of the second machine (Business Logic) while Saving.
<Error> <EJB> <Exception during commit of transact
ion Name=[EJB com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB.proc
ess(reefwork.bp.BusinessProcessEvent)],Xid=1:d4f44d847f28edb9(7225037),Status=Ro
lled back. [Reason=javax.transaction.SystemException: Aborting prepare because
s
ome resources could not be assigned],numRepliesOwedMe=0,numRepliesOwedOthers=0,s
econds since begin=1,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connec
tion]=(state=new,assigned=none),SCInfo[mydomain+myserver]=(state=rolledback),pro
perties=({weblogic.transaction.name=[EJB com.toontown.matchmaker.ejb.service.Bus
inessProcessGatewayEJB.process(reefwork.bp.BusinessProcessEvent)], weblogic.jdbc
=t3://130.10.11.30:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDesc
riptor=(CoordinatorURL=myserver+130.10.7.94:7001+mydomain+, Resources={})],Coord
inatorURL=myserver+130.10.7.94:7001+mydomain+): javax.transaction.SystemExceptio
n: Aborting prepare because some resources could not be assigned
at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:924)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1566)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:218)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl.process(BusinessProcessGatewayEJB_yd4d11_EOImpl.java:46)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Aborting prepare because some resources
could not be assigned - with nested exception:
[javax.transaction.SystemException: Aborting prepare because some resources coul
d not be assigned]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(
TransactionImpl.java:1475)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl.process(BusinessProcessGatewayEJB_yd4d11_EOImpl.java:46)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
Please note that 130.10.7.94 is the IP of Business Logic Layer and 130.10.11.30
is the IP of Persistence Layer.
Thanks!

Try changing the server name on either on persistence machine or business logic
machine
"Devika" <[email protected]> wrote:
>
>
The Application is deployed in 3 machines (Win2K) in Weblogic 6.1 SP2
with Oracle
8i as the Database - Presentation EAR file in one machine, Business Logic
EAR
file in second machine and Persistence EAR file in the third machine.
The Database
is also in the third machine. Tx Datasource is configured in all the
3 weblogic
instances to point to the Database.
The application has a 'Save' operation in which case the EJB in the Business
Logic
Layer connects to the Datasource of the Persistence Layer. The following
error
is seen in the console of the second machine (Business Logic) while Saving.
<Error> <EJB> <Exception during commit of transact
ion Name=[EJB com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB.proc
ess(reefwork.bp.BusinessProcessEvent)],Xid=1:d4f44d847f28edb9(7225037),Status=Ro
lled back. [Reason=javax.transaction.SystemException: Aborting prepare
because
s
ome resources could not be assigned],numRepliesOwedMe=0,numRepliesOwedOthers=0,s
econds since begin=1,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connec
tion]=(state=new,assigned=none),SCInfo[mydomain+myserver]=(state=rolledback),pro
perties=({weblogic.transaction.name=[EJB com.toontown.matchmaker.ejb.service.Bus
inessProcessGatewayEJB.process(reefwork.bp.BusinessProcessEvent)], weblogic.jdbc
=t3://130.10.11.30:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDesc
riptor=(CoordinatorURL=myserver+130.10.7.94:7001+mydomain+, Resources={})],Coord
inatorURL=myserver+130.10.7.94:7001+mydomain+): javax.transaction.SystemExceptio
n: Aborting prepare because some resources could not be assigned
at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:924)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1566)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:218)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl.process(BusinessProcessGatewayEJB_yd4d11_EOImpl.java:46)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Aborting prepare because some
resources
could not be assigned - with nested exception:
[javax.transaction.SystemException: Aborting prepare because some resources
coul
d not be assigned]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(
TransactionImpl.java:1475)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl.process(BusinessProcessGatewayEJB_yd4d11_EOImpl.java:46)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
Please note that 130.10.7.94 is the IP of Business Logic Layer and 130.10.11.30
is the IP of Persistence Layer.
Thanks!

Similar Messages

  • Exception during commit of transaction in wli when using oracle database

    I have configured oracle Database instead of pointbase in wli 9.2
    While getting the response through callback in wli process (from Worklist console)this errror is coming "Exception occurred during commit of transaction ".
    What should I do to remove this error??
    Stack trace is
    <Jan 6, 2007 5:19:59 PM CST> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transac
    tion Xid=BEA1-012806F477B49C8F6264(7312912),Status=Rolled back. [Reason=weblogic.utils.NestedRuntime
    Exception: Error in beforeCompletion],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=
    0,seconds left=60,XAServerResourceInfo[WLStore_oracle1domain_cgJMSStore]=(ServerResourceInfo[WLStore
    oracle1domaincgJMSStore]=(state=rolledback,assigned=AdminServer),xar=WLStore_oracle1domain_cgJMSSt
    ore1269044,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(Ser
    verResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=rolledback,assigned=AdminServer),xar
    =weblogic.jdbc.wrapper.JTSXAResourceImpl@14c0a31,re-Registered = false),SCInfo[oracle1domain+AdminSe
    rver]=(state=rolledback),properties=({weblogic.jdbc=t3://199.81.36.226:7001}),local properties=({mod
    ifiedListeners=[weblogic.ejb.container.internal.TxManager$TxListener@1442c7b], class com.bea.wli.bpm
    .runtime.JpdContainer$TxnListener1168125300187=com.bea.wli.bpm.runtime.JpdContainer$TxnListener@1313
    24d}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+199.8
    1.36.226:7001+oracle1domain+t3+, XAResources={WLStore_oracle1domain_cgJMSStore, WLStore_oracle1domai
    n_WseeFileStore, WLStore_oracle1domain__WLS_AdminServer, weblogic.jdbc.wrapper.JTSXAResourceImpl},No
    nXAResources={})],CoordinatorURL=AdminServer+199.81.36.226:7001+oracle1domain+t3+): weblogic.transac
    tion.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb.container.intern
    al.TxManager$TxListener@1442c7b
    Error in beforeCompletion
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java
    :1782)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.
    java:331)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:463)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
    at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:291)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:3953)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4467)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    .>

    Did you get a solution to this problem ?I am seeing similar exceptions intermittently .
    Thanks,
    Meena.

  • File not found and exception during commit of transaction

    Hi All,<p></p>
    We are using weblogic 8.1 sp5 and oracle 9.2. In a business process (jpd), I am getting this message and exception immediately after publishing a request document(xml) to a channel and goes to the next process node and the process aborts. Any thoughts are appreciated. Please let me know soon.
    <p></p>
    Thanks in advance!<p></p>
    Prashant
    <p></P>
    <u>Message:</u>
    Could not find a file for class oracle.jdbc.driver.T4CXAConnection
    <p></P>
    If I hit continue while debugging then I get this <u>exception:</u><p></P>
    <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-0049BFC11227BCBD651D(24359063),Status=Rolled back. [Reason=javax.ejb.EJBException: Exception on insert: java.lang.RuntimeException: Unable to serialize invocable],numRepliesOwedMe=0,numR
    epliesOwedOthers=0,seconds since begin=645,seconds left=60,XAServerResourceInfo[JMS_cgJMSStore]=(ServerResourceInfo[JMS_cgJMSStore]=(state=rolledback,assigned=qbAdmin),xar=JMS_cgJMSStore,re-Registered = false),XAServerResourceInfo[cgPool]=(ServerResourceInfo[cgPool]=(state=rolledback,assigned=qbAdmi
    n),xar=cgPool,re-Registered = false),SCInfo[qbDomain+qbAdmin]=(state=rolledback),SCInfo[current+qprocwlp1]=(state=rolledback),properties=({}),local properties=({modifiedListeners=[weblogic.ejb20.internal.TxManager$TxListener@397bfb], weblogic.jdbc.jta.cgPool=weblogic.jdbc.wrapper.TxInfo@4eb65b}),Own
    erTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=qbAdmin+10.1.130.38:7003+qbDomain+t3+, XAResources={JMS_FileStore, JMS_QProcureFileStore, cgPool, JMS_cgJMSStore, bpmArchPool},NonXAResources={})],CoordinatorURL=qbAdmin+10.1.130.38:7003+qbDomain+t3+): javax.ejb.EJBException:
    Exception on insert: java.lang.RuntimeException: Unable to serialize invocable at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerBean.java:1837) at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContainerBean.java:193) at com.bea.wli.bpm.runtime.ProcessContainerBean.ejbStore(ProcessContainerBean.java:171) at com.bea.wlwgen.PersistentContainer_bajz39_Impl.ejbStore(PersistentContainer_bajz39_Impl.java:149)at weblogic.ejb20.manager.ExclusiveEntityManager.beforeCompletion(ExclusiveEntityManager.java:593) at weblogic.ejb20.internal.TxManager$TxListener.beforeCompletion(TxManager.java:737) at weblogic.transaction.internal.ServerSCInfo.callBeforeCompletions(ServerSCInfo.java:1026) at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:116) at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1202) at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:1974) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:257) 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:2686) at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
    Caused by: java.lang.Exception: Exception on insert: java.lang.RuntimeException: Unable to serialize invocable
    at .bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerBean.java:1909) at com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbStore(BMPContainerBean.java:1817)... 18 more
    Caused by: java.lang.RuntimeException: Unable to serialize invocable at com.bea.wlw.runtime.core.container.Invocable.toByteArray(Invocable.java:812) at com.bea.wlw.runtime.core.bean.BMPContainerBean.doInsert(BMPContainerBean.java:1859)... 19 more
    Caused by: java.io.NotSerializableException: java.util.AbstractList$ListItr at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
    at com.bea.wlw.runtime.core.container.Invocable.toByteArray(Invocable.java:803)
    ... 20 more
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb20.internal.TxManager$TxListener@397bfb
    Exception on insert: java.lang.RuntimeException: Unable to serialize invocable - with nested exception:
    [javax.ejb.EJBException: Exception on insert: java.lang.RuntimeException: Unable to serialize invocable] at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1684) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311) 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)

    One possible cause of this issue is that your JPD may have some non-transient field(s) which is/are not Serializable. Check for the warnings in the Workshop, that may point you to such fields.
    ~Balwinder

  • BEA-010026 Exception occurred during commit of transaction Xid...

    Srs,
    Does anyone know how can i change the IP address bellow ? is there any file with this configuration ? ( i dont know so well weblogic )
    This is a unkown IP (10.26.71.28) and probably for this reason, the following error appears:
    <Mar 31, 2010 1:53:48 PM BRT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-012A4C55A4FA8C6F67D0(13881631),Status=Rolling Back. [Reason=javax.transaction.SystemException: SubCoordinator 'AdminServer+*10.26.71.28*:7001+tdws_domain+t3+' not available],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=167,seconds left=55,XAServerResourceInfo[JMS_ADMLoggingStore]=(ServerResourceInfo[JMS_ADMLoggingStore]=(state=rolledback,assigned=adm_managed_server),xar=JMS_ADMLoggingStore,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=new,assigned=AdminServer),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@15d1298,re-Registered = false),SCInfo[tdws_domain+AdminServer]=(state=rolling-back),SCInfo[adm+adm_managed_server]=(state=rolledback),properties=({weblogic.jdbc=t3://*10.26.71.28*:8080, START_AND_END_THREAD_EQUAL=false}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=adm_managed_server+146.250.132.247:7001+adm+t3+, XAResources={weblogic.jdbc.wrapper.JTSXAResourceImpl, JMS_ADMLoggingStore},NonXAResources={})],CoordinatorURL=adm_managed_server+146.250.132.247:7001+adm+t3+): javax.transaction.SystemException: SubCoordinator 'AdminServer+*10.26.71.28*:7001+tdws_domain+t3+' not available
    at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:1045)
    at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:173)
    at weblogic.transaction.internal.ServerSCInfo.startPrePrepareAndChain(ServerSCInfo.java:163)
    at weblogic.transaction.internal.ServerTransactionImpl.localPrePrepareAndChain(ServerTransactionImpl.java:1202)
    at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2007)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:257)
    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)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: SubCoordinator 'AdminServer+10.26.71.28:7001+tdws_domain+t3+' not available - with nested exception:
    [javax.transaction.SystemException: SubCoordinator 'AdminServer+10.26.71.28:7001+tdws_domain+t3+' not available]
    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1687)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:311)
    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)
    Thanks,
    Claudio
    Edited by: user1098890 on 31/03/2010 12:35

    Did anyone ever find an answer to this? I have the same problem.

  • Exception occurred during commit of transaction Name

    Hi,
    I am getting following error while updating a Table through the application.
    I am running the application on welogic 9.2.. I have added new Constants to the the existing methods and i am trying to update the database table row with this new constant. It works fine if i use the existing constants in from the constant file.
    *<Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.mfizac.oe.session.so.SOServiceBean.completeRoutes(com.mfizac.framework.data.DataMap)],Xid=BEA1-00F6B94908E2407590E1(1552254),Status=Rolled back. [Reason=weblogic.utils.NestedRuntimeException: Error in beforeCompletion],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=rolledback,assigned=AdminServer),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@221fc5,re-Registered = false),SCInfo[mfizac+AdminServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.mfizac.oe.session.so.SOServiceBean.completeRoutes(com.mfizac.framework.data.DataMap)], weblogic.jdbc=t3://192.9.200.122:7001}),local properties=({modifiedListeners=[weblogic.ejb.container.internal.TxManager$TxListener@1cc7bf]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+192.9.200.122:7001+mfizac+t3+, XAResources={weblogic.jdbc.wrapper.JTSXAResourceImpl, WLStore_mfizac_JMSMessageStore},NonXAResources={})],CoordinatorURL=AdminServer+192.9.200.122:7001+mfizac+t3+): weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb.container.internal.TxManager$TxListener@1cc7bf*
    Error in beforeCompletion
    *     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1809)*
    *     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:331)*
    *     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)*
    *     at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:546)*
    *     at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)*
    *     at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:381)*
    *     at com.mfizac.oe.session.so.SOService_mfkez4_EOImpl.completeRoutes(SOService_mfkez4_EOImpl.java:1573)*
    *     at com.mfizac.oe.session.so.SOService_mfkez4_EOImpl_WLSkel.invoke(Unknown Source)*
    *     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)*
    *     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)*
    *     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)*
    *     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)*
    *     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)*
    *     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:439)*
    *     at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:61)*
    *     at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:983)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)*
    *.>*
    Any help would be greatly appriciated.
    Thanks,
    Ven
    Edited by: user1545630 on Jan 12, 2010 1:21 PM
    Edited by: user1545630 on Jan 12, 2010 1:23 PM
    Edited by: user1545630 on Jan 12, 2010 1:26 PM
    Edited by: user1545630 on Jan 12, 2010 1:39 PM

    Hi,
    I am getting following error while updating a Table through the application.
    I am running the application on welogic 9.2.. I have added new Constants to the the existing methods and i am trying to update the database table row with this new constant. It works fine if i use the existing constants in from the constant file.
    *<Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.mfizac.oe.session.so.SOServiceBean.completeRoutes(com.mfizac.framework.data.DataMap)],Xid=BEA1-00F6B94908E2407590E1(1552254),Status=Rolled back. [Reason=weblogic.utils.NestedRuntimeException: Error in beforeCompletion],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=60,XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=rolledback,assigned=AdminServer),xar=weblogic.jdbc.wrapper.JTSXAResourceImpl@221fc5,re-Registered = false),SCInfo[mfizac+AdminServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.mfizac.oe.session.so.SOServiceBean.completeRoutes(com.mfizac.framework.data.DataMap)], weblogic.jdbc=t3://192.9.200.122:7001}),local properties=({modifiedListeners=[weblogic.ejb.container.internal.TxManager$TxListener@1cc7bf]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+192.9.200.122:7001+mfizac+t3+, XAResources={weblogic.jdbc.wrapper.JTSXAResourceImpl, WLStore_mfizac_JMSMessageStore},NonXAResources={})],CoordinatorURL=AdminServer+192.9.200.122:7001+mfizac+t3+): weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=weblogic.ejb.container.internal.TxManager$TxListener@1cc7bf*
    Error in beforeCompletion
    *     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1809)*
    *     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:331)*
    *     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)*
    *     at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:546)*
    *     at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)*
    *     at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:381)*
    *     at com.mfizac.oe.session.so.SOService_mfkez4_EOImpl.completeRoutes(SOService_mfkez4_EOImpl.java:1573)*
    *     at com.mfizac.oe.session.so.SOService_mfkez4_EOImpl_WLSkel.invoke(Unknown Source)*
    *     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)*
    *     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)*
    *     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)*
    *     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)*
    *     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)*
    *     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:439)*
    *     at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:61)*
    *     at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:983)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)*
    *.>*
    Any help would be greatly appriciated.
    Thanks,
    Ven
    Edited by: user1545630 on Jan 12, 2010 1:21 PM
    Edited by: user1545630 on Jan 12, 2010 1:23 PM
    Edited by: user1545630 on Jan 12, 2010 1:26 PM
    Edited by: user1545630 on Jan 12, 2010 1:39 PM

  • TOPLINK-69 exception during commit.

    I am receiving the following exception during commit, idcprice.tenor happens to
    be an aggregate object defined in extending class, this does not always happen,
    can provide more info.
    This is extremely urgent!!! thanks
    Exception:
    2008-04-03 17:05:05,390 ERROR http-0.0.0.0-8080-3 [[email protected]] FXTRADER_WORKFLOWHEL
    PER_FACADE :: acceptRFPQuote() : Exception thrown Database exception: Exception [TOPLINK-69] (Oracle
    TopLink - 10g Release 3 (10.1.3.3.0) (Build 070620)): oracle.toplink.exceptions.DescriptorException
    Exception Description: A NullPointerException was thrown while extracting a value from the instance
    variable [tenor] in the object [null].
    Internal Exception: java.lang.NullPointerException
    Mapping: oracle.toplink.mappings.DirectToFieldMapping[tenor-->IdcPrice.tenor]
    Descriptor: Descriptor(com.integral.finance.trade.Tenor --> [DatabaseTable(IdcPrice)]).

    The bug is that you're getting an NPE instead of a validation exception. When the bug is fixed you'll still get an exception--just one that communicates the problem in your code better.
    It boils down to the fact that you can't share a single aggregate instance between two "owners". This has nothing to do with the aggregate being defined in the base class. The owner and aggregate form a composite--they have the same life cycle. For example if you delete the owner you delete the aggregate. I think you have a situation in which the same instance of an aggregate is being assigned to two owner objects and you're getting this exception.
    In other words somewhere in your code you're either doing something like:
    MyAggregate ag = new MyAggregate();
    object1.setAggregate(ag);
    object2.setAggregate(ag);or
    object1.setAggregate(object2.getAggregate());You need to clone an aggregate if you want to duplicate it's value and assign it to a second owner. Something like:
    MyAggregate ag = new MyAggregate();
    object1.setAggregate(ag);
    object2.setAggregate(ag.clone());or
    object1.setAggregate(object2.getAggregate().clone());--Shaun                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • BPELEngineBean.syncCreateAndInvoke throws Exception occurred during commit

    We have a SOA Suite 11g composite deployed on a cluster with 4 managed server.
    Version of SOA suite is 11.1.1.1.0
    This composite gets called only once a day.
    Following errror is thrown by the composite only sometimes
    ###<Apr 12, 2010 8:03:51 AM EDT> <Error> <EJB> <ulolaaspa06> <lolasoa-9711-Managed2> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <webserviceuser> <> <> <1271073831333> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean.syncCreateAndInvoke(oracle.soa.management.ComponentDN,java.lang.String,oracle.fabric.common.NormalizedMessage)],Xid=BEA1-353533481A0F8887627C(308589051),Status=Rolled back. [Reason=oracle.jdbc.xa.OracleXAException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=214,seconds left=60,XAServerResourceInfo[lolaDS_lolasoa]=(ServerResourceInfo[lolaDS_lolasoa]=(state=rolledback,assigned=lolasoa-9711-Managed2),xar=lolaDS,re-Registered = false),XAServerResourceInfo[SOADataSource_lolasoa]=(ServerResourceInfo[SOADataSource_lolasoa]=(state=rolledback,assigned=lolasoa-9711-Managed2),xar=SOADataSource,re-Registered = false),SCInfo[lolasoa+lolasoa-9711-Managed2]=(state=rolledback),SCInfo[lola+lola-9631-Managed2]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean.syncCreateAndInvoke(oracle.soa.management.ComponentDN,java.lang.String,oracle.fabric.common.NormalizedMessage)]}),local properties=({weblogic.jdbc.jta.SOADataSource=[ No XAConnection is attached to this TxInfo ], weblogic.jdbc.jta.lolaDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=lolasoa-9711-Managed2+ulolaaspa06.cuc.com:9711+lolasoa+t3+, XAResources={eis/tibjms/Queue, eis/activemq/Queue, WSATGatewayRM_lolasoa-9711-Managed2_lolasoa, eis/fioranomq/Topic, eis/DB/SOADemo, eis/Apps/Apps, eis/webspheremq/Queue, eis/AQ/aqSample, lolaDS_lolasoa, eis/tibjmsDirect/Queue, eis/aqjms/Queue, eis/sunmq/Queue, eis/pramati/Queue, eis/tibjms/Topic, WLStore_lolasoa__WLS_lolasoa-9711-Managed2, eis/jbossmq/Queue, eis/wls/Queue, oracle.tip.adapter.jms.JmsXAResource, eis/tibjmsDirect/Topic, WLStore_lolasoa_SOAJMSFileStore_auto_2, eis/wls/Topic, EDNDataSource_lolasoa, eis/aqjms/Topic, WLStore_lolasoa_filestore_lolasoa_9711_2, WLStore_lolasoa_UMSJMSFileStore_auto_2, SOADataSource_lolasoa},NonXAResources={})],CoordinatorURL=lolasoa-9711-Managed2+ulolaaspa06.cuc.com:9711+lolasoa+t3+): weblogic.transaction.RollbackException: Could not prepare resource 'lolaDS_lolasoa
         at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1834)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
         at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
         at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:591)
         at weblogic.ejb.container.internal.BaseLocalObject.postInvokeTxRetry(BaseLocalObject.java:424)
         at com.collaxa.cube.engine.ejb.impl.bpel.BPELEngineBean_51369e_ICubeEngineLocalBeanImpl.syncCreateAndInvoke(BPELEngineBean_51369e_ICubeEngineLocalBeanImpl.java:676)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:528)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:482)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:156)
         at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.request(CubeDeliveryBean.java:600)
         at sun.reflect.GeneratedMethodAccessor836.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
         at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
         at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
         at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
         at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy188.request(Unknown Source)
         at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.request(BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.java:745)
         at oracle.fabric.CubeServiceEngine.request(CubeServiceEngine.java:290)
         at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139)
         at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:179)
         at oracle.integration.platform.blocks.mesh.MeshImpl$2.run(MeshImpl.java:167)
         at javax.security.auth.Subject.doAs(Subject.java:396)
         at oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject(MeshImpl.java:165)
         at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:141)
         at sun.reflect.GeneratedMethodAccessor830.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:296)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:177)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:144)
         at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:59)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166)
         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
         at $Proxy202.request(Unknown Source)
         at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.doMessageProcessing(WebServiceEntryBindingComponent.java:1155)
         at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.processIncomingMessage(WebServiceEntryBindingComponent.java:767)
         at oracle.integration.platform.blocks.soap.FabricProvider.processMessage(FabricProvider.java:113)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1119)
         at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:881)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
         at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.security.Security.runAs(Security.java:61)
         at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
         at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
         at oracle.security.jps.wls.jaas.WlsSubjectSecurity.executeAs(WlsSubjectSecurity.java:145)
         at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:293)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:888)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:553)
         at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:202)
         at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:166)
         at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:384)
         at oracle.integration.platform.blocks.soap.FabricProviderServlet.doPost(FabricProviderServlet.java:444)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: oracle.jdbc.xa.OracleXAException
         at oracle.jdbc.xa.client.OracleXAResource.prepare(OracleXAResource.java:673)
         at weblogic.jdbc.wrapper.VendorXAResource.prepare(VendorXAResource.java:70)
         at weblogic.jdbc.jta.DataSource.prepare(DataSource.java:887)
         at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:1278)
         at weblogic.transaction.internal.XAServerResourceInfo.prepare(XAServerResourceInfo.java:500)
         at weblogic.transaction.internal.ServerSCInfo.startPrepare(ServerSCInfo.java:380)
         at weblogic.transaction.internal.ServerTransactionImpl.localPrepare(ServerTransactionImpl.java:2589)
         at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2236)
         at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
         ... 84 more
    .>
    lolaDS is our XA datasource pointing to application database.
    We can not consistently recreate this error. It happens only sometimes.
    It looks when appllication is redeployed or when it goes through reintialization (of application singletons) we have seen this error happen more. We have some application config properties and lolaDS datasource stored in a singleton.

    Did you ever get a solution to this issue? We are having a similar problem.

  • Deploy to Application Server Failed on a distributed environment

    Hi All,
    I am trying to configure new Hyperion verion 11.1.2.2 on distributed environment but during configuring calculation manager to application server failed and getting error message like "Deploy to Application Server Failed". I am not sure what is issue and how to fix it. I have tried to read log files but I am not able to undersantd where to look and debug this issue.
    My Hyperion Environment over view as a below:-
    1- I have used Microsoft VMWARE to build my Hyperion Enviornment
    2- I have created 1 window server 2003 domain and made 4 clients of that domain. (All these systems have windows server 2003 installed). I have given name to each client server i.e. System A, System B, System C, System D
    3- I have installed SQL 2005 and created databases for all Hyperion components i.e. Shared services, calculation manager, epma on a system A
    5- I have installed and configured foundation services and weblogic server on a system B. (In this system I have installed and configured shared services, weblogic, workspace, and able to deploye application server on a same system)
    6- On a system A I am able to complete installation for hyperion Performance Management Architect and Calculation Manager and able to finish all type of configuration for these two components but as soon as system trying to configure any related to APPLICATION SERVER services it fails to configure. On a configuration summary page system shows everything is configured but APPLICATION SERVER says FAILED wrtten on a red color letters.
    I have explored log files and found that Calculation Manager application server failed to deploy or Deploy to Application server failed.....
    Since, I am not sure where to look and how to debug this issue I am requesting to all hyperion friends to help and guide me to debug as I have been trying to install this product since last friday and still no out put....
    I will be really thankful if someone share his or her wisdom to help me....
    Thank you to all in Advance.....
    Thanks,
    Safi

    Did you install all the WebLogic web applications on the foundation machine as well as the machine they are going to be deployed to.
    "On the machine on which you plan to administer the WebLogic Server, you must install all Web applications for all applications you plan to deploy on any machine in the environment. (The WebLogic Administration Server is installed and deployed on the Foundation Services machine.)"
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Weblogic 7 SP5 SQL Exceptions follow a JTA transaction timeout

    I have a problem in Weblogic 7 SP5 that was not happening in SP2. I'm using the
    Weblogic jDriver (weblogic.jdbc.mssqlserver4.Driver)
    I have a transaction that times out due to JTA transaction timeout, and then gets
    marked for rollback. For several minutes after the timeout, I get many SQL Exceptions
    with bogus messages like "invalid column name" when the column name is, in fact,
    correct.
    Then the weblogic log file shows "Exception during rollback of transaction" (javax.transaction.SystemException:
    Heuristic hazard). Next, the connection is tested on reserve, this test fails,
    and the connection is refreshed. As soon as the connection is refreshed, I stop
    getting SQL exceptions and everything starts working correctly again.
    It seems like the transaction timeout is making the connection go bad, and somehow
    other requests are using this bad connection before the transaction finishes rolling
    back. What could the problem be? Some excerpts from my app log and weblogic log
    are below.
    com.workpoint.server.ejb.WorkPointEJBException: The transaction is no longer active
    - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 901 seconds
    Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17109:68c10765ba68aaaa(12114044),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=901,seconds left=60,activeThread=Thread[WorkQueueThread[q=1, qName=ProcReleaseTaskWorkers,
    id=6],5,WorkQueueGroup[id=1, name=ProcReleaseTaskWorkers]],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none,xar=weblogic.jdbc.jts.Connection@18cd616,re-Registered
    = false),SCInfo[DomainManager+edwards-s1]=(state=active),properties=({weblogic.transaction.name=[EJB
    com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
    weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
    Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+)]'.
    No further JDBC access is allowed within this transaction.SQL Command = INSERT
    INTO WP_PROCI_NODE_HIST (NODE_HIST_ID, NODE_HIST_DB, PROCI_ID, PROCI_DB, PROCI_NODE_ID,
    PROCI_NODE_DB, NODE_ITERATION, NODE_STATE_ID, ROW_VERSION, LU_ID, LU_DATE) VALUES
    weblogic.jdbc.mssqlserver4.TdsException: Invalid column name 'user_fname'.
    [from weblogic log]
    ####<Jun 17, 2004 8:14:16 AM MDT> <Error> <EJB> <EDWARDS> <edwards-s1> <WorkQueueThread[q=1,
    qName=ProcReleaseTaskWorkers, id=7]> <kernel identity> <> <010025> <Exception
    during rollback of transaction Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17439:68c10765ba68aaaa(31878774),Status=Rolled
    back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
    since begin=3,seconds left=57,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=edwards-s1,xar=weblogic.jdbc.jts.Connection@15e1b7e,re-Registered
    = false),SCInfo[DomainManager+edwards-s1]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
    com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
    weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
    Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+): javax.transaction.SystemException:
    Heuristic hazard: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException:
    I/O exception while talking to the server, java.io.EOFException))
    ####<Jun 17, 2004 8:14:17 AM MDT> <Warning> <JDBC> <EDWARDS> <edwards-s1> <ExecuteThread:
    '8' for queue: 'default'> <kernel identity> <> <001094> <A connection from pool
    "sp_connection_pool" was tested during reserve with the SQL "select 1" and failed:
    weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server,
    java.io.EOFException
    ...[stack trace omitted]...
    This connection will now be refreshed.>

    Brad Swanson wrote:
    According to BEA's documentation, the jDriver is deprecated (no longer supported)
    in WLS 7 SP5. Not sure when they stopped supporting it, but sometime after SP2,
    apparently. Our solution, unfortunately, was to stay with SP2. Using the newer,
    supported JDBC driver would presumably fix the problem, but we didn't have time
    to do a full regression test with a different driver.Hi, no. The jDriver is deprecated, not unsupported. For WLS releases that contain
    the jDriver it will be supported for as long as we support the WLS release!
    Deprecation just means that we may choose to not supply that driver in any future
    release, and will not support it in that or any subsequent release.
    Practically, much depends on which jDriver you're using. In decreasing order
    of practical support we have: The weblogic.jdbc.oci.Driver to Oracle: We do actively
    continue to fix bugs in it. The weblogic.jdbc.mssqlserver4.Driver: Very unlikely that
    we will fix any new problem with it. The weblogic.jdbc.ifmx.Driver: Even less
    likely that we will do anything with it...
    I hope that makes it better for you.
    Joe

  • Javax.transaction.SystemException: Timeout during commit processing

              In my Workshop 8.1 SP2 project I have a Custom Java Control whose methods I call
              from my JPF. From that custom control I create a remote connection to a Weblogic
              6.1 Application server. I execute remote methods and get the expected objects
              back with no problem. The problem is that I cannot return that object from my
              custom control back to my jpf. As soon as the method's return statement is executed,
              the process hangs for a considerable period of time and then throws the following
              Exception:
              An error has occurred:
              Exception while commiting Tx : Name=[EJB com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)],Xid=BEA1-0005BF0F3E6E72419698(655489),Status=Unknown,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
              since begin=217,seconds left=42983,XAServerResourceInfo[BMResourceManager]=(ServerResourceInfo[BMResourceManager]=(state=new,assigned=none),xar=null),SCInfo[midway+cgServer]=(state=active),SCInfo[prdsdomain+prdsserver]=(state=active),properties=({weblogic.transaction.name=[EJB
              com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(com.bea.wlw.runtime.core.request.Request)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=cgServer+172.23.83.174:7001+midway+t3+,
              XAResources={},NonXAResources={})],CoordinatorURL=prdsserver+172.23.4.109:7041+prdsdomain+t3+);
              nested exception is:
              javax.transaction.SystemException: Timeout during commit processing
              Start server side stack trace:
              javax.transaction.SystemException: Timeout during commit processing
              at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:243)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
              at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
              at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              caused by: : javax.transaction.SystemException: Timeout during commit processing
              Start server side stack trace:
              javax.transaction.SystemException: Timeout during commit processing
              at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:243)
              at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
              at weblogic.transaction.internal.CoordinatorImpl.commit(CoordinatorImpl.java:68)
              at weblogic.transaction.internal.CoordinatorImpl_WLSkel.invoke(Unknown Source)
              at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
              at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
              at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              As soon as I take out RMI calls from my custom control's code, I can return any
              object I want back to my JPF. Here is the what I am thinking is happenning.
              The system that runs on Weblogic 6.1 manages its own transactions and begins a
              new transaction every time a session bean residing on that server is invoked.
              In addition, Weblogic 8.1 starts an internal transaction when the Custom Java
              Control makes a call. Could there be some kind conflict? If yes, is it possible
              to disable transactions from the Java Control?
              Thank you very much
              Alex Mayzlin
              

    Horst,
              "aa aa" <[email protected]> wrote in message news:20701457.1093414960276.JavaMail.root@jserv5...
              > we are getting the same Exception. As nobody replied to your question, it would be interesting, if you found any solution
              yourself?
              >
              > Additional info:
              > We are also getting these error messages from BEA when testing connections in pool before and after the exception:
              >
              > <20.08.2004 19.32 Uhr CEST> <Error> <JDBC> <BEA-001112> <Test "SELECT count(*) FROM invoice" set up for pool "ABCConnection Pool"
              failed with exception: "java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction 4.47.141655".>
              Generally it's a good idea to use Oracle's system DUAL table
              for testing connections on reserve. Try to change your ABCConnection
              connection pool configuration to use DUAL as the test table
              instead of "invoice".
              Regards,
              Slava Imeshev
              

  • Java.sql.SQLException: You cannot commit during a managed transaction!

    Hi all,
    I'm just trying to get the tutorial Car EJP app to work with Jboss 3.2.1
    When creating a new car record by calling the car.edit() method it reaches
    the line
    pm.makePersistent (car);
    and then throws the exception
    com.solarmetric.kodo.runtime.FatalDataStoreException:
    com.solarmetric.kodo.runtime.FatalDataStoreException:
    java.sql.SQLException: You cannot commit during a managed transaction!
    [code=0;state=null]
    When checking the jboss log, it is clear that kodo is trying to commit the
    sequence update :
    at
    org.jboss.resource.adapter.jdbc.WrappedConnection.commit(WrappedConnection.java:477)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.commit(SQLExecutionManagerImpl.java:783)
    at
    com.solarmetric.kodo.impl.jdbc.schema.DBSequenceFactory.updateSequence(DBSequenceFactory.java:267)
    at
    com.solarmetric.kodo.impl.jdbc.schema.DBSequenceFactory.getNext(DBSequenceFactory.java:111)
    at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.newDataStoreId(JDBCStoreManager.java:598)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.makePersistentFilter(PersistenceManagerImpl.java:1418)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.makePersistent(PersistenceManagerImpl.java:1348)
    at com.titan.kodojdotest.ejb.CarBean.edit(CarBean.java:51)
    How should i get this to work ????
    tx for your help,
    Roger.

    It appears that you are using ConnectionFactoryName. First be sure to
    set a ConnectionFactory2Name which will be a non-transactional (in terms
    of global transaction) DataSource for sequence generation for which you
    are seeing here. There are also some issues with JBoss's connection
    pooling on certain dbs if you are still seeing the problem after this.
    If so, try setting ConnectionURL, ConnectionPassword, etc explicitly
    Roger Laenen wrote:
    Hi all,
    I'm just trying to get the tutorial Car EJP app to work with Jboss 3.2.1
    When creating a new car record by calling the car.edit() method it reaches
    the line
    pm.makePersistent (car);
    and then throws the exception
    com.solarmetric.kodo.runtime.FatalDataStoreException:
    com.solarmetric.kodo.runtime.FatalDataStoreException:
    java.sql.SQLException: You cannot commit during a managed transaction!
    [code=0;state=null]
    When checking the jboss log, it is clear that kodo is trying to commit the
    sequence update :
    at
    org.jboss.resource.adapter.jdbc.WrappedConnection.commit(WrappedConnection.java:477)
    at
    com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.commit(SQLExecutionManagerImpl.java:783)
    at
    com.solarmetric.kodo.impl.jdbc.schema.DBSequenceFactory.updateSequence(DBSequenceFactory.java:267)
    at
    com.solarmetric.kodo.impl.jdbc.schema.DBSequenceFactory.getNext(DBSequenceFactory.java:111)
    at
    com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.newDataStoreId(JDBCStoreManager.java:598)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.makePersistentFilter(PersistenceManagerImpl.java:1418)
    at
    com.solarmetric.kodo.runtime.PersistenceManagerImpl.makePersistent(PersistenceManagerImpl.java:1348)
    at com.titan.kodojdotest.ejb.CarBean.edit(CarBean.java:51)
    How should i get this to work ????
    tx for your help,
    Roger.
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com

  • [EMF Transaction] Exception during rollback

    On a number of occasions we have faced some exception during rollback, if our code encounters an exception while processing the transaction.
    Here is a very typical example:
    org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: index=1, size=1
    at org.eclipse.emf.common.util.BasicEList.remove(BasicEList.java:602)
    at org.eclipse.emf.common.notify.impl.NotifyingListImpl.doRemove(NotifyingListImpl.java:756)
    at org.eclipse.emf.common.notify.impl.NotifyingListImpl.remove(NotifyingListImpl.java:707)
    at org.eclipse.emf.ecore.change.impl.ListChangeImpl.process(ListChangeImpl.java:546)
    at org.eclipse.emf.ecore.change.impl.ListChangeImpl.apply(ListChangeImpl.java:476)
    at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:701)
    at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.process(FeatureChangeImpl.java:611)
    at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:518)
    at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:493)
    at org.eclipse.emf.ecore.change.impl.ChangeDescriptionImpl.apply(ChangeDescriptionImpl.java:300)
    at org.eclipse.emf.transaction.util.CompositeChangeDescription.apply(CompositeChangeDescription.java:104)
    at org.eclipse.emf.transaction.impl.TransactionImpl.doRollback(TransactionImpl.java:570)
    at org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:417)
    at org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.doExecute(TransactionalCommandStackImpl.java:70)
    at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
    at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
    at org.eclipse.emf.emfstore.internal.client.transaction.EMFStoreTransactionalCommandStack.execute(EMFStoreTransactionalCommandStack.java:52)
    This seems to be caused by an attempt to remove an element from a list. Debugging here is showing that the rollback is trying to apply the undo changes produced by the transaction recorder. But the element that it is attempting to remove doesn't exist in the list, and thus the error. I suspect that this is because when the initial exception occurred that this command had not been executed yet. If that is the case, I would expect the rollback to have a way to check for the commands that have completed and to reverse them, but to ignore any commands that have never completed yet. Is it what I might be saying and what is the solution?
    I'm adding below portion of the stacktrace that represents the original exception that triggered the rollback. This might help a bit in understanding the situation.
    Caused by: java.lang.ClassCastException: ....
    at com.castortech.util.emf.VersioningUtils.runInCompositeOperation(VersioningUtils.java:83)
    at org.eclipse.sirius.table.business.internal.dialect.TableDialectServices.refresh(TableDialectServices.java:272)
    at org.eclipse.sirius.business.internal.dialect.DialectManagerImpl.refresh(DialectManagerImpl.java:106)
    at org.eclipse.sirius.business.api.dialect.command.RefreshRepresentationsCommand.doExecute(RefreshRepresentationsCommand.java:85)
    at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
    at org.eclipse.emf.common.command.CompoundCommand.execute(CompoundCommand.java:261)
    at org.eclipse.sirius.business.internal.session.SessionEventBrokerImpl$PreCommitPriorityNotifyListenersCommand.launchCommands(SessionEventBrokerImpl.java:251)
    at org.eclipse.sirius.business.internal.session.SessionEventBrokerImpl$PreCommitPriorityNotifyListenersCommand.doExecute(SessionEventBrokerImpl.java:242)
    at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
    at org.eclipse.emf.transaction.util.TriggerCommand.execute(TriggerCommand.java:113)
    at org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.executeTriggers(TransactionalCommandStackImpl.java:218)
    at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.precommit(TransactionalEditingDomainImpl.java:712)
    at org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:414)
    at org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.doExecute(TransactionalCommandStackImpl.java:70)
    at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
    at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
    at org.eclipse.emf.emfstore.internal.client.transaction.EMFStoreTransactionalCommandStack.execute(EMFStoreTransactionalCommandStack.java:52)
    Thanks
    Alain

    Hi, Alain,
    Indeed, the transaction will have difficulty rolling back if the
    ChangeDescription cannot successfully be applied. However, a
    ChangeDescription records only changes that actually are effected in
    the model. I don't know how it could record changes that haven't yet
    occurred.
    Does your model have custom implementations of some of these list
    features, as UML2 does, that perhaps coordinate changes with other
    features? Could it be that undoing some changes causes side-effects in
    others that then invalidate changes recorded in those?
    Or are there non-ChangeDescription-based commands being undone by the
    transaction that could interfere with ChangeDescriptions?
    There's not really much that a transaction can do to validate the
    applicability of a ChangeDescription ... it seems to me that it's up to
    the model and the commands captured by a transaction to ensure that
    undo will happen correctly. Although, perhaps failed rollback could
    somehow be handled more gracefully? I'm not sure.
    Cheers,
    Christian
    On 2015-08-08 18:12:21 +0000, Alain Picard said:
    > On a number of occasions we have faced some exception during rollback,
    > if our code encounters an exception while processing the transaction.
    > Here is a very typical example:
    >
    >
    > org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException:
    > index=1, size=1
    > at org.eclipse.emf.common.util.BasicEList.remove(BasicEList.java:602)
    > at
    > org.eclipse.emf.common.notify.impl.NotifyingListImpl.doRemove(NotifyingListImpl.java:756)
    >
    > at
    > org.eclipse.emf.common.notify.impl.NotifyingListImpl.remove(NotifyingListImpl.java:707)
    >
    > at
    > org.eclipse.emf.ecore.change.impl.ListChangeImpl.process(ListChangeImpl.java:546)
    >
    > at
    > org.eclipse.emf.ecore.change.impl.ListChangeImpl.apply(ListChangeImpl.java:476)
    >
    > at
    > org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:701)
    >
    > at
    > org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.process(FeatureChangeImpl.java:611)
    >
    > at
    > org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:518)
    >
    > at
    > org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:493)
    >
    > at
    > org.eclipse.emf.ecore.change.impl.ChangeDescriptionImpl.apply(ChangeDescriptionImpl.java:300)
    >
    > at
    > org.eclipse.emf.transaction.util.CompositeChangeDescription.apply(CompositeChangeDescription.java:104)
    >
    > at
    > org.eclipse.emf.transaction.impl.TransactionImpl.doRollback(TransactionImpl.java:570)
    >
    > at
    > org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:417)
    >
    > at
    > org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.doExecute(TransactionalCommandStackImpl.java:70)
    >
    > at
    > org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
    >
    > at
    > org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
    >
    > at
    > org.eclipse.emf.emfstore.internal.client.transaction.EMFStoreTransactionalCommandStack.execute(EMFStoreTransactionalCommandStack.java:52)
    >
    >
    >
    > This seems to be caused by an attempt to remove an element from a list.
    > Debugging here is showing that the rollback is trying to apply the undo
    > changes produced by the transaction recorder. But the element that it
    > is attempting to remove doesn't exist in the list, and thus the error.
    > I suspect that this is because when the initial exception occurred that
    > this command had not been executed yet. If that is the case, I would
    > expect the rollback to have a way to check for the commands that have
    > completed and to reverse them, but to ignore any commands that have
    > never completed yet. Is it what I might be saying and what is the
    > solution?
    >
    > I'm adding below portion of the stacktrace that represents the original
    > exception that triggered the rollback. This might help a bit in
    > understanding the situation.
    >
    > Caused by: java.lang.ClassCastException: ....
    > ...
    > at
    > com.castortech.util.emf.VersioningUtils.runInCompositeOperation(VersioningUtils.java:83)
    >
    > at
    > org.eclipse.sirius.table.business.internal.dialect.TableDialectServices.refresh(TableDialectServices.java:272)
    >
    > at
    > org.eclipse.sirius.business.internal.dialect.DialectManagerImpl.refresh(DialectManagerImpl.java:106)
    >
    > at
    > org.eclipse.sirius.business.api.dialect.command.RefreshRepresentationsCommand.doExecute(RefreshRepresentationsCommand.java:85)
    >
    > at
    > org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
    >
    > at
    > org.eclipse.emf.common.command.CompoundCommand.execute(CompoundCommand.java:261)
    >
    > at
    > org.eclipse.sirius.business.internal.session.SessionEventBrokerImpl$PreCommitPriorityNotifyListenersCommand.launchCommands(SessionEventBrokerImpl.java:251)
    >
    > at
    > org.eclipse.sirius.business.internal.session.SessionEventBrokerImpl$PreCommitPriorityNotifyListenersCommand.doExecute(SessionEventBrokerImpl.java:242)
    >
    > at
    > org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
    >
    > at
    > org.eclipse.emf.transaction.util.TriggerCommand.execute(TriggerCommand.java:113)
    >
    > at
    > org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.executeTriggers(TransactionalCommandStackImpl.java:218)
    >
    > at
    > org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.precommit(TransactionalEditingDomainImpl.java:712)
    >
    > at
    > org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:414)
    >
    > at
    > org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.doExecute(TransactionalCommandStackImpl.java:70)
    >
    > at
    > org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
    >
    > at
    > org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
    >
    > at
    > org.eclipse.emf.emfstore.internal.client.transaction.EMFStoreTransactionalCommandStack.execute(EMFStoreTransactionalCommandStack.java:52)
    >
    >
    >
    > Thanks
    > Alain

  • Exception generated during defered local transaction handling

    Hi All,
    We are using data direct connect 3.3 driver with MS SQL Server 7 on WebSphere 4.0. We are getting the exception "Exception generated during defered local transaction handling". Anyone encountered similar problem?> please let me know the solution. I am pasting the stack trace here.
    Thanks in advance.
    Regards,
    Girish
    [7/29/05 9:19:31:210 EDT] 37c1f1 SystemOut U 2005-07-29 09:19:31,177 [Servlet.Engine.Transports:10] ERROR com.xyz.nuuw.bus.dao.JDBCWrapper -livdsqa11122643171177
    java.sql.SQLException: [IBM][SQLServer JDBC Driver]Exception generated during defered local transaction handling. See next exception via SQLException.getNextException for details.
    at com.ibm.websphere.jdbc.base.BaseExceptions.createException(Unknown Source)
    at com.ibm.websphere.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.ibm.websphere.jdbc.base.BaseExceptions.getException(Unknown Source)
    at com.ibm.websphere.jdbc.base.BaseConnection.transactionableWorkStarting(Unknown Source)
    at com.ibm.websphere.jdbc.base.BaseStatement.commonExecute(Unknown Source)
    at com.ibm.websphere.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
    at com.ibm.websphere.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source)
    at com.ibm.websphere.jdbcx.base.BasePreparedStatementWrapper.executeQuery(Unknown Source)
    at com.ibm.ejs.cm.cache.CachedStatement.executeQuery(CachedStatement.java:312)
    at com.ibm.ejs.cm.proxy.StatementProxy.executeQueryCommon(StatementProxy.java:410)
    at com.ibm.ejs.cm.proxy.PreparedStatementProxy.executeQuery(PreparedStatementProxy.java:53)
    at com.xyz.nuuw.bus.dao.JDBCWrapper.getdata(JDBCWrapper.java:164)
    at com.xyz.nuuw.bus.dao.AccountSetupPH.getKeyID(AccountSetupPH.java:445)
    at com.xyz.nuuw.bus.bo.AccountSetupBO.getKeyID(AccountSetupBO.java:50)
    at com.xyz.nuuw.accountSetup.bus.ejb.AccountSetupSBBean.getKeyID(AccountSetupSBBean.java:85)
    at com.xyz.nuuw.accountSetup.bus.ejb.EJSRemoteStatelessAccountSetupSB_14ea1086.getKeyID(EJSRemoteStatelessAccountSetupSB_14ea1086.java:99)
    at com.xyz.nuuw.accountSetup.bus.ejb._AccountSetupSB_Stub.getKeyID(_AccountSetupSB_Stub.java:310)
    at com.xyz.nuuw.bus.AccountSetupBD.getKeyID(AccountSetupBD.java:73)

    I am currently working with IBM on a similar problem with WAS 5.1 and SQL Server 2000. The SQLException has a nested exception that can be retrieved using the getNextException() method. This will give you some more information as to what is causing the problem. Ours seems to be triggered by a dropped connection at the SQL end. normally WAS will recover from that gracefully, but in our situation it is not.
    Doug

  • Question: Exception during Transaction

    I have a question regarding Transactions. Suppose I have the following code:
    public void test() throws Exception {
    UserTransaction ut = getUserTransaction(); // lookup method
    ut.begin();
    if (true) throw new Exception("Testing");
    ut.commit();
    As it is not going to commit the transaction, no rollback is explicity made. Is the transaction automatically closed ? Or this is a memory leak ?
    Thank you

    Hi,
    I have a question regarding Transactions. Suppose I
    have the following code:
    public void test() throws Exception {
    UserTransaction ut = getUserTransaction(); //
    // lookup method
    ut.begin();
    if (true) throw new Exception("Testing");
    ut.commit();
    As it is not going to commit the transaction, no
    rollback is explicity made. Is the transaction
    automatically closed ? Or this is a memory leak ?
    Thank youWhat you mean by memory leak here? If it is regarding the UserTransaction object existence then it is there in the test() only.Once the test returns the object is prepared for GC.
    Regards
    Vicky

  • Doubt about locking of record's in distributed environment...

    i read kumar's comment in my previous thread, he haad mentioned the following code,
    cursor <> is select * from <> where <> for update of <>, so that it will be locked if it was unlocked...
    but assume i have the following part of code
    cursor <> is select * from <> where <>
    begin
    update the records if some condition is found during runtime
    end;
    and this happens to be invoked in a distributed manner, so what will happen if two sessions run the code at the same time, and how is data integrity handled in this case???
    also explain with regard to usage of sequence(S) in a distributed environment...
    Thanks And Regards,
    Vairavan.S

    Oracle will prevent two transactions from simultaneously modifying a row. Oracle can ensure that the database is consistent.
    Many applications need to enforce a more stringent constraint. They need to ensure that committed data isn't accidentally overwritten by another user.
    Session 1
    SELECT's a value of 5
    Session 2
    SELECT's a value of 5
    UPDATE's the value to 6
    COMMIT's
    Session 1
    UPDATE's the value to 7 <- most applications want to tell User 1 that he is overwriting someone else's changes here
    COMMIT's
    If you have an application where people open a record, work with it for a minute, and then save, there is plenty of opportunity for someone else to change the data before the user saves. Allowing the user to overwrite changes he's never seen is often a bad thing-- the user whose changes were overwritten often gets upset if they have to redo their work.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

Maybe you are looking for

  • DME File not Generating

    Hi Experts,                 Is there any authorization required for the generation of the DME file after we run the automatic payment program?. 1. The open line items are cleared once the APP is run. 2. checked for the dme file using the AL11, But no

  • Help, my account is blocked.

    My account is blocked, please help me  Subject/title expanded to provide more detail.

  • Release Repetitive code in OT81

    Hi All, Have 2 scenario; 1. Create Repetitive code in 0T81 and required 2 person to release the repetitive code 2. Copy repetitive code in OT81 only required 1 person to release. Regards to the above scenario ; When we create repetitive code in OT81

  • Line on top of text box

    I got a nice photo book printed out but on top of any page with a long text box there is a horizontal line atop the heading for that text panel.... I thought it was just a visual anomoly in the app but it actually PRINTED that way and now I've got a

  • HP Officejet Pro 8600 Plus AIO automatic document feeder paper jam.

    While scanning a smaller document using the ADF, it got jammed in the feeder. While recovering the document, a corner of the document got torn and got stuck in the document feeder. Now, every time I use the feeder to scan a document again, that docum