[
https://issues.apache.org/jira/browse/AMQ-8470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493091#comment-17493091
]
Chris Scott commented on AMQ-8470:
----------------------------------
I can confirm that there is nothing else running on port 1099 (it works with
JDK8 and 11 which kind of confirms this).
I thought adding a list of versions where this issues arises would add more
clarity, clearly it hasn't. So let me restate this
With JDK17 running with activemq 5.16.3 the error occurs, the release notes
state that 5.16.3 fully supports JDK9+
[https://activemq.apache.org/activemq-5016003-release]
With JDK11 running activemq 5.16.3 the error does occur.
> Failed to start JMX connector Cannot bind to URL
> ------------------------------------------------
>
> Key: AMQ-8470
> URL: https://issues.apache.org/jira/browse/AMQ-8470
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.15.12, 5.15.13, 5.15.15, 5.16.2, 5.16.3
> Reporter: Chris Scott
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> With Java 17 from version 5.15.12 the following error is raised when the
> ManagementContext is configured to create a jmx connector.
> [JMX connector] WARN o.a.a.broker.jmx.ManagementContext - Failed to start
> JMX connector Cannot bind to URL [rmi://localhost:1099/jmxrmi]:
> javax.naming.CommunicationException [Root exception is
> java.rmi.NoSuchObjectException: no such object in table]. Will restart
> management to re-create JMX connector, trying to remedy this issue.
> This error does not occur when running Java 8 or Java 11.
> This error does not occur when running Java 17 against 5.15.11 of ActiveMQ
>
> This could be related to AMQ-7400 which introduced in 5.15.12
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
