UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.

BES 5.2.1 SonicMQ Broker exits when database connection is lost

BES 5.2.1 SonicMQ Broker exits when database connection is lost

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.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:22
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.