Menu

#1731 Calculate Capacity Plan run backward lock

closed-fixed
CRP (4)
9
2009-03-18
2009-01-30
Ioan Bogdan
No

Test case:

Run Calculate Capacity Plan process with parameter Schedule Type = Backward. The process never end.
Here the console log for a resource that end in 1997 and continue.

Query.buildSQL: TableName = S_ResourceUnAvailable...
SQL = SELECT AD_Client_ID,AD_Org_ID,Created,CreatedBy,DateFrom,DateTo,Description,IsActive,S_ResourceUnAvailable_ID,S_Resource_ID,Updated,UpdatedBy FROM S_ResourceUnAvailable WHERE (DateFrom <= ? AND S_Resource_ID=? AND AD_Client_ID=?) ORDER BY DateFrom DESC [17]
17:55:33.581 CRP.scheduleBackward: --> dayStart=1997-05-26 01:17:00.0, dayEnd=1997-05-26 00:50:00.0 [17]
17:55:33.581 CRP.scheduleBackward: --> availableDayDuration -1620000 [17]
17:55:33.581 CRP.scheduleBackward: --> availableDayDuration >= nodeDuration false -1620000|7228300000 [17]
17:55:33.581 CRP.scheduleBackward: --> nodeDuration-availableDayDuration 7229920000 [17]
17:55:33.581 CRP.scheduleBackward: --> end=1997-05-25 00:00:00.0 [17]
17:55:33.581 CRP.scheduleBackward: --> nodeDuration=7229920000 [17]

In this point I terminate the process from Eclipse.

Best regards,

Ioan Bogdan - www.arhipac.ro

Discussion

  • Ioan Bogdan

    Ioan Bogdan - 2009-01-30
    • priority: 5 --> 9
    • assigned_to: nobody --> vpj-cd
     
  • Victor Perez Juarez

    Hi Ioan Bogdan.

    Can you review the duration time , the setup time and the Duration Units that you is using in Workflow Manufacturing, also is necessary review the Resource Type. if you have mad parameter then the process can take a lot time.

    Kind regards
    Victor Perez
    www.e-evolution.com

     
  • Ioan Bogdan

    Ioan Bogdan - 2009-02-01

    I thought that it is related to the durations term. But in production, where we uses hundreds of resources I think it is very difficult to cover all data in case of errors. More nor realize what happened when the process end with an NPE. I think that there should be a validation process to alert the user for bad resources or workflow.

    Best regards,

    Ioan Bogdan - www.arhipac.ro

     
  • Teo Sarca

    Teo Sarca - 2009-02-02
    • summary: Calculate Capacity Plan run backward --> Calculate Capacity Plan run backward lock
    • status: open --> pending-fixed
     
  • Teo Sarca

    Teo Sarca - 2009-02-02

    Hi guys,

    The issue was when S_Resource.TimeSlotStart > S_Resource.TimeSlotEnd. I've corrected by validating in CRP engine.

    > Can you review the duration time , the setup time and the Duration Units
    > that you is using in Workflow Manufacturing, also is necessary review the
    > Resource Type. if you have mad parameter then the process can take a lot
    > time.

    Victor, there is no excuse for a process to take infinite time. More, if you have a lot of resources, resource types and workflows it's hard (i.e. impossible) to validate all these...
    We need to validate all possible errors and throw proper exceptions.
    I've corrected this "TimeSlotStart > TimeSlotEnd", do you know any other possible issues ?

    Best regards,
    Teo Sarca - www.arhipac.ro

     
  • Victor Perez Juarez

    Teo, I am agree but the process engineer need validate before each Manufacturing Workflow before the use :-)

    so , define a hide parameter do not is nice for me I think we can use the horizontal planning or before and after floating.

    The other import feature for process engineer will be can execute some simulation process this way can valdiate if the time is right with real process. can be that we use the Editor workflow to run a simulate process but this required some development.

    the other current issue the CRP is infinity capacity , the reason is because current the system do not validate the available capacity to distribute the load only when is available.

    Kind regards
    Victor Perez
    www.e-evolution.com

     
  • SourceForge Robot

    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 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-fixed --> closed-fixed
     

Log in to post a comment.