Bharath, I looked at the code that handles the connections to various different database types ( https://github.com/apache/activemq/tree/master/activemq-jdbc-store/src/main/java/org/apache/activemq/store/jdbc/adapter). I see specialized subclasses (which handle certain non-standard behaviors) for a number of database types, including Oracle, MySQL, DB2, Sybase, etc. I don't see one for MSSQL, which means that MSSQL uses DefaultJDBCAdapter and there's no attempt to capture the MSSQL-specific logic of needing to reconnect when you receive that specific exception.
So in summary, it appears that although MSSQL is supported, the HA features of MSSQL are not, and you should submit an enhancement request in JIRA to ask for that feature to be added. Tim On Nov 13, 2017 3:49 AM, "BharathMohan" <baratmo...@gmail.com> wrote: > Hi Tim, > > Thanks a lot for the response. > > To add more detail to the issue > 1.) ESB Server is single instance that connects to Single instance of > Active > MQ. > 2.) This single Broker connects to MSSQL HA. > > I will submit the JIRA for this issue. > > Just wanted to confirm one thing from your reply "*MSSQL HA wasn't > supported*" > > Are you saying that ActiveMQ 5.14.0 *does not support MSSQL HA Cluster at > all*. > > > Thanks, > Bharath > > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
