IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Process instance stuck after workflow task is completed

    Posted Fri May 02, 2008 01:29 PM

    hi,

    I am using MwS 7.0 with task engine.

    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 workflow task, task gets queued and I accept and complete the task. While looking at the process instance steps, it says task 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)</null></null></null></null>
    

    #BPM
    #webMethods
    #webMethods-BPMS


  • 2.  RE: Process instance stuck after workflow task is completed

    Posted Fri October 23, 2009 09:30 AM

    Hi All,

    Facing the same problem,
    Can some one tell me what would be the resolution for this?

    Thanks in advance,
    Aparna


    #webMethods
    #webMethods-BPMS
    #BPM


  • 3.  RE: Process instance stuck after workflow task is completed

    Posted Wed January 13, 2010 11:11 AM

    Do you have any error message in IS’s log ?

    I got a similar problem, with a “insufficient credentials” error in IS’s log.
    I had to enter the right user/password in system settings > task engine settings.

    I guess MWS coudln’t connect to the IS to update the process.


    #webMethods-BPMS
    #BPM
    #webMethods


  • 4.  RE: Process instance stuck after workflow task is completed

    Posted Tue May 22, 2018 04:49 AM

    Facing the same, process stuck just after “receive” task step - no errors found in IS’s log.


    #webMethods-BPMS
    #webMethods
    #BPM


  • 5.  RE: Process instance stuck after workflow task is completed

    Posted Tue May 22, 2018 10:11 AM

    Could you try to restart UniversalMessaging and after that reload WmPRT package on IntegrationServer.


    #webMethods
    #webMethods-BPMS
    #BPM


  • 6.  RE: Process instance stuck after workflow task is completed

    Posted Tue May 22, 2018 11:01 AM

    Thx for suggestions Slawomir :wink:

    After changing debug log level I’ve found entry:

    UMConnectionAlias - Channel Lookup: wm::is::wm::prt::dispatch::ProcessTransitionVol
    UMConnectionAlias - Did Not Get Descriptor for channel: wm::is::wm::prt::dispatch::ProcessTransitionVol

    Dropping appropriate queue on UM: umserver/wm/is/wm/prtdispatch/ProcessTransitionVol

    and syncing document types on WmPRT/wm/prt/dispatch/ProcessTransitionVol

    helped in my case


    #BPM
    #webMethods-BPMS
    #webMethods