Callable Processes Referenced by More Than One Manual Process Cause Exceptions During Deployment
(Doc ID 1354166.1)
Last updated on FEBRUARY 03, 2019
Applies to:
Oracle Business Process Management Suite - Version 11.1.1.5.0 and laterInformation in this document applies to any platform.
Symptoms
When a Callable Process is called by more than one Manual Process, the application deployment fails with a unique constraint violation ORA-00001. The error is present when deploying composites with BPM flows that contain multiple calls to the same reusable task. Following error is seen in Jdeveloper:
Sending archive - sca_MultiProcessCall_rev1.0.jar
Received HTTP response from the server, response code=500
Invalid logging line: #;There was an error deploying the composite on AdminServer: Deployment Failed:
Error occurred during deployment of component: MyFirstProcess to service engine: implementation.bpmn, for composite: MultiProcessCall:
javax.ejb.EJBException: BEA1-6CDEF3415703C2D29F79: Local Exception Stack:
Invalid logging line: #;Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.1.3.v20110304-r9073):
org.eclipse.persistence.exceptions.DatabaseException
Invalid logging line: #;
Invalid logging line: #;Error Code: 1
Invalid logging line: #;Call: INSERT INTO BPM_CUBE_PROCESS (PROCESSID, ORGANIZATIONALUNITID, HASGLOBALCREATIONTASKS,
TARGETNAMESPACE, COMPOSITENAME, STATUS, SCALABEL, PROCESSNAME, LABEL, DOMAINNAME, COMPOSITEDN, PROCESSTYPE, CREATIONDATE,
SUBTYPE, REVISION, UNDEPLOYDATE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)
Invalid logging line: #; bind => [523, null, null, null, MultiProcessCall, 1, soa_a612103b-76f8-4942-8404-c0d47c546b23,
BAR, BAR, default, default/MultiProcessCall!1.0*soa_a612103b-76f8-4942-8404-c0d47c546b23, BPMN, 2011-07-20 11:41:25.016, CALLABLE, 1.0, null]
Invalid logging line: #;Query: InsertObjectQuery(CubeProcess(domain:default, composite:MultiProcessCall, revision:1.0, name:BAR, hasNametab:false))
Invalid logging line: #; at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:324)
Invalid logging line: #; at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:797)
Invalid logging line: #; at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:863)
Invalid logging line: #; at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:583)
Invalid logging line: #; at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:526)
Invalid logging line: #; at org.eclipse.persistence.internal.sessions.AbstractSession.executeCall(AbstractSession.java:980)
Invalid logging line: #; at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:206)
Invalid logging line: #; at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:192)
Invalid logging line: #; at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:341)
Invalid logging line: #; at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:162)
Invalid logging line: #; at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:177)
Invalid logging line: #; at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:465)
Invalid logging line: #; at org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:80)
Invalid logging line: #; at org.eclipse.persistence.queries.InsertObjectQuery.executeCommitWithChangeSet(InsertObjectQuery.java:90)
Invalid logging line: #; at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:290)
Invalid logging line: #; at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58)
Invalid logging line: #; at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:740)
Invalid logging line: #; at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:643)
...
Cause
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 |