Resolution:
If the JMS receiver/subscriber activity loses connection to the JMS server, it will first close all session objects and the connection object. After 10 seconds it will try to establish a connection, if successful it will recreate the connection and session objects.  But if the retry attempt on the 10th second is unsuccessful then JMS receiver/subscriber activity will retry every 60 seconds thereafter until it can successfully establish a connection to the JMS server.

As you see, there is a robust recovery mechanism in-built within JMS receiver/subscriber

There maybe a scenario where you are starting the BW engine(containing JMS process starters) and the JMS server is still not up. This is different from the scenario described above where the JMS process starters have already established a connection to the JMS server during BW engine startup, but have lost the connection later on.
In such scenarios, set the following property to true :
bw.plugin.jms.recoverOnStartupError

This will allow the BW process engine to start and the JMS process starters will wait until the JMS sever is up before starting.