Problem
- Product Name: Borland Enterprise Server
- Product Version: 5.2.1
- Product Component: SonicMQ
- Platform/OS Version: All
- JDK/Compiler Version: JDK 1.3.1
SonicMQ Broker exits when the database connection is lost.
Resolution
The SonicMQ Broker treats all SQLExceptions as fatal and therefore will exit if there is a connection loss to the Broker"s backend database. This causes SonicMQ Broker to be NOT able to support database fail over strategies such as Oracle FailSafe.
It is possible in Borland Deployment Op Center 6.0 and later to manage the SonicMQ Broker so that it will restart if there is a failure.
#Security
#failsafe
#VisiBroker
#SonicMQ
#SQLException
#BES
#5.2.1
