javax.naming.NotContextException: jndiname when running a tck case
------------------------------------------------------------------

                 Key: GERONIMO-5828
                 URL: https://issues.apache.org/jira/browse/GERONIMO-5828
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: OpenEJB
    Affects Versions: 3.0
         Environment: ubuntu 10.04 x86
oracle jdk 1.6.0_23
            Reporter: Forrest Xia


When running a tck case which is related to EJB. I encounter this exception:
02-22-2011 14:54:58:  ERROR: javax.naming.NotContextException: [anjndiname]
        at 
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:165)
        at 
org.apache.xbean.naming.context.AbstractContext.lookup(AbstractContext.java:605)
        at 
org.apache.openejb.server.ejbd.JndiRequestHandler.doLookup(JndiRequestHandler.java:188)
        at 
org.apache.openejb.server.ejbd.JndiRequestHandler.processRequest(JndiRequestHandler.java:129)
        at 
org.apache.openejb.server.ejbd.EjbDaemon.processJndiRequest(EjbDaemon.java:200)
        at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:153)
        at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:71)
        at 
org.apache.openejb.server.ejbd.KeepAliveServer$Session.service(KeepAliveServer.java:213)
        at 
org.apache.openejb.server.ejbd.KeepAliveServer.service(KeepAliveServer.java:233)
        at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:66)
        at org.apache.openejb.server.ServicePool$2.run(ServicePool.java:91)
        at org.apache.openejb.server.ServicePool$3.run(ServicePool.java:120)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)

This same exception happens in several other EJB related cases.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to