[
https://issues.apache.org/jira/browse/AMQ-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017304#comment-13017304
]
Oleg Kiorsak commented on AMQ-1780:
-----------------------------------
I also see a message in teh log that might explain why transport connections
don't get restarted:
[mdtapdot01]# WARN | Failure occurred while restarting broker connectors
java.io.IOException: Transport Connector could not be registered in JMX:
org.apache.activemq:BrokerName=MobTechTest1,Type=Connector,ConnectorName=openwire
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
at
org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1670)
at
org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2159)
at
org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2073)
at
org.apache.activemq.util.DefaultIOExceptionHandler$2.run(DefaultIOExceptionHandler.java:99)
Caused by: javax.management.InstanceAlreadyExistsException:
org.apache.activemq:BrokerName=MobTechTest1,Type=Connector,ConnectorName=openwire
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482)
at
org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:299)
at
org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:65)
at
org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1667)
... 3 more
[mdtapdot01]#
> ActiveMQ broker does not automatically reconnect if the connection to the
> database is lost
> ------------------------------------------------------------------------------------------
>
> Key: AMQ-1780
> URL: https://issues.apache.org/jira/browse/AMQ-1780
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0
> Environment: Windows 2003 Server
> Reporter: Jaya Srinivasan
> Assignee: Gary Tully
> Fix For: 5.5.0
>
>
> hi
> We are noticing that after any SQL Server restart or network blip between
> ActiveMQ and the database, after the connection or the database comes back
> online activeMQ broker needs to be restarted as well i.e it doesn't
> automatically re-establish connection to the database as result any message
> send fails because the broker is still using the stale connection to the
> database.
> Is this designed behaviour or a bug? we are using ActiveMQ 5.0.0 and the
> latest version of the JSQLConnect database driver: version 5.7. The database
> we are using is MS SQL Server 2005
> Right now, in our production environment any time we have network maintenance
> or database restart we also have to restart the ActiveMQ broker which is not
> a good option for us.
> Also, We are using a single ActiveMQ broker and not the JDBC(Master/Slave)
> set up.
> Issue details in
> http://www.nabble.com/Database-connection-between-ActiveMQ-and-broker-td17321330s2354.html
> Please let me know if I need to give more information
> thanks
> jaya
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
