[
https://issues.apache.org/jira/browse/AMQ-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3438.
-----------------------------
Resolution: Fixed
resolved in http://svn.apache.org/viewvc?rev=1154162&view=rev
new
org.apache.activemq.broker.jmx.ManagementContext#allowRemoteAddressInMBeanNames,
accessible via xml. when false, a transport connector will just be registered
by its clientId (which defaults to connectionid)
> Make use of remote port in Connection MBeanNames optional, useful when
> ephemeral range cycles quickly
> -----------------------------------------------------------------------------------------------------
>
> Key: AMQ-3438
> URL: https://issues.apache.org/jira/browse/AMQ-3438
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 5.5.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: connector, jmx, stomp
> Fix For: 5.6.0
>
>
> With fast connection close/creation (like stomp) the client side ephemeral
> port range can result in duplicate mbean names when close is async. Potential
> of failed mbean registration due to port reuse.
> {code}DEBUG ManagedTransportConnection - Failure reason:
> javax.management.InstanceAlreadyExistsException:
> org.apache.activemq:BrokerName=XXXXXX,Type=Connection,ConnectorName=stomp,ViewType=address,Name=/X.X.X.X_52170{code}
> Make the registration of an address type mbean configurable so that this case
> can be avoided. In the main, it is handy to see the remote address in the
> mbean name, so the default should be to use the remote port. Just the client
> Id (which default to the connection id, will be used in the mbean name) when
> use of remote port is not allowed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
