Synchronous invoke process activity fails to run

Hello Experts,

We have documentum 6.7sp1 on RHEL 6.1.

I have created a dar file of some process template and moved them to another server. Again on this server we have RHEL 6.1 DM 6.7 sp1.

But the synchronous invoke activity fails on that environment. Do you know what can be the issue?

The error message is shown below.

Could not invoke child process <Create new SOProfile> in Process Template: 'Create new SSentToOrganization' - Activity: 'Create new organization profile'.

Workitem: '4a026c158000094b'

Workflow: 'Create new SSentToOrganization 2012-07-04' - '4d026c1580000917'

Activity: 'Create new organization profile' - '4c026c1580012297'

Process: 'Create new SSentToOrganization' - '4b026c1580012201'

DfException:: THREAD: http-0.0.0.0-9080-2; MSG: Could not invoke child process <Create new SOProfile>; ERRORCODE: ff; NEXT: null

at com.documentum.bps.syncsubproc.StartSubProcessUtils.startStatelessWorkflow(StartSubProcessUtils.java:46)

at com.documentum.bps.syncsubproc.runtime.StartSubProcessService.execute(StartSubProcessService.java:126)

at com.documentum.bpm.services.BPSIntegrationFramework.executeService(BPSIntegrationFramework.java:252)

at com.documentum.bpm.services.BPSIntegrationFramework.executeMethod(BPSIntegrationFramework.java:84)

at com.documentum.bpm.services.BPSIntegrationMethod.executeMethod(BPSIntegrationMethod.java:26)

at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:124)

at com.documentum.bpm.rtutil.GenericWorkflowMethod.execute(GenericWorkflowMethod.java:65)

at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)

at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)

at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)

at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)

at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)

at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)

at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)

at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)

at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)

at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)

at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

at java.lang.Thread.run(Thread.java:662)

Caused by: com.documentum.bpm.model.dao.ProcessModelDAOException: Error occured while reading process Create new SOProfilefrom Docbase

at com.documentum.bpm.model.dao.impl.ProcessModelDAO.read(ProcessModelDAO.java:154)

at com.documentum.bpm.model.dao.impl.ProcessModelDAO.read(ProcessModelDAO.java:127)

at com.documentum.bpm.model.dao.impl.SinglePassProcessModelDAOImpl.read(SinglePassProcessModelDAOImpl.java:51)

at com.documentum.bpm.engine.ProcessDefinitionDAO.loadProcessModel(ProcessDefinitionDAO.java:67)

at com.documentum.bpm.engine.ProcessDefinitionDAO.loadProcessModelByName(ProcessDefinitionDAO.java:59)

at com.documentum.bpm.engine.ProcessDefinitionDAO.addProcess(ProcessDefinitionDAO.java:50)

at com.documentum.bpm.engine.StatelessEngine.addProcess(StatelessEngine.java:70)

at com.documentum.bpm.engine.StatelessEngine.execute(StatelessEngine.java:65)

at com.documentum.bps.syncsubproc.StartSubProcessUtils.startStatelessWorkflow(StartSubProcessUtils.java:42)

... 32 more

Caused by: com.documentum.bpm.model.dao.ProcessModelDAOException: Error while loading Process Packages using activity: Link Profile To Folder

at com.documentum.bpm.model.docbase.DmProcessDataHandler.loadProcessPackageInfo(DmProcessDataHandler.java:324)

at com.documentum.bpm.model.docbase.DmProcessHandler.loadSkeletolActivities(DmProcessHandler.java:482)

at com.documentum.bpm.model.docbase.DmProcessHandler.loadProcessModel(DmProcessHandler.java:76)

at com.documentum.bpm.model.dao.impl.ProcessModelDAO.readInternal(ProcessModelDAO.java:383)

at com.documentum.bpm.model.dao.impl.ProcessModelDAO.read(ProcessModelDAO.java:148)

... 40 more

Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.documentum.bpm.adaptor.ProcessDataChangeAdapter

at com.documentum.bpm.model.process.impl.ProcessDataImpl.getPackage(ProcessDataImpl.java:167)

at com.documentum.bpm.model.docbase.DmProcessDataHandler.loadProcessPackageInfo(DmProcessDataHandler.java:312)

... 44 more

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Imran_Yusubov

Hello All,

The issue finally had been solved.

Known problems for Process Engine 6.7 SP1

The following table lists the known problems for Process Engine 6.7 SP1:

Defect # Description of known problems

BPM-6335 The execution of the synchronous invoke process activity fails in a Linux 6.1

environment. To avoid this issue, refer to Downloading EMF Runtime 2.6.1

and replacing relevant jars.

Additional information about known problems

Downloading EMF Runtime 2.6.1 and replacing relevant jars

Download EMF Runtime 2.6.1 from the Eclipse download site (http://eclipse.org/modeling/emf/

downloads/?project=emf) and use the following EMF jars in the Java method server in place of the

bundled 2.6.0 EMF jars, and restart the java method server:

• org.eclipse.emf.common_2.6.0.v20100914-1218.jar

• org.eclipse.emf.ecore.xmi_2.5.0.v20100521-1846.jar

• org.eclipse.emf.ecore_2.6.1.v20100914-1218.jar

Path to replace EMF jars: <DOCUMENTUM_SHARED_DIR>/jboss5.1.0/server/DctmServer_

MethodServer/deploy/bpm.ear/bpm.war/WEB-INF/lib

Names of jars from EMF 2.6.0 Runtime bundled in Process Engine 6.7 SP1 that must be replaced

with jars from EMF Runtime 2.6.1:

• org.eclipse.emf.common_2.6.0.v20100614-1136.jar

• org.eclipse.emf.ecore.xmi_2.5.0.v20100521-1846.jar

• org.eclipse.emf.ecore_2.6.0.v20100614-1136.jar

In addition if you are not using JMS activity templates, delete the the sibc.jms.jar from <DOCUMENTUM_SHARED_DIR>/jboss5.1.0/server/DctmServer_

MethodServer/deploy/bpm.ear/bpm.war/WEB-INF/lib.

That solves the issue.

All comments

DCTM_Guru

"...Could not invoke child process <Create new SOProfile>"

- Have you verified that the child process is installed? If so, then my guess is that the reference to the child process from within the parent process is hardcoded to object ID of the child of process and that the child process in the other server has a different object ID. Try opening up the parent process template and then "reassociate" the child process in the invoke process activity. This should update the object ID of the child process in that activity.

Imran_Yusubov

Hello Johnny,

of course I have checked and then cerated the discussion. The child process is running properly and installed, but it does not work from that activity. I opened the process templtes selected the process again no help.

DCTM_Guru

Have you verified the user has permissions to launch child process (maybe permissions are different from the parent process)?

Imran_Yusubov

Yes Johhny, also at least the error should indicate this.

Imran_Yusubov

I do remember that there was an issue related with the activity and had been fixed in one of documentum patches. But now I have checked all of them and cant find it. Is there any way to search the errors and fixes?

DCTM_Guru

Not that I am aware of. Worst case scenario - you can read the release notes for each of the patches. The release notes tells the issues that the patch is fixes.

Imran_Yusubov

Hello Guys,

Any help on this issue? We are still having the same problem, please help me to fix it.

Miller-zzMST

Hi Imran,

Could you invoke another process? Just for testing purposes: create a simple process1 and try to invoke it from another simple process2. Did you get it?

Second, try to create a simple process3 and try to invoke your process 'Create new SOProfile'.

Imran_Yusubov

Hello Konstantin,

The problem is not related to the process because the same process is working fine in several other environments.

But now I have no other idea so I will try what you are suggesting.

Imran_Yusubov

Ugh, no luck, again the some error occurs, but this seems a little differnt.

Could not invoke child process <Test child process> in Process Template: 'Test parent process' - Activity: 'Synchronous Invoke Process'.

Workitem: '4a026c1580003d05'

Workflow: 'Test parent process 2012-08-13' - '4d026c158000310a'

Activity: 'Synchronous Invoke Process' - '4c026c158001a1a4'

Process: 'Test parent process' - '4b026c158001a196'

DfException:: THREAD: http-0.0.0.0-9080-2; MSG: Could not invoke child process <Test child process>; ERRORCODE: ff; NEXT: null