Ensuring BPM Events server starts after JMS server is started
You must ensure that you start BPM Events server only after JMS server is started. BPM Events provides the following two parameters in the %OEBPS_HOME%\conf\bpmevents.conf file to help you achieve this.
bpmevents.server.jms.init.max.retry.count
Before starting BPM Events server, it checks whether JMS server is started and is accessible or not. The value of this parameter specifies how many times BPM Events server can check this.
bpmevents.server.jms.init.retry.interval
Before starting BPM Events server, it checks whether JMS server is started and is accessible or not. The value of this parameter specifies the duration (in milliseconds) between two successive checks.
bpmevents.server.jms.init.max.retry.count