Clarity PPM

Expand all | Collapse all

Error in bg-ca.log after upgrade to 15.3

  • 1.  Error in bg-ca.log after upgrade to 15.3

    Posted 05-22-2018 03:54 AM

    After upgrading from 14.3 to 15.3, we are getting lots of below error messages in bg-ca.log:

     

    ERROR 2018-05-22 02:25:40,647 [NMS Message Receiver (tenant=clarity)] bpm.eventmgr (clarity:none:none:none) Error in onMessage.
    java.util.concurrent.RejectedExecutionException: Task com.niku.bpm.eventmgr.ObjectEventHandler@2182e4c rejected from java.util.concurrent.ThreadPoolExecutor@7bb95929[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 86105]
    at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047)
    at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823)
    at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369)
    at com.niku.bpm.eventmgr.BusinessProcessEventManagerImpl.onMessage(BusinessProcessEventManagerImpl.java:687)
    at com.niku.bpm.eventmgr.messageserver.MessageServerImpl.processMessages(MessageServerImpl.java:1258)
    at com.niku.bpm.eventmgr.messageserver.MessageServerImpl.runMessageReceiver(MessageServerImpl.java:1201)
    at com.niku.bpm.eventmgr.messageserver.MessageServerImpl.access$100(MessageServerImpl.java:52)
    at com.niku.bpm.eventmgr.messageserver.MessageServerImpl$1.run(MessageServerImpl.java:158)
    at java.lang.Thread.run(Thread.java:745)
    Although all GUI jobs and processes are running fine, but need to know what is causing this error to show up in bg logs.


  • 2.  Re: Error in bg-ca.log after upgrade to 15.3

    Posted 05-22-2018 07:28 PM

    Hi Piyush 

     

    With 15.3 there is a new feature where the BPM_ERRORS table is backed up and cleared out. So, I don't suspect that you would have any completed or old process instances lying in the system. But just in case, check those and delete them.

     

    Also, restart the BG service and check if the Errors still come up. 

     

    If you still get the errors, you can raise a case with CA support and we could try to find the cause. 

     

    Thanks

    Shailey