[DM_E_COMPUTE_PERFORMER] error

Hi,

Sympton: randomly (most of time it's ok) we met error like subject. and the performer of the activity explained like below.

1. workflow: we named it as "WF1"

2. automation activity : we named it as "AA1"

3. manual activity: we named it as "MA1"

4. the workflow simply like that : start --> AA1 --> MA1 --> ......

5. error randomly happened while AA1: workitem.complete()

6. the whole error log like below I pasted.

7. The performer of MA1 is an alias, let me explained below:

7.1 WF1.packages.package(0) <== we called it, Form1

7.2 There's an alias called "Co-Sign" in Form1's aliasset. Right before workflow running, we already set the alias with value of a group, for example, like "Form1_cosigner_group", and the cosigner put in the group at same time.

8. AA1 runs a method, implements "WorkflowMethod". (what's it's done is not related to MA1. We tried removed all statements inside doTask(), still remains randomly error.)

We have done something trying to find out why, only one way success, but it's not really the result we want. Let me describe like below.

(1) Remove all statements inside doTask(), only "return 0" left. ==> not work, still randomly error.

(2) Choose another java method system provided like "dm_noop_auto_method_java" ==> not work, still randomly error.

(3) Set the performer of "MA1" as a specific user ==> no error, but that's not logic what we want.

(4) Set the performer of "MA1" as picked from process data (variable), and we setup the variable with group of "Form1_cosigner_group" in AA1 ==> not work, still randomly error.

(5) Change method type inside "AA1" from "java" to "program", and rewrite the workflowmethod as java program, and launched by an independant JVM ==> it works, but it still not what we want. If every time step workflow go through we have to launch a JVM, it consumes terrible resource, and much slower.

It's a weird problem and maybe no one experienced. But hopely there's some expert could help me dig more. I knew DfWorkItem.complete() triggered a RPC call, and the call is fail. But unfortunately, in below logs, there's nothing to say what really happen inside that RPC call, and I don't know where the RPC call is executed and where to find the log or turn the trace-info on.

It would be very appreciate if some expert could tell me why or let me know where to find more logs of it.

DfException:: THREAD: http-0.0.0.0-9060-5; MSG: [DM_WORKFLOW_E_COMPUTE_PERFORMER]error: "Failed to compute performers for activity 'Co-sign' (1) of the workflow (4d00000b8001d9c8)."; ERRORCODE: 100; NEXT: null

at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57)

at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(MessageEntry.java:39)

at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getException(DocbaseMessageManager.java:137)

at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.checkForMessages(NetwiseDocbaseRpcClient.java:305)

at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.applyForBool(NetwiseDocbaseRpcClient.java:349)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection$1.evaluate(DocbaseConnection.java:1076)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.evaluateRpc(DocbaseConnection.java:1014)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.applyForBool(DocbaseConnection.java:1069)

at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.apply(DocbaseConnection.java:1054)

at com.documentum.fc.client.impl.docbase.DocbaseApi.witemComplete(DocbaseApi.java:1191)

at com.documentum.fc.client.DfWorkitem.completeEx2(DfWorkitem.java:503)

at com.documentum.fc.client.DfWorkitem.completeEx(DfWorkitem.java:497)

at com.documentum.fc.client.DfWorkitem.complete(DfWorkitem.java:491)

at com.documentum.bpm.DfWorkitemEx___PROXY.complete(DfWorkitemEx___PROXY.java)

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

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

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

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:710)

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

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:230)

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

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

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

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

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

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

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

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

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

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

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

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

DfException:: THREAD: http-0.0.0.0-9060-5; MSG: [DM_WORKFLOW_E_WORKITEM_TRANSITION]error: "Workitem (4a00000b8002601b) fails to make the state transition."; ERRORCODE: 100; NEXT: DfException:: THREAD: http-0.0.0.0-9060-5; MSG: [DM_WORKFLOW_E_ACTION_NOT_ALLOWED]error: "This operation is not allowed when the state is 'finished' for workitem '4a00000b8002601b'."; ERRORCODE: 100; NEXT: null