subject:"\[jira\] \[Commented\] \(AMQ\-6052\) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations"

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-19 Thread Pablo Lozano (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15107363#comment-15107363
 ] 

Pablo Lozano commented on AMQ-6052:
---

This issue can also be worked around be setting on the networkConnector 
gcDestinationViews="false".

Although disabling the log level on that class avoids the huge log output it 
still creates a performance impact during the time where the issue occurs until 
the next removal of destinations as for every message that is received being on 
that faulty state will enter the synchronization block and throw and exception 
which will cause performance to degrade.

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>Assignee: Gary Tully
>  Labels: jmx, networkBridge, networkConnector
> Fix For: 5.13.1, 5.14.0, 5.12.3
>
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-15 Thread Christopher L. Shannon (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101903#comment-15101903
 ] 

Christopher L. Shannon commented on AMQ-6052:
-

I actually already backported this to 5.13.x but forgot to update the fixed 
versions.  I can also move it to 5.12.3 in case it is released but any others 
can be backported later if there is a desire for them.

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>Assignee: Gary Tully
>  Labels: jmx, networkBridge, networkConnector
> Fix For: 5.14.0
>
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
> at 
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-15 Thread Tim Bain (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101802#comment-15101802
 ] 

Tim Bain commented on AMQ-6052:
---

Can we back-port this issue to any future patch releases we do (5.13.1 at a 
minimum, plus 5.12.3, 5.11.4, etc. if we do them)?  I don't think it's 
important enough to make a patch version just for this issue, but I do think 
it's enough of a frustration for anyone with a NoB configuration that it should 
be in a patch release if we're already doing one for any of the earlier 
versions.

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>Assignee: Gary Tully
>  Labels: jmx, networkBridge, networkConnector
> Fix For: 5.14.0
>
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-15 Thread Tim Bain (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101813#comment-15101813
 ] 

Tim Bain commented on AMQ-6052:
---

Also note that a workaround is to set the logging level to ERROR for 
org.apache.activemq.network.MBeanBridgeDestination.  You run the risk of not 
seeing errors in MBean creation due to other reasons, but in practice the odds 
of that are unlikely so there's really not much of a cost, and I think that's 
better than disabling JMX entirely.

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>Assignee: Gary Tully
>  Labels: jmx, networkBridge, networkConnector
> Fix For: 5.14.0
>
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-15 Thread Tim Bain (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15101971#comment-15101971
 ] 

Tim Bain commented on AMQ-6052:
---

Great, thanks.

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>Assignee: Gary Tully
>  Labels: jmx, networkBridge, networkConnector
> Fix For: 5.13.1, 5.14.0, 5.12.3
>
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
> at 
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-11 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091866#comment-15091866
 ] 

ASF GitHub Bot commented on AMQ-6052:
-

Github user asfgit closed the pull request at:

https://github.com/apache/activemq/pull/164


> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>  Labels: jmx, networkBridge, networkConnector
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
> at 
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-11 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15091865#comment-15091865
 ] 

ASF subversion and git services commented on AMQ-6052:
--

Commit 3bb7e4a5c8497c8259a267e2eb11dddb8615a1ea in activemq's branch 
refs/heads/master from [~Altaflux]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=3bb7e4a ]

Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
already existing destinations
https://issues.apache.org/jira/browse/AMQ-6052
closes #164


> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>  Labels: jmx, networkBridge, networkConnector
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-11 Thread Pablo Lozano (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092338#comment-15092338
 ] 

Pablo Lozano commented on AMQ-6052:
---

Great thanks Gary,
I expect it to work correctly, we have run this patch in production for a while 
and haven't seen the issue occur again so fingers crossed.

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>Assignee: Gary Tully
>  Labels: jmx, networkBridge, networkConnector
> Fix For: 5.14.0
>
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
> at 
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2016-01-04 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081805#comment-15081805
 ] 

ASF GitHub Bot commented on AMQ-6052:
-

GitHub user Altaflux opened a pull request:

https://github.com/apache/activemq/pull/164

AMQ-6052 Network of brokers on duplex mode reports 
InstanceAlreadyExistsException on already existing destinations

This PR is related to Issue AMQ-6052
https://issues.apache.org/jira/browse/AMQ-6052


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Altaflux/activemq master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq/pull/164.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #164


commit a262140a616e238984b25e326143fb8e00291ed1
Author: Altaflux 
Date:   2016-01-04T21:00:00Z

Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
already existing destinations

commit 15dc63cb96a02d64cda9b5bd0f77492f36938f47
Author: Altaflux 
Date:   2016-01-04T21:03:26Z

Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
already existing destinations




> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>  Labels: jmx, networkBridge, networkConnector
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2015-12-01 Thread Pablo Lozano (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15034322#comment-15034322
 ] 

Pablo Lozano commented on AMQ-6052:
---

Is there anything missing to check this issue?

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.10.1, 5.12.1, 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>  Labels: jmx, networkBridge, networkConnector
> Attachments: AMQ_6052-2.patch, AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
> at 
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2015-11-20 Thread Pablo Lozano (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15018499#comment-15018499
 ] 

Pablo Lozano commented on AMQ-6052:
---

I have included a patch for this issue.

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>  Labels: jmx, networkBridge, networkConnector
> Attachments: AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
> at 
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2015-11-20 Thread Pablo Lozano (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15018701#comment-15018701
 ] 

Pablo Lozano commented on AMQ-6052:
---

No problem, 
Let me work out a test and attach it.

> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>  Labels: jmx, networkBridge, networkConnector
> Attachments: AMQ_6052.patch
>
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at 
> org.apache.activemq.broker.jmx.ManagementContext.registerMBean(ManagementContext.java:380)
> at 
> org.apache.activemq.broker.jmx.AnnotatedMBean.registerMBean(AnnotatedMBean.java:72)
> at 
> org.apache.activemq.network.MBeanBridgeDestination.onInboundMessage(MBeanBridgeDestination.java:97)
> at 
> org.apache.activemq.network.MBeanNetworkListener.onInboundMessage(MBeanNetworkListener.java:115)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceInboundMessage(DemandForwardingBridgeSupport.java:1680)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport.serviceRemoteCommand(DemandForwardingBridgeSupport.java:649)
> at 
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.onCommand(DemandForwardingBridgeSupport.java:224)
> at 
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:116)
> at 
> org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
> at 
> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

2015-11-19 Thread Pablo Lozano (JIRA)


[ 
https://issues.apache.org/jira/browse/AMQ-6052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15015059#comment-15015059
 ] 

Pablo Lozano commented on AMQ-6052:
---

I have found the issue that activates this problem.

{code:title=MBeanBridgeDestination.java|borderStyle=solid}
private Map destinationObjectNameMap = new 
ConcurrentHashMap();
private Map 
outboundDestinationViewMap = new ConcurrentHashMap();
private Map 
inboundDestinationViewMap = new ConcurrentHashMap();
{code}

Both onOutboundMessage() and onInboundMessage() use the  
destinationObjectNameMap to register the ObjectName of the 
NetworkDestinationView. But each other overwrite their value when using a 
duplex connection.

{code:title=MBeanBridgeDestination.java|borderStyle=solid}
public void onInboundMessage(Message message) {

 destinationObjectNameMap.put(destination, objectName);
}
{code}

When running with the option to purge unactiveDestinationViews which by default 
is active it will un-register from the MBeanServer the objectName that is found 
on  destinationObjectNameMap.remove(entry.getKey()); //ActiveMqDestination. 
This happens on the method 
purgeInactiveDestinationView(Map 
map) which receives both outboundDestinationViewMap and 
inboundDestinationViewMap.

Thus when running for outboundDestinationViewMap if the last registration of a 
destination was actually of a inBound it will incorrectly delete  the object 
name of and  inboundDestination insead of the one from outboundDestination.

I am working on a fix and submitting a patch for this issue.



> Network of brokers on duplex mode reports InstanceAlreadyExistsException on 
> already existing destinations
> -
>
> Key: AMQ-6052
> URL: https://issues.apache.org/jira/browse/AMQ-6052
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: networkbridge
>Affects Versions: 5.11.3
> Environment: Linux
>Reporter: Pablo Lozano
>  Labels: jmx, networkBridge, networkConnector
>
> When using a network of brokers apparently on duplex with destinations which 
> were already created on each MBeanBridgeDestination.onOutboundMessage() and 
> MBeanBridgeDestination.onInboundMessage() the bridge tries to register the 
> MBean of a destination which has already been created.
> Here is a discussion that started but a ticket was not created.
> http://activemq.2283324.n4.nabble.com/Broker-log-full-of-Failed-to-register-queue-messages-td4685241.html
> Although this does not seem to impact the functionality of the application it 
> creates a massive amount of logs as this message repeats for every received 
> message. 
> This are the important bits of my activeMQ configuration:
> {code:xml}
>
>  uri="multicast://default" conduitSubscriptions="true" duplex="true" >
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> connectorPort="1091"
>jmxDomainName="org.apache.activemq"/>
> 
> 
> 
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  discoveryUri="multicast://default" 
> updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
>  updateClusterClients="true"
> rebalanceClusterClients="true" 
> updateClusterClientsOnRemove="true"/>
> 
> {code}
> And this is the output log generated:
> {noformat}
> 2015-11-18 15:43:10,497 [.69:41090@36731] WARN  MBeanBridgeDestination
>  - Failed to register queue://mailsystem.templateprocessor
> javax.management.InstanceAlreadyExistsException: 
> org.apache.activemq:brokerName=mailsystemBroker,connector=duplexNetworkConnectors,networkConnectorName=#0,networkBridge=tcp_//10.211.2.69_41090,type=Broker,direction=inbound,destinationType=Queue,destinationName=mailsystem.templateprocessor
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at 
>

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

[jira] [Commented] (AMQ-6052) Network of brokers on duplex mode reports InstanceAlreadyExistsException on already existing destinations

13 matches

Site Navigation

Mail list logo

Footer information