[ https://issues.apache.org/jira/browse/KARAF-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581298#comment-17581298 ]
Ondrej Mrekaj commented on KARAF-7443: -------------------------------------- We want to upgrade to 4.3.x but the issue is in it too. 4.2.11/4.3.1 are last versions, where we know, that jmx connection to Karaf in docker container working fine. I tried 4.4.1 but with same result. > JMX: rmiRegistryHost=0.0.0.0 Runtime IO exception: no such object in table > -------------------------------------------------------------------------- > > Key: KARAF-7443 > URL: https://issues.apache.org/jira/browse/KARAF-7443 > Project: Karaf > Issue Type: Bug > Components: karaf > Affects Versions: 4.2.15 > Reporter: João Andrade > Assignee: Jean-Baptiste Onofré > Priority: Minor > Labels: JMX, jmx > > Setting rmiServerHost/rmiRegistryHost to 0.0.0.0 no longer allows connections > from remote hosts: > {code:java} > $>open > service:jmx:rmi://10.11.12.13:44444/jndi/rmi://10.11.12.13:1099/karaf-root -u > karaf -p karaf > #RuntimeIOException: Runtime IO exception: no such object in table {code} > ...but allows from actual host: > {code:java} > $>open > service:jmx:rmi://10.11.12.13:44444/jndi/rmi://10.11.12.13:1099/karaf-root -u > karaf -p karaf > #Connection to > service:jmx:rmi://10.11.12.13:44444/jndi/rmi://10.11.12.13:1099/karaf-root is > opened > {code} > This behavior changed somewhere between 4.2.10 and 4.2.15 (im guessing > https://issues.apache.org/jira/browse/KARAF-6955) > Setting rmiServerHost/rmiRegistryHost to the interface IP (10.11.12.13) works > around the issue, but then ports 1099/44444 are bound to that interface. -- This message was sent by Atlassian Jira (v8.20.10#820010)