java.lang.RuntimeException: Connector Runtime not initialized

Oracle Community | lb54 | 5 years ago
  1. 0

    Synchronization errors in Glassfish SSH Cluster Setup

    Oracle Community | 5 years ago | lb54
    java.lang.RuntimeException: Connector Runtime not initialized
  2. 0
    samebug tip
    Switch to Android Build Tools 23.0.3
  3. 0

    Got the exception below when try to update JMX ports with config:update command from console. {code} karaf@root()> config:edit --force org.apache.karaf.management karaf@root()> config:property-set rmiRegistryPort 1101 karaf@root()> config:property-set rmiServerPort 44445 karaf@root()> config:update karaf@root()> Exception in thread "JMX Connector Thread [service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-r oot]" java.lang.RuntimeException: Could not start JMX connector server at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:258) Caused by: java.io.IOException: Cannot bind to URL [rmi://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:826) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431) at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:245) Caused by: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in tabl e] at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:143) at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:226) at javax.naming.InitialContext.bind(InitialContext.java:419) at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:643) at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:426) ... 1 more Caused by: java.rmi.NoSuchObjectException: no such object in table at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:275) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:252) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:378) at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source) at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:137) ... 5 more {code} more bad thing is the serviceUrl property in the etc/org.apache.karaf.management.cfg has been updated to: {code} serviceUrl = service:jmx:rmi://0.0.0.0:44444/jndi/rmi://0.0.0.0:1099/karaf-root {code} so even after restart karaf, it will still try to use the old JMX ports. These commands work fine in karaf 2.3.x.

    Apache's JIRA Issue Tracker | 2 years ago | Xilai Dai
    java.lang.RuntimeException: Could not start JMX connector server
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [KARAF-304] Startup problems: javax.naming.NoInitialContextException: Unable to determine caller'sBundleContext - ASF JIRA

    apache.org | 2 years ago
    java.lang.RuntimeException: Could not start JMX connector server

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.RuntimeException

      Connector Runtime not initialized

      at com.sun.enterprise.connectors.ConnectorRuntime.getRuntime()
    2. Connectors Runtime
      ResourcesUtil.getDomain
      1. com.sun.enterprise.connectors.ConnectorRuntime.getRuntime(ConnectorRuntime.java:213)
      2. com.sun.enterprise.connectors.util.ResourcesUtil.getRuntime(ResourcesUtil.java:122)
      3. com.sun.enterprise.connectors.util.ResourcesUtil.getDomain(ResourcesUtil.java:115)
      3 frames