Clarity

Expand all | Collapse all

Event and continuos attempts to launch a process in bg

  • 1.  Event and continuos attempts to launch a process in bg

    Posted 09-15-2016 12:27 PM

    When a resource has generated an event but he hasn't enough rights to execute an autostart process then the process engine try to execute it and produces a warning message in logs, but it is not registered in process instances. It could be an expected behavior.

     

    However, it seems that  parameters for re-attempt must have something wrong (maybe a defect),  because the system tries  too many times and in a very short interval of time producing high impact on log files and in performance.

     

     

     

    1st real example from bg-ca.log (Clarity v14.2)  with  142 warning messages produced by an event in a very short period of time (from 12:09:59,644 to 12:10:13,920)

     

    WARN  2016-07-18 12:09:59,654 [Event Handler pool-3-thread-9] bpm.eventmgr (clarity:user1:000000:none) User that created event does not have the right to start process. processID: 5001000 userId: 5051001

    WARN  2016-07-18 12:09:59,687 [Event Handler pool-3-thread-15] bpm.eventmgr (clarity:user1:000000:none) User that created event does not have the right to start process. processID: 5001000 userId: 5051001

    WARN  2016-07-18 12:09:59,687 [Event Handler pool-3-thread-15] bpm.eventmgr (clarity:user1:000000:none) User that created event does not have the right to start process. processID: 5001000 userId: 5051001

    .......

    ...........

    .......

    .......

    .......

    WARN  2016-07-18 12:10:13,918 [Event Handler pool-3-thread-11] bpm.eventmgr (clarity:user1:000000:none) User that created event does not have the right to start process. processID: 5001000 userId: 5051001

    WARN  2016-07-18 12:10:13,918 [Event Handler pool-3-thread-11] bpm.eventmgr (clarity:user1:000000:none) User that created event does not have the right to start process. processID: 5001000 userId: 5051001

     

    2nd real  example, an update event  and from  NMS_MESSAGES table,  fields SEND_DATE and EXPIRATION_DATE have 2 hours of difference. is this the timeout #1? will it be re-processed after this expiration time?

     

    table NMS_MESSAGES

     

    #1 in logs the last message is from 20:24:33, what is later than the expected expiration date.

     

    WARN  2016-09-15 20:24:33,426 [Event Handler pool-3-thread-2] bpm.eventmgr (clarity:user4:000000:none) User that created event does not have the right to start process. processID: 5001000 userId: 5000112

    On the other hand in previous screenshot there are two update entries, but i cannot confirm if the user generated two events in this short interval of time or if both entries were generated by  the same event (a duplicate)?

     

    Anyway, for an single event i can in NMS_MESSAGE_DELIVERY more than 900 entries in an hour

     

    NMS_MESSAGE_DELIVERY

     

     

    What is the default behavior of the process engine?

    Why warning messages are written so continuously?

    is this a defect or a configuration problem?

     

     

    this post has some relation with the following question:

    Warnings in bg.log for process engine 



  • 2.  Re: Event and continuos attempts to launch a process in bg

    Posted 04-11-2017 08:51 PM

    Hi dapg, do you have any update for the behavior? I have the same problem, that problem affect the PPM performance and maybe some process execution.