This discussion is archived
1 Reply Latest reply: Jun 29, 2012 7:46 AM by RaviJegga RSS

Error ejbtimer

945343 Newbie
Currently Being Moderated
I can not lookup ejbtimer, following error:

com.teste.core.exception.SystemException: While trying to lookup 'TesteImpl#br.com.teste.service.Teste' didn't find subcontext 'TesteImpl#br'. Resolved ''
     at br.com.teste.service.locator.WebLogicServiceLocator$InternalInvocationHandler.getService(WebLogicServiceLocator.java:109)
     at br.com.teste.service.locator.WebLogicServiceLocator$InternalInvocationHandler.<init>(WebLogicServiceLocator.java:88)
     at br.com.teste.service.locator.WebLogicServiceLocator.getService(WebLogicServiceLocator.java:72)
     at br.com.teste.relatorio.Relatorio.test4(Relatorio.java:66)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
     at java.lang.reflect.Method.invoke(Method.java:616)
     at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
     at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
     at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
     at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
     at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
     at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
     at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
     at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
     at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
     at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
     at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
     at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
     at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'TesteImpl#br.com.teste.service.Teste' didn't find subcontext 'TesteImpl#br'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'TesteImpl#br.com.teste.service.Teste' didn't find subcontext 'TesteImpl#br'. Resolved '']; remaining name 'TesteImpl#br/com/teste/service/Teste'
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
     at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
     at weblogic.jndi.internal.ServerNamingNode_1034_WLStub.lookup(Unknown Source)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at javax.naming.InitialContext.lookup(InitialContext.java:409)
     at br.com.teste.service.locator.WebLogicServiceLocator$InternalInvocationHandler.getService(WebLogicServiceLocator.java:106)
     ... 26 more
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'TesteImpl#br.com.teste.service.Teste' didn't find subcontext 'TesteImpl#br'. Resolved ''
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.Secur
  • 1. Re: Error ejbtimer
    RaviJegga Expert
    Currently Being Moderated
    Hi
    0. The error clearly says, JNDI Lookup failed and it is not able to find your EJB.

    1. Make sure your EJB is deployed and there are on errors at all. From Weblogic Console, this JAR or EAR should be Active. Check the logs for any errors.

    2. Now, check the actual Bean class to make sure you have that annotation and the package is correct. I have a EJB like this: Make sure you give the mappedName followed by fully qualified with package the remote interface name.
    package com.abc.xyz.facade;
    @Stateless(name = "MyManager", mappedName = "MyApp_MyManager")
    public class MyManagerrBean implements MyManager, MyManagerLocal { ...}
    
    In Client side, my JNDI Lookup is like below and all my ejbs do work fine:
    
    "MyApp_MyManager#com.abc.xyz.facade.MyManager"
    Thanks
    Ravi Jegga

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points