javax.naming.ContextNotEmptyException

karaf-user | codeoncoffee | 6 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Re: Deploying bare Blueprint xml files?

    karaf-user | 6 years ago | codeoncoffee
    javax.naming.ContextNotEmptyException
  2. 0

    Re: Deploying bare Blueprint xml files?

    karaf-user | 6 years ago | codeoncoffee
    javax.naming.ContextNotEmptyException

    Root Cause Analysis

    1. javax.naming.ContextNotEmptyException

      No message provided

      at org.osjava.sj.jndi.AbstractContext.destroySubcontext()
    2. simple-jndi
      AbstractContext.close
      1. org.osjava.sj.jndi.AbstractContext.destroySubcontext(AbstractContext.java:539)
      2. org.osjava.sj.jndi.AbstractContext.close(AbstractContext.java:697)
      2 frames
    3. Java RT
      InitialContext.close
      1. javax.naming.InitialContext.close(InitialContext.java:531)
      1 frame
    4. simple-jndi
      DelegatingContext.close
      1. org.osjava.sj.jndi.DelegatingContext.close(DelegatingContext.java:164)
      1 frame
    5. Java RT
      RMIConnectorServer.start
      1. javax.naming.InitialContext.close(InitialContext.java:531)
      2. javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:626)
      3. javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412)
      3 frames
    6. org.apache.karaf
      ConnectorServerFactory$1.run
      1. org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:102)
      1 frame