Hi Michael,

I saw your Jira. Does it work with 2.4.1 ?

I gonna take a look later today.

Regards
JB

On 07/27/2015 04:20 PM, Michael Täschner wrote:
Hi Karaf-Users,

I raised issue KARAF-3887 [1] as I can recreate the problem using
provided Apache Karaf 2.4.3 and documented the necessary steps for
configuring JMXRMI over SSL connection.

Best Regards,
Michael

[1] https://issues.apache.org/jira/browse/KARAF-3887

2015-07-23 14:08 GMT+02:00 Michael Täschner <[email protected]
<mailto:[email protected]>>:

    Hi Karaf Users,

    based on referenced RedHat docu [1] we set up JMX over SSL
    connection for our ServiceMix 5.4.0 container (Karaf 2.4.1). This
    worked fine. Now with the upgrade to ServiceMix 5.4.1 / Karaf 2.4.3
    we get one of two exception stacktraces on container shutdown (see
    below). Has anything changed in regard to the keystore.xml, jaas
    provider, etc. changed between the minor version upgrade ? Currently
    it has no impact on usage, the JMXRMI interface is using SSL but the
    output is irritating.

    Stack 1
    Exception in thread "JMX Connector Thread
    [service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root
    <http://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root>]"
    java.lang.RuntimeException: Could not start JMX connector server
             at
    
org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:272)
    Caused by: java.io.IOException: Cannot bind to URL
    [rmi://0.0.0.0:1099/karaf-root <http://0.0.0.0:1099/karaf-root>]:
    javax.naming.CommunicationException [Root exception is
    java.rmi.NoSuchObjectException: no such object in table]
             at
    
javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827)
             at
    
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432)
             at
    
org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:259)
    Caused by: javax.naming.CommunicationException [Root exception is
    java.rmi.NoSuchObjectException: no such object in table]
             at
    com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:147)
             at
    com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228)
             at javax.naming.InitialContext.bind(InitialContext.java:425)
             at
    
javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644)
             at
    
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
             ... 1 more
    Caused by: java.rmi.NoSuchObjectException: no such object in table
             at
    
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:276)
             at
    sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:253)
             at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:379)
             at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
             at
    com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:141)
             ... 5 more

    Stack 2
    Exception in thread "JMX Connector Thread
    [service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root
    <http://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root>]"
    java.lang.RuntimeException:
    Port already in use: 44444;
    You may have started two containers.  If you need to start a second
    container or the default ports are already in use update the config
    file etc/org.apache.karaf.management.cfg and change the Registry
    Port and Server Port to unused ports
             at
    
org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:268)

    StackTrace:

    [1]
    
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Security_Guide/files/ESBSecurityJmxSSL.html

    Thanks and Best Regards,
    Michael



--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to