#4548 Workflow failed

R2.6.0
closed
9
2007-10-02
2007-08-17
ADAXA
No

The workflow process generated by completing shipment ran for over 40 minutes and had to be aborted by user.

The particular Shipment contains around 330 lines, is it possible there might be a threshold as to how many workflow process/activities can be running?

We suspect this was happening when more than 1 user tried to complete a large shipments at almost the same time.

Once these 'running' process been stopped and tried completing these shipments again, the work flow seems to complete normally.

Message taken debug screen is shown below:

OnlineHelp.Worker.run (e) java.lang.NullPointerException
-----------> MInOut.lock: failed [11]
-----------> MWorkflow.startWait: Timeout after sec 15 [11]
-----------> MLookup.run: AD_WF_Process.AD_WF_Process_ID: Loader - Too many records [12]

Discussion

  • Kathy Pink

    Kathy Pink - 2007-08-17
    • assigned_to: kmpink --> sboda
     
  • sboda

    sboda - 2007-08-18

    Logged In: YES
    user_id=1705860
    Originator: NO

    Reviewing

     
  • sboda

    sboda - 2007-08-23

    Logged In: YES
    user_id=1705860
    Originator: NO

    Hi,

    I could not able to reproduce this problem in 2.6.1(I have tried with 500 shipment lines).
    Is it happening every time or just 1 time happened? How about in 2.6.1? And what is your delivery rule?

    Thanks,
    Sabitha

     
  • sboda

    sboda - 2007-08-23
    • status: open --> pending
     
  • sboda

    sboda - 2007-08-23

    Logged In: YES
    user_id=1705860
    Originator: NO

    *** Status set to PENDING *** If the issue solved, please CLOSE
    this request - otherwise set the status back to OPEN (we only
    check OPEN items). If there is no reaction within a week, the
    system will automatically CLOSE it. To speed up response time,
    you may want to consider a support agreement.
    ***

     
  • ADAXA

    ADAXA - 2007-08-28

    Logged In: YES
    user_id=1039991
    Originator: YES

    Delivery rules were set to Availability.

    The problem been happening intermittently and just yesterday there been another reported incident on a shipment containing only 1 line.

    Also, should we be concerned with this warning message?
    -----------> MLookup.run: AD_WF_Process.AD_WF_Process_ID: Loader - Too many records

    I will try to reproduce this on 2.6.1 as it is currently running on 2.6.0

     
  • ADAXA

    ADAXA - 2007-08-28
    • status: pending --> open
     
  • sboda

    sboda - 2007-08-29

    Logged In: YES
    user_id=1705860
    Originator: NO

    Investigating

     
  • Yves Sandfort - Compiere EMEA

    • priority: 5 --> 9
     
  • Yves Sandfort - Compiere EMEA

    Logged In: YES
    user_id=1784395
    Originator: NO

    raised to highest prio as per int. discussion!

     
  • sboda

    sboda - 2007-08-31

    Logged In: YES
    user_id=1705860
    Originator: NO

    Could you able to send the whole log file?

     
  • ADAXA

    ADAXA - 2007-09-10

    Logged In: YES
    user_id=1039991
    Originator: YES

    Logging been enabled. Will contribute log once we see this happening again.

     
  • ADAXA

    ADAXA - 2007-09-10

    Logged In: YES
    user_id=1039991
    Originator: YES

    *** Status set to PENDING *** If the issue solved, please CLOSE
    this request - otherwise set the status back to OPEN (we only
    check OPEN items). If there is no reaction within a week, the
    system will automatically CLOSE it. To speed up response time,
    you may want to consider a support agreement.
    ***

     
  • ADAXA

    ADAXA - 2007-09-18

    Logged In: YES
    user_id=1039991
    Originator: YES

    File Added: javaws20059.zip

     
  • ADAXA

    ADAXA - 2007-09-18

    java log 18/09/2007

     
  • ADAXA

    ADAXA - 2007-09-18

    Logged In: YES
    user_id=1039991
    Originator: YES

    In regard to the attached JAVA log, it was reported by user that while completing a shipment, it seemed to time-out and left the shipment at "In-Progress" state, also the workflow continued to run and eventually had to be aborted. About 5 minutes later, the application was restarted then the shipment could be completed normally.

    I hope this help with the investigation.

     
  • sboda

    sboda - 2007-09-19

    Logged In: YES
    user_id=1705860
    Originator: NO

    Reviewing

     
  • sboda

    sboda - 2007-09-24
    • assigned_to: sboda --> lfreyes
     
  • Felipe Reyes

    Felipe Reyes - 2007-09-24

    Logged In: YES
    user_id=1793135
    Originator: NO

    Have you been able to reproduce this issue after applying the code changes that were sent on Thursday (Sep 20)? (bug 1744930)

     
  • Felipe Reyes

    Felipe Reyes - 2007-09-24
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 7 days (the time period specified by
    the administrator of this Tracker).

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks