[
https://issues.apache.org/jira/browse/AMQ-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256768#comment-16256768
]
Gary Tully commented on AMQ-6862:
---------------------------------
some combination of a smart connection pool that will verify connections and
some tweaks to the iOExceptionHandler[1] handler may be what you need. I think
the broker is currently stopping on the first occurrence of that exception.
see:
https://github.com/apache/activemq/blob/c7291f1ecfefec7aad6fcf168e298e2ef0af8ed7/activemq-broker/src/main/java/org/apache/activemq/util/DefaultIOExceptionHandler.java#L83
> ActiveMQ Broker Not able to reconnect to MSSQL HA during Failover
> -----------------------------------------------------------------
>
> Key: AMQ-6862
> URL: https://issues.apache.org/jira/browse/AMQ-6862
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.14.0
> Environment: Platform : Windows Server 2012 R2
> ESB : Mulesoft Server
> ActiveMQ 5.14.0
> MSSQL Server HA Clustered(Primary and Secondary)
> Reporter: Bharath Mohan
> Priority: Critical
> Fix For: 5.14.0
>
>
> Active MQ 5.14.0 loses connection to Database that is persisted on MS SQL
> database.
> Mulesoft reads the file and sends them as messages to topic
> This messages are taken for transformation and written as file to target
> When failover occurs from primary to secondary in HA DB cluster
> The messages that are enqueued are not dequeued as the DB connection is
> closed.
> Could you please check the attached mq xml file and let us know why activemq
> not able to reach the secondary node when failover occurs.
> Does ActiveMQ supports MSSQL HA DB.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
