java.sql.SQLException: Transaction was deadlocked
(Doc ID 373137.1)
Last updated on FEBRUARY 03, 2019
Applies to:
Oracle(R) BPEL Process Manager - Version: 10.1.2.0.2 to 10.1.2.3.0 - Release: AS10gR2 toInformation in this document applies to any platform.
***Checked for relevance on 15-Sep-2010**
Symptoms
When running multiple processes in parallel the following exception occurs:
ORABPEL-04050
Cannot select delivery subscription.
The process domain was unable to select the delivery data for conversation "bpel://localhost/ahayes/SyncMultipleCallback~1.0/33462-BpInv0-BpSeq0.3-5" from the datastore. The exception reported is: Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
sql statement: SELECT conv_id, conv_type, cikey, domain_ref, process_id, revision_tag, process_guid, operation_name, subscriber_id, service_name, subscription_date, state, properties FROM dlv_subscription WHERE conv_id = ? AND state = 0 AND domain_ref = ?
at com.collaxa.cube.engine.adaptors.common.BaseDeliveryPersistenceAdaptor.getSubscriptionsByConvId(BaseDeliveryPersistenceAdaptor.java:1401)
at com.collaxa.cube.engine.adaptors.common.BaseDeliveryPersistenceAdaptor.getSubscriptionsByConvId(BaseDeliveryPersistenceAdaptor.java:1355)
at com.collaxa.cube.engine.data.DeliveryPersistenceMgr.getSubscriptions(DeliveryPersistenceMgr.java:257)
at com.collaxa.cube.engine.delivery.SOAPProtocolHandler.subscribe(SOAPProtocolHandler.java:73)
at com.collaxa.cube.engine.delivery.DeliveryService.subscribe(DeliveryService.java:239)
at com.collaxa.cube.engine.ext.wmp.BPELOnMessageWMP.perform(BPELOnMessageWMP.java:208)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836)
at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.handleWorkItem(CubeEngineBean.java:345)
at ICubeEngineLocalBean_StatelessSessionBeanWrapper0.handleWorkItem(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:1429)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2224)
at net.sourceforge.jtds.jdbc.TdsCore.isDataInResultSet(TdsCore.java:792)
at net.sourceforge.jtds.jdbc.JtdsResultSet.<init>(JtdsResultSet.java:146)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:424)
at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:693)
at com.evermind.sql.FilterPreparedStatement.executeQuery(FilterPreparedStatement.java:270)
at com.evermind.sql.FilterPreparedStatement.executeQuery(FilterPreparedStatement.java:270)
at com.collaxa.cube.engine.adaptors.common.BaseDeliveryPersistenceAdaptor.getSubscriptionsByConvId(BaseDeliveryPersistenceAdaptor.java:1387)
... 18 moreCause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms
Cause
Solution
References
Platforms: 1-914CU;
| This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |