javax.naming.CommunicationException: Communication exception for SerialContext[myEnv={org.omg.CORBA.ORBInitialPort=34513, java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Failed to look up ConnectorDescriptor from JNDI]

Oracle Community | bastian_knight | 5 years ago
  1. 0

    JMS destination lookup doesn't work on GlassFish 3.1.1 with a standalone client

    Oracle Community | 5 years ago | bastian_knight
    javax.naming.CommunicationException: Communication exception for SerialContext[myEnv={org.omg.CORBA.ORBInitialPort=34513, java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Failed to look up ConnectorDescriptor from JNDI]
  2. 0

    Problem with jndi lookup from remote machine

    GitHub | 10 months ago | andreas513
    javax.naming.CommunicationException: Communication exception for SerialContext[myEnv={org.omg.CORBA.ORBInitialPort=3700, java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory, com.sun.jndi.ldap.connect.timeout=500, com.sun.corba.ee.transport.ORBTCPTimeouts=500:30000:30:999999, org.omg.CORBA.ORBInitialHost=prodweb4, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming} [Root exception is com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Failed to look up ConnectorDescriptor from JNDI]
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    Starting Java EE Application on Glassfish

    Stack Overflow | 1 year ago | Peter-TI
    com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Invalid destination jms/NewMessage for MDB: JNDI name not found

    2 unregistered visitors
    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. com.sun.appserv.connectors.internal.api.ConnectorRuntimeException

      Failed to look up ConnectorDescriptor from JNDI

      at com.sun.enterprise.resource.naming.AdministeredObjectFactory.getObjectInstance()
    2. Connectors Runtime
      AdministeredObjectFactory.getObjectInstance
      1. com.sun.enterprise.resource.naming.AdministeredObjectFactory.getObjectInstance(AdministeredObjectFactory.java:104)
      1 frame
    3. Java RT
      NamingManager.getObjectInstance
      1. javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)
      1 frame
    4. Glassfish Naming
      SerialContext.lookup
      1. com.sun.enterprise.naming.impl.SerialContext.getObjectInstance(SerialContext.java:556)
      2. com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:514)
      3. com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
      3 frames
    5. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:411)
      1 frame
    6. libraryclient
      LibraryClient.main
      1. libraryclient.LibraryClient.main(LibraryClient.java:34)
      1 frame