You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Wojciech Targosz (Jira)" <ji...@apache.org> on 2022/06/13 12:58:00 UTC

[jira] [Commented] (AMQ-8470) Failed to start JMX connector Cannot bind to URL

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

Wojciech Targosz commented on AMQ-8470:
---------------------------------------

Hi [~jbonofre],

Any update on the issue? We're thinking on how to proceed with our product...

> 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
>             Fix For: 5.18.0, 5.17.2, 5.16.6
>
>
> 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.7#820007)