Clarity

Expand all | Collapse all

Warnings in bg.log for process engine

Jump to Best Answer
  • 1.  Warnings in bg.log for process engine

    Posted 06-10-2016 03:18 PM

    Hi all.

       I am seeing warnings such as this in my bg.log on our process engine server:

     

    WARN  2016-05-31 08:38:50,430 [Event Handler pool-4-thread-4] bpm.eventmgr (clarity:thor30:13070331__C5D60339-E33D-4C7B-BA82-551BF7C5DE6F:none) User that created event does not have the right to start process. processID: 5004058 userId: 5004322

     

    To investigate, is there a query that I can input the process ID into to see what isn't happening?



  • 2.  Re: Warnings in bg.log for process engine

    Posted 07-29-2016 01:01 PM

    A big problem is that these errors sometimes are produced too frequently

     

    A real example of 142 warning messages produced by an event in a very short period of time (from 12:09:59,644 to

    12:10:13,920)

     

    Though the total number of messages with same error is much bigger because it was for a longer time being written.

    Why warning is written so continuously?

     

    is there a timeout for this type of problems to avoid fullfilling the log files and impact in performance?

     

     

    Part of the log for the previous period.

     

    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:09:59,700 [Event Handler pool-3-thread-3] 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,700 [Event Handler pool-3-thread-3] 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,733 [Event Handler pool-3-thread-1] 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,733 [Event Handler pool-3-thread-1] 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,746 [Event Handler pool-3-thread-10] 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,746 [Event Handler pool-3-thread-10] 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:00,035 [Event Handler pool-3-thread-10] 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:00,035 [Event Handler pool-3-thread-10] 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:00,083 [Event Handler pool-3-thread-5] 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:00,083 [Event Handler pool-3-thread-5] 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

    WARN  2016-07-18 12:10:13,920 [Event Handler pool-3-thread-1] 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,920 [Event Handler pool-3-thread-1] bpm.eventmgr (clarity:user1:000000:none) User that created event does not have the right to start process. processID: 5001000 userId: 5051001



  • 3.  Re: Warnings in bg.log for process engine
    Best Answer

    Broadcom Employee
    Posted 06-13-2016 06:23 PM

    Hi Robert,

     

    This error message means that the user with the id mentioned in the error has performed an action that would normally launch an instance of the process mentioned in the error.  However he does not have the right to start that process.  So the process never launched in this case.  The process id in this error is the process version id.

     

    Please feel free to let me know if you need any additional information.

     

    Sincerely yours,

     

    Jeanne Gaskill

    Senior Support Engineer - CA PPM



  • 4.  Re: Warnings in bg.log for process engine

    Posted 06-13-2016 05:35 AM

    Hi Robert,

     

    You can view the process in clarity :

    https://CAPPM_URL/niku/nu#action:bpm.processDefinitionProperties&process_version_id=5004058

    does that help you?



  • 5.  Re: Warnings in bg.log for process engine

    Posted 06-13-2016 10:07 AM

    Thanks Davor - this does get me to the process. This is an auto start process on the project object that appears to be functioning properly - not sure what all of these log warnings are. I guess if no one is reporting trouble...