add DEBUG level logging for
org.apache.activemq.broker.jmx.ManagedRegionBroker and you will get a
stack trace for the mbean registration failure. that may help diagnose
On 16 June 2014 19:31, Geurt Schimmel <gschim...@schubergphilis.com> wrote:
> Hi,
>
> After upgrading from 5.9 to 5.10.0, it's not as stable anymore as it used to
> be: after a day without any log-entries, I suddenly get 'Failed to register
> MBean....':
>
>
> 2014-06-15 21:01:55,772 | INFO | Started responder end of duplex bridge
> BrokerLinkXxxmmon4ToXxxxdb1@ID:xxxmmon4-39389-1402857158840-0:1 |
> org.apache.activemq.broker.TransportConnection | ActiveMQ Transport:
> ssl:///192.168.176.84:47269
> 2014-06-15 21:01:55,772 | INFO | Network connection between
> vm://localhost#23364 and ssl:///192.168.176.84:47269 (localhost) has been
> established. | org.apache.activemq.network.DemandForwardingBridgeSupport |
> triggerStartAsyncNetworkBridgeCreation:
> remoteBroker=ssl:///192.168.176.84:47269, localBroker= vm://localhost#23364
> 2014-06-16 17:34:13,957 | WARN | Failed to register MBean
> org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Topic,destinationName=ActiveMQ.Advisory.TempQueue_ActiveMQ.Advisory.TempTopic,endpoint=Consumer,clientId=ID_savxdb1-26710-1402857684846-3_27600,consumerId=ID_xxxxdb1-26710-1402857684846-4_27600_-1_1
> | org.apache.activemq.broker.jmx.ManagedRegionBroker | ActiveMQ VMTransport:
> vm://localhost#55207-1
> 2014-06-16 17:34:13,957 | WARN | Failed to register MBean
> org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Topic,destinationName=ActiveMQ.Advisory.TempQueue_ActiveMQ.Advisory.TempTopic,endpoint=Consumer,clientId=ID_savxdb1-26710-1402857684846-3_27600,consumerId=ID_xxxxdb1-26710-1402857684846-4_27600_-1_1
> | org.apache.activemq.broker.jmx.ManagedRegionBroker | ActiveMQ VMTransport:
> vm://localhost#55207-1
>
> The ActiveMQ process is still there, but the JMX-listener has died without
> any trace.
>
> The network-connector between this machine and Xxxmmon4 is set up by Xxxmmon4
> (reason why duplex is "true"):
>
> <networkConnector name="BrokerLinkXxmmon4ToXxxxdb1" userName="system"
> password="${activemq.password}"
> uri="static:(ssl://xxxxdb1:61616?wireFormat.maxInactivityDuration=0)?useJmx=true"
> dynamicOnly="false" staticBridge="true" networkTTL="3"
> decreaseNetworkConsumerPriority="true" duplex="true">
> <staticallyIncludedDestinations>
> <queue physicalName="LOCAL.ORATK"/>
> </staticallyIncludedDestinations>
> </networkConnector>
>
> Any clues ?
>
> Thanks,
> Geurt
--
http://redhat.com
http://blog.garytully.com
