There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Port error during startup
    via by malakh,
  • ServiceMix - User - Problem starting ServiceMix
    via by Unknown author,
  • Can't Start a Local Weblogic server.
    via by 1e78763c-6a53-49e3-8c4c-c9abc48c74fb,
  • Can't Start Glassfish server on Open Solaris
    via by yuvaraju460,
  • CruiseControl cannot get web interface to work
    via Stack Overflow by bguiz
  • Can't run j2ee :((
    via by 843833,
  • We are using JMXRMI over SSL connector as described at JBoss Fuse 6 documentation [1]. This has worked flawlessly with Karaf 2.4.1 (as base for ServiceMix 4.5.0) but causes exceptions on container shutdown for version 2.4.3. During runtime the SSL connector is working though as before. Exceptions: StackTrace 1 {noformat}Exception in thread "JMX Connector Thread [service:jmx:rmi://]" java.lang.RuntimeException: Could not start JMX connector server at$ Caused by: Cannot bind to URL [rmi://]: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table] at at at$ Caused by: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table] at com.sun.jndi.rmi.registry.RegistryContext.bind( at com.sun.jndi.toolkit.url.GenericURLContext.bind( at javax.naming.InitialContext.bind( at at ... 1 more Caused by: java.rmi.NoSuchObjectException: no such object in table at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer( at sun.rmi.transport.StreamRemoteCall.executeCall( at sun.rmi.server.UnicastRef.invoke( at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source) at com.sun.jndi.rmi.registry.RegistryContext.bind( ... 5 more {noformat} StackTrace 2 {noformat} Exception in thread "JMX Connector Thread [service:jmx:rmi://]" 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/ and change the Registry Port and Server Port to unused ports at$ {noformat} etc/ {code:none} # # The ObjectName used to register the JMXConnectorServer # objectName = connector:name=rmi keyStoreAvailabilityTimeout = 5000 keyStore = karaf.keystore # keyAlias maps to keystore.xml keyPasswords alias keyAlias = local-test secured = true authenticatorType = password trustStore = karaf.keystore secureAlgorithm = default secureProtocol = SSL {code} The issue can be recreated using stock Karaf download with the following steps: - copy attached keystore.xml and org.apache.felix.fileinstall-keystore.cfg to ./etc folder - copy self-signed keystore file (karaf.jmx.ssl.jks) to etc folder - modify etc/ as shown below (or use modified copy attached to issue) - run container, check exceptions on shutdown [1]
    via by Michael Taeschner,
    • Cannot bind to URL [rmi://wesley-bakers-macbook-pro.local:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: wesley-bakers-macbook-pro.local; nested exception is: > Operation timed out] > at at at com.sun.enterprise.admin.jmx.remote.server.rmi.JmxConnectorServerDriver.startConnectorServer( at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(
    No Bugmate found.