Workflow step status is completed but process status is started

, ,
1

hi,
I am using MwS 7.0 with task engine & IS 6.5 SP3.
I am working on bootcamp exercise for WM 7.0.
I am successful in creation of a process model and it gets invoked by publishing the document. When it comes to a workflow task, task gets queued as it should. As per the process, I accept and complete the task.
While looking at the process instance steps, it task status is completed but the process status is still ‘started’ and next step after workflow task does not get executed.
Any idea about this issue?
Error I saw in MwS logs is:

2008-05-02 11:02:49 PDT (Framework : WARN) - [PRT.0101.9130] Error sending wm.prt.dispatch:ProcessTransitionVol: >>>BasicData:ProcessInstanceID=94dc87a0186f11dda8a99b3ce5d8f16a:1,ProcessModelID=MyProcess/MyFirstProcess,ProcessModelVersion=1,SourceStepID=PRETDE_S17,TargetStepID=POSTTDE_S17,SourceServerID=Default,Pipeline=[B@177a174< com.wm.app.b2b.server.ServiceException: [PRT.0101.9130] Error sending wm.prt.dispatch:ProcessTransitionVol: >>>BasicData:ProcessInstanceID=94dc87a0186f11dda8a99b3ce5d8f16a:1,ProcessModelID=MyProcess/MyFirstProcess,ProcessModelVersion=1,SourceStepID=PRETDE_S17,TargetStepID=POSTTDE_S17,SourceServerID=Default,Pipeline=[B@177a174< at com.wm.app.prt.EventPublish.tmSend(EventPublish.java:155) at com.wm.app.prt.EventPublish.sendTx(EventPublish.java:117) at wm.prt.tde.sendTransition(tde.java:111) at wm.prt.tde.tdeCallback(tde.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:322) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:612) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:235) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:198) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:411) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:521) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:369) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPInvokeHandler._process(HTTPInvokeHandler.java:131) at com.wm.app.b2b.server.InvokeHandler.process(InvokeHandler.java:119) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:312) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:595)

-Nilesh

2

hi ndgohel: I see the same error as you, could you please tell me how to solve this? thank you very much!

3

same problem for me too,can some one pls reply

Thanks in advance,
Aparna

4

aparnad
I solved this problem long time ago. this is because the task engine can’t access the process engine and can’t report the task complete message to process engine. So you should check if the connection is right or not in your mws system setting.

hope this can help you

5

Hi jacky_sx,

Thanks for the reply.
In mws system settings, I have given the username and password as Administrator and manage.But still I am getting the same error.

Do you see any other reasons for this?

6

the username and password is for process engine to connect to task engine. you should check your setting for Integration Server (Process Engine Host)

In my case, finally I found I provide wrong connection address
the address I input was http://localhost
but actually the right string is just “localhost”

If you are sure about the address, i am afraid you should check if process engine is running well.

7

Hi…

I have faced the same issue with the process and the task

The workaround i could find for the same is as below:

  1. Go to the developer and delete the process package which has been created initially.
    2.Go to Designer and delete the input /output steps for the tasks(As u can c the input and output with same as task name)
    3.Close the Designer and open again,so that you can see the input and output has been created automatically.
    4.Now build and upload the process.
    5.Check for the Result