ODB Service taking more time to start - OBM 2018.02
We have OBM 2018.02 version installed on a single machine with Embedded PostgreSQL database.
For the past two weeks, I notice the incoming message to OBM and the other functions are getting hang until we restart the server & OBM application. The operation agent on the server is not showing the agent status and after some time it's showing as message agent is buffering.
During the Application restart, the services taking more time to stop & start. Especially ODB service is taking more than 1 hour to start.Also we are getting an internal OMI health message as "Server.handlePacket(505) - AMQ224016 Caught exception"
Please suggest your comments.
Re: ODB Service taking more time to start - OBM 2018.02
- Have you checked if OBM has enough resources to process the incoming messages to OBM? I mean CPU/Memory/Heap memory.
- Do you have too many event correlations/ETI scripts enabled?
- At the same time, I recommend to track on which lifecycle stage your events are getting slow down... maybe there is something causing the bottleneck, so if you need to see where is your incomming message and how much time OMi took to process an event, you can enable the DEBUG Level for backend on DPS:
In case tracing is enabled, you will see more details in below log files:
GW --> <OMi>\log\wde\opr-gateway-flowtrace.log
DPS --> <OMi>\log\opr-backend\opr-flowtrace-backend.log
You can check the time stamp when the event lifecycle was updated. This way you can calculate time consumed bo OMi in each Event stage.