javax.naming.NamingException: Unhandled error in lookup. Root exception is java.lang.NullPointerException
at javax.naming.NameImpl.<init>(NameImpl.java:250)
at javax.naming.CompositeName.<init>(CompositeName.java:223)
at weblogic.iiop.IIOPInvocationHandlerImpl.getClusteredStub(IIOPInvocationHandlerImpl.java:150)
at weblogic.iiop.IIOPInvocationHandlerImpl.resolveObject(IIOPInvocationHandlerImpl.java:114)
at weblogic.iiop.IIOPReplacer.resolveObject(IIOPReplacer.java:375)
at weblogic.iiop.AbstractMsgInput.readRemote(AbstractMsgInput.java:185)
at weblogic.iiop.AbstractMsgInput.readObject(AbstractMsgInput.java:156)
at weblogic.cos.naming.NamingContext_WLStub.resolve(NamingContext_WLStub.java:122)
at weblogic.jndi.cosnaming.IIOPInitialContextServer.lookup(IIOPInitialContextServer.java:109)
at javax.naming.InitialContext.lookup(InitialContext.java:345)
at jsp_servlet._jsp.__test._jspService(__test.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:946)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:910)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:277)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:403)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:285)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
Thanks for any help,
Rosa
5.1 <-> 7.0 is not officially supported. There is a known problem
(which is the same as the one below) which is fixed in a temporary
patch for CR93420 - you will need to go through support to get hold of
this.
andy
--
Is it known that there will be an officially Service Pack that correct the problem?.
It would be extremely useful.
Waiting for answer, Rosa
> Thanks for help, Andy.
>
> Is it known that there will be an officially Service Pack that correct the problem?.
> It would be extremely useful.
5.1 is EOL'ed there will be no new service packs. The only way you can
get this patch is through support.
andy
--