Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#4548 Workflow failed

R2.6.0
closed
Felipe Reyes
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

1 2 3 > >> (Page 1 of 3)
  • 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

     
    • priority: 5 --> 9
     
  • Logged In: YES
    user_id=1784395
    Originator: NO

    raised to highest prio as per int. discussion!

     
1 2 3 > >> (Page 1 of 3)