Root exception is weblogic.rjvm.PeerGoneException:

I have a problem doing the Look onto the Weblogic server.
          Here is the code I use in a method for this purpose and call the
          method from main(). I paste the code below (enclosed within "CODE
          BEGINS", "CODE ENDS")
          -----------------CODE BEGINS-----------------------------------------
               System.out.println("DataCollector : Look up serverHome called");
               Hashtable props = new Hashtable();
               props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
               props.put(Context.PROVIDER_URL, url);
               props.put(Context.SECURITY_PRINCIPAL, userName);
               props.put(Context.SECURITY_CREDENTIALS, passWord);
               System.out.println("Before Inital Context "+props);
               Context ctx = new InitialContext(props);
               System.out.println("Initial Context successful");
               serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
               System.out.println("Look up successful");
               ctx.close();
               System.out.println("Closed context successfully");
          -----------------CODE ENDS-----------------------------------------
          On executing this piece of code, I receive the following Exceptions
          -------------OUTPUT OF CODE BEGINS---------------------
          DataCollector : Look up serverHome called
          Before Inital Context
          {java.naming.provider.url=T3://njecomprod06:10817,
          java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory,
          java.naming.security.principal=system,
          java.naming.security.credentials=security}
          Initial Context successful
          Exception in thread "main" javax.naming.CommunicationException. Root
          exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
          java.io.EOFException
          java.io.EOFException
          at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
          at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
          at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          -------------OUTPUT OF CODE ENDS---------------------
          This piece of code fails in the line
          serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
          The weblogic server is standalone (not on a cluster). All other
          details give for this purpose like port no, username, password etc are
          correct.
          Also, On the WebLogic server prompt, the following stack trace is
          printed. Please let me know what is wrong in this look up code
          element.
          Thanks in advance for your help.
          -------------------------------------------------------EXCEPTION ON
          WEBLOGIC SIDE BEGINS--------------------------
          java.io.EOFException
          at java.io.DataInputStream.readInt(DataInputStream.java:343)
          at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          --------------- nested within: ------------------
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
          creating response stream ] - with nested exception:
          [java.io.EOFException]
          at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
          at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          <Oct 25, 2002 10:57:04 AM EDT> <Error> <Posix Performance Pack>
          <Uncaught Throwable in processSockets
          java.io.EOFException:
          Start server side stack trace:
          java.io.EOFException
          at java.io.DataInputStream.readInt(DataInputStream.java:343)
          at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          at java.io.DataInputStream.readInt(DataInputStream.java:343)
          at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          --------------- nested within: ------------------
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
          creating response stream ]
          Start server side stack trace:
          java.io.EOFException
          at java.io.DataInputStream.readInt(DataInputStream.java:343)
          at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          --------------- nested within: ------------------
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
          creating response stream ] - with nested exception:
          [java.io.EOFException]
          at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
          at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          - with nested exception:
          [java.io.EOFException:
          Start server side stack trace:
          java.io.EOFException
                  at java.io.DataInputStream.readInt(DataInputStream.java:343)
                  at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
                  at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
                  at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
                  at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
                  at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
                  at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
                  at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
                  at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
                  at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
                  at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
                  at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
                  at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
                  at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
                  at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End  server side stack trace
          at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
          at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          -------------------------------------------------------EXCEPTION ON
          WEBLOGIC SIDE ENDS--------------------------
          

You may want to open a support case with BEA to resolve this issue. I
          suspect that you may be using some server patches which have not also
          been applied to your WebLogic client JVMs. If that is the case,
          upgrading to the latest service pack may be the easiest and best remedy.
          Sincerely,
          Charlie Therit
          Developer Relations Engineer
          BEA Support
          Lakshmi Narasimhan wrote:
          >I have a problem doing the Look onto the Weblogic server.
          >
          >Here is the code I use in a method for this purpose and call the
          >method from main(). I paste the code below (enclosed within "CODE
          >BEGINS", "CODE ENDS")
          >
          >
          >-----------------CODE BEGINS-----------------------------------------
          >{
          >     System.out.println("DataCollector : Look up serverHome called");
          >     Hashtable props = new Hashtable();
          >     props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
          >     props.put(Context.PROVIDER_URL, url);
          >     props.put(Context.SECURITY_PRINCIPAL, userName);
          >     props.put(Context.SECURITY_CREDENTIALS, passWord);
          >     System.out.println("Before Inital Context "+props);
          >     Context ctx = new InitialContext(props);
          >     System.out.println("Initial Context successful");
          >     serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
          >     System.out.println("Look up successful");
          >     ctx.close();
          >     System.out.println("Closed context successfully");
          >}
          >-----------------CODE ENDS-----------------------------------------
          >
          >On executing this piece of code, I receive the following Exceptions
          >
          >-------------OUTPUT OF CODE BEGINS---------------------
          >DataCollector : Look up serverHome called
          >Before Inital Context
          >{java.naming.provider.url=T3://njecomprod06:10817,
          >java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory,
          >java.naming.security.principal=system,
          >java.naming.security.credentials=security}
          >Initial Context successful
          >
          >Exception in thread "main" javax.naming.CommunicationException. Root
          >exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
          >java.io.EOFException
          >java.io.EOFException
          > at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
          > at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
          > at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >-------------OUTPUT OF CODE ENDS---------------------
          >
          >This piece of code fails in the line
          >
          >serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
          >
          >The weblogic server is standalone (not on a cluster). All other
          >details give for this purpose like port no, username, password etc are
          >correct.
          >
          >Also, On the WebLogic server prompt, the following stack trace is
          >printed. Please let me know what is wrong in this look up code
          >element.
          >
          >Thanks in advance for your help.
          >
          >-------------------------------------------------------EXCEPTION ON
          >WEBLOGIC SIDE BEGINS--------------------------
          >java.io.EOFException
          > at java.io.DataInputStream.readInt(DataInputStream.java:343)
          > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >--------------- nested within: ------------------
          >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
          >creating response stream ] - with nested exception:
          >[java.io.EOFException]
          > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
          > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          ><Oct 25, 2002 10:57:04 AM EDT> <Error> <Posix Performance Pack>
          ><Uncaught Throwable in processSockets
          >java.io.EOFException:
          >Start server side stack trace:
          >java.io.EOFException
          > at java.io.DataInputStream.readInt(DataInputStream.java:343)
          > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >End server side stack trace
          >
          > at java.io.DataInputStream.readInt(DataInputStream.java:343)
          > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >--------------- nested within: ------------------
          >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
          >creating response stream ]
          >
          >Start server side stack trace:
          >java.io.EOFException
          > at java.io.DataInputStream.readInt(DataInputStream.java:343)
          > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >--------------- nested within: ------------------
          >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
          >creating response stream ] - with nested exception:
          >[java.io.EOFException]
          > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
          > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >End server side stack trace
          > - with nested exception:
          >[java.io.EOFException:
          >Start server side stack trace:
          >java.io.EOFException
          >        at java.io.DataInputStream.readInt(DataInputStream.java:343)
          >        at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
          >        at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
          >        at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
          >        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
          >        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
          >        at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
          >        at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
          >        at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
          >        at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          >        at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          >        at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          >        at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          >        at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          >        at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          >        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          >        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >End  server side stack trace
          >]
          > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
          > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
          > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
          > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          >
          >
          >-------------------------------------------------------EXCEPTION ON
          >WEBLOGIC SIDE ENDS--------------------------
          >
          >
          [att1.html]
          

Similar Messages

  • Getting weblogic.rjvm.PeerGoneException while posting request to foreign Q

    Hi,
    There are two application deployed on 2 different weblogic server .Say application A(EJB) is deployed on weblogic 9 and Application B (Oracle service Bus) is runing on Weblogic 10.3.
    Application A sends request to a queue that is on applcation B server. Weblogic (app A) has foreign JMS server that exports the queue of app B. Configuration at Application A is :
    <foreign-server name="JmsSyncServer">
    <sub-deployment-name>SUBDEPLOYMENT_xyz</sub-deployment-name>
    <foreign-destination name="Synchronous Request Queue">
    <local-jndi-name>spain.queue.sebulasyncoutput</local-jndi-name>
    <remote-jndi-name>osb.jms.queue.extern.service.request</remote-jndi-name>
    </foreign-destination>
    <foreign-connection-factory name="Sebula Synchronous QCF">
    <local-jndi-name>spain.SebulaSyncQueueConnectionFactory</local-jndi-name>
    <remote-jndi-name>osb.jms.cf.nonXA</remote-jndi-name>
    </foreign-connection-factory>
    <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
    <connection-url>t3://abcd.1.com:20001,abcd.2.com::20002</connection-url>
    </foreign-server>
    Now this cf and queue osb.jms.cf.nonXA and osb.jms.queue.extern.service.request are implemented on application B weblogic server. No authentication is given to this implementation. As soon as application A posts request to Application B following exception is thrown in application A logs :
    2010.05.21 16:31:04,919 | ERROR | SyncEaiSebulaDelegate | <null|null|U289145226331099999430000> Failed to send JMS request: properties[{ClientID=SPAIN, Operation=MsisdnDetails, message_type=sebula.sync.out, RequestTag=U289145226331099999430000}].
    com.o2.spain.jms.MessagingException: Failure during JMS setup: destination[sebula_sync_output].
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:85)
    at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:426)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:382)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
    at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at com.o2.spain.jms.ServiceLocator.lookupDestination(ServiceLocator.java:130)
    at com.o2.spain.jms.ServiceLocator.getDestination(ServiceLocator.java:109)
    at com.o2.spain.jms.MessageDestinationHandler.setup(MessageDestinationHandler.java:193)
    at com.o2.spain.jms.MessageDestinationHandler.setupLazyAndAfterFailure(MessageDestinationHandler.java:165)
    at com.o2.spain.jms.MessageDestinationHandler.getTemporaryReceiver(MessageDestinationHandler.java:543)
    at com.o2.spain.jms.MessageDestination.getTemporaryReceiver(MessageDestination.java:318)
    at com.o2.spain.jms.JmsClientImpl.doRequest(JmsClientImpl.java:147)
    at com.o2.spain.jms.JmsClientImpl.request(JmsClientImpl.java:125)
    at com.o2.spain.interfaces.sebula.sync.SyncEaiSebulaDelegate.executeRequest(SyncEaiSebulaDelegate.java:345)
    at com.o2.spain.interfaces.sebula.sync.SyncEaiSebulaDelegate.getMsisdnDetails(SyncEaiSebulaDelegate.java:182)
    at com.o2.spain.ejb.SynchronousEaiFacadeBean.getMsisdnDetails(SynchronousEaiFacadeBean.java:221)
    at com.o2.spain.ejb.SynchronousEaiFacade_letkhg_ELOImpl.getMsisdnDetails(SynchronousEaiFacade_letkhg_ELOImpl.java:405)
    at com.o2.spain.ejb.SpainWebFacadeBean.getMsisdnDetails(SpainWebFacadeBean.java:1084)
    at com.o2.spain.ejb.SpainWebFacade_sesxly_ELOImpl.getMsisdnDetails(SpainWebFacade_sesxly_ELOImpl.java:1787)
    at com.o2.spain.ejb.ws.SpainWebWSPortSoapBindingImpl.getMsisdnDetails(SpainWebWSPortSoapBindingImpl.java:379)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
    at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
    at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
    at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at com.o2.spain.ejb.ws.AxisServletFilter.doFilter(AxisServletFilter.java:29)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3242)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: com.o2.spain.jms.MessagingException: Failed looking up Destination [spain.queue.sebulasyncoutput].
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
    at weblogic.jndi.internal.ServerNamingNode_923_WLStub.lookup(Unknown Source)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:379)
    ... 58 more
    Caused by: javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
            java.io.EOFException]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:85)
    at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:426)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:382)
    ... 58 more
    Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
    at weblogic.jndi.internal.ServerNamingNode_923_WLStub.lookup(Unknown Source)
    at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:379)
    ... 58 more
    Caused by: java.io.EOFException
    at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:383)
    at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:737)
    at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:684)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:845)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:802)
    at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:120)
    at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    It will be great if someone helps in finding out the cause....waiting for reply..
    thanks,
    Kshitij

    I had the exact same issue and found a solution here:
    http://kr.forums.oracle.com/forums/thread.jspa?threadID=755132
    "The root cause of the PGE in this instance was missing Principle classes in the remote JVM. An authenticated subject's (has our custom principles) security context is propagated to the remote JVM which throws a ClassNotFoundException, this is wrapped in the PGE."

  • Weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.EOFException

    Hi,
    We are working with Weblogic 6.1.
    The system was quite stable, but a couple of days ago some batch process suddenly
    started to fail, with no apparent reason, there was no change in the system neither
    in the code.
    The following exception is received:
    Stopped, RemoteException weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException
    We have also noticed that other jobs had failed before due to some memory problems,
    but using the Weblogic Console; Monitoring; Performance, then when some jobs had
    some memory problems forcing the garbage collection the batches worked properly.
    Maybe these 2 problems have no relation between one an other, but they appeared
    at the same time.
    Any help will be appreciated.
    Thanks and best regards.

    Hi,
    We are working with Weblogic 6.1.
    The system was quite stable, but a couple of days ago some batch process suddenly
    started to fail, with no apparent reason, there was no change in the system neither
    in the code.
    The following exception is received:
    Stopped, RemoteException weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException
    We have also noticed that other jobs had failed before due to some memory problems,
    but using the Weblogic Console; Monitoring; Performance, then when some jobs had
    some memory problems forcing the garbage collection the batches worked properly.
    Maybe these 2 problems have no relation between one an other, but they appeared
    at the same time.
    Any help will be appreciated.
    Thanks and best regards.

  • Weblogic.rjvm.PeerGoneException: ; nested exception is

    Hi,
    I am trying to access Remote EJB(deployed in server A) from Client (deployed in server B). I am getting this error.
    Please help!!!
    weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
         java.io.InvalidClassException: com.sybase.jdbc2.tds.SybTimestamp; local class incompatible: stream classdesc serialVersionUID = 4038526507615253075, local class serialVersionUID = -4859870295624974195
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:315)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:250)
         at com.bankofny.gdoasis.payment.ejb.PaymentCalculationManagerRemoteEJB_suyjh6_EOImpl_910_WLStub.rollInterestPeriod(Unknown Source)
         at com.bankofny.gdoasis.batch.payment.RollInterestPeriod.main(RollInterestPeriod.java:96)
    Caused by: java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
         java.io.InvalidClassException: com.sybase.jdbc2.tds.SybTimestamp; local class incompatible: stream classdesc serialVersionUID = 4038526507615253075, local class serialVersionUID = -4859870295624974195
         at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:430)
         at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:362)
         at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:359)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:851)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:787)
         at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:283)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    Caused by: java.io.InvalidClassException: com.sybase.jdbc2.tds.SybTimestamp; local class incompatible: stream classdesc serialVersionUID = 4038526507615253075, local class serialVersionUID = -4859870295624974195
         at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:546)
         at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
         at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1292)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
         at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:36)
         at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755)
         at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717)
         at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
         at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
         at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:65)
         at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:37)
         at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:214)
         at weblogic.rjvm.MsgAbbrevInputStream.init(MsgAbbrevInputStream.java:169)
         at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:424)
         ... 9 more

    Hi
    This is due to invalid class compatibility. May be you are using the two different versions of classes. one at server side and another at your client side. please make sure both are having the SerialVersion Id's.
    regards,
    Sudheer

  • WLS 9.2 - weblogic.rjvm.PeerGoneException

    Hello, I am currently dealing with a particularly annoying problem for which I have already raised a support case with BEA.
    Our application makes calls to a thired party security application via EJBs provided by the thired party.
    The thired party application registers and RMI stub on the WLS JNDI tree and the thired party EJBs use this stub to make calls to the security application.
    We have a simple test harness that Remotely looks up the different EJBs and calls methods on them. This works for the limited set of methods that we test.
    However at specific points in the applications usage we run into:
    ####<Dec 10, 2006 8:13:38 PM GMT> <Notice> <Stdout> <myserver> <examplesServer> <[ACTIVE] ExecuteThread: '0' for
    queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1165781618271> <000000> <20:13:38.271: Error: at.client.
    AtClient.doService() : Client: Service com/thalesesecurity/at/server/wl92dsms -
    has gone down! Trying next server.
    Exception: weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException>
    Once we get this error all further calls to the thired party beans that use the stub fail with:
    ####<Dec 10, 2006 8:13:38 PM GMT> <Notice> <Stdout> <myserver> <examplesServer> <[ACTIVE] ExecuteThread: '0' for
    queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1165781618489> <000000> <<Dec 10, 2006 20:13:38> <FATAL>
    com.output.rule.impl.ValidateAcknowledgement.checkSignature(86): common.service.security.exceptions.Securit
    yException: Unexpected exception: com.thalesesecurity.at.service.ServiceException: Client: Could not connect to any server
    Error(s):
    Client: Service com/thalesesecurity/at/server/wl92dsms -
    has gone down! Trying next server.
    Exception: java.rmi.ConnectException: Could not establish a connection with 5640100714642584389C:172.21.4.27R:-522103521865481
    3556S:myserver:[7003,7003,-1,-1,-1,-1,-1]:wl_server:examplesServer, java.rmi.ConnectException: Destination is not
    a server; No available router to destination; nested exception is:
    java.rmi.ConnectException: Destination is not a server; No available router to destination
    The thired party server is running and is reachable. It seems the exception may be masking some other problem.
    So far the only real lead I have has come from turning up some debug parameters which reveals that the EOF at the root of the POE seems to occur shortly after the last of the 100 principles that belong to the user has been transmitted over the socket:
    12928: ace2 d273 7100 7e00 0c74 0023 434f 4c4c ...sq.~..t.#COLL
    12944: 4543 545f 5052 4f43 4553 5349 4e47 5f52 ECT_PROCESSING_R
    12960: 4550 4f52 545f 5052 494e 4349 5041 4c75 EPORT_PRINCIPALu
    12976: 7100 7e00 1100 0000 0d31 3136 3733 3239 q.~......1167329
    12992: 3636 3638 3130 7571 007e 0011 0000 0010 666810uq.~......
    13008: b82b 60ed 529c c990 fa98 c67e d667 174e .+`.R......~.g.N
    13024: 78 x
    >
    ####<Dec 28, 2006 7:31:24 PM GMT> <Debug> <RJVM> <myserver> <examplesServer> <ExecuteThread: '8' for queue: 'weblogic.soc
    ket.Muxer'> <<WLS Kernel>> <> <> <1167334284325> <BEA-000517> <Error on connection: 'weblogic.rjvm.t3.MuxableSocketT3$T3MsgAbbrevJVMCo
    nnection@1f78388'
    java.io.EOFException
    java.io.EOFException
    at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:383)
    at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:732)
    at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:679)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:840)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:797)
    at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:120)
    at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    >
    I have asked our application team to try reducing the number of principles that can be assigned to the user to see if this has any effect on the problem. I have already tried, among others, incleasing the maximum message size for all protocols and ensureing and security jar files before the weblogic.jar file but so far I have had no luck. Any suggestions would be most welcome.
    Hussein Badakhchani
    http://dev2dev.bea.com/blog/hoos
    London Middleware
    http://londonmiddleware.org/index.html
    Edited by hoos at 12/29/2006 9:25 PM

    <p>The root cause of the PGE in this instance was missing Principle classes in the remote JVM. An authenticated subject's (has our custom principles) security context is propagated to the remote JVM which throws a ClassNotFoundException, this is wrapped in the PGE.</p>
    <p>
    Hussein Badakhchani
    London Middleware
    </p>
    Edited by hoos at 01/09/2007 1:48 AM
    Edited by hoos at 01/09/2007 1:49 AM

  • Weblogic.rjvm.PeerGoneException

    this package is not in the API doc on the web for WL5.1... but i still get
    an error:
    <I> <RJVM> Signaling
    peer -2000438937484024190S110.20.116.265:[7031,7031,7032,7032,7031,-1] gone:
    weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException]
    anyone know where I can find some info on it?

    Hendry Janto wrote:
    Hi,
    I got problem in my weblogic server. I got 1 table SQL Server 2000 contains 31 millions of records. When I try to delete some records using Statement.executeUpdate, it tooks about 7 hours, and then comes out error message as follow :
    weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
    [weblogic.rjvm.PeerGoneException: ; nested exception is:
    weblogic.utils.net.SocketResetException - with nested exception:
    [java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read]]
    My question is, what is the meaning of this error message, and will this situation cause the weblogic server performance / SQL Server 2000 performance dropping ? Coz after I restart the weblogic server, the performance back to normal again. Thanks.Hi. The PeerGoneException has nothing to do with JDBC, but indicates a communication failure
    between WLS and an external client. The SQLServer issue is separate. Whose JDBC driver
    are you using? The SQLServer delete problem is internal to the DBMS and certainly a function of the
    size of the table. How are you doing the update? Is it via a PreparedStatement? Please show it
    to me.
    Joe Weinstein at BEA

  • Weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds

    Hi to All
    when i am trying to retrieve huge amount of data using the application deployed in the weblogic server 9.1
    i am getting the following exception at the client side...
    my client was using "weblogic.jar" to run and compile...
    this application will take 10-15 mins to process the request.. but i am getting this exception at the 5 min of the request...
    the exception follows.....
    weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds
    at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
    .java:315)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
    .java:250)
    at com.nybot.prd.businesscomponent.ProductDictionaryMaintenanceBean_etiu
    ur_EOImpl_910_WLStub.retrieveInstruments(Unknown Source)
    at RetrieveFuturesInstruments.testInstruments(RetrieveFuturesInstruments
    .java:67)
    at RetrieveFuturesInstruments.main(RetrieveFuturesInstruments.java:87)
    S.Prabhu

    Senthamarai Prabhu wrote:
    Hi to All
    when i am trying to retrieve huge amount of data using the application
    deployed in the weblogic server 9.1 i am getting the following exception
    at the client side... my client was using "weblogic.jar" to run and
    compile... this application will take 10-15 mins to process the request..
    but i am getting this exception at the 5 min of the request...
    the exception follows.....
    weblogic.rjvm.PeerGoneException: No message was received for: '240'Hi,
    Just increase the timeout on JTA level
    B
    Schelstraete Bart
    [email protected]
    http://www.schelstraete.org
    http://www.linkedin.com/in/bschelst

  • Weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds with WLS 7.0

    I've got an EJB application which, at one stage, has to go off and import a lot
    of data from another external application. A java client is triggering this execution.
    I've updated the Transaction timeout setting and Stuck Thread timeout setting
    on the server. But the client is still getting a weblogic.rjvm.PeerGoneException.
    I've found a previous message which talks about updating either the weblogic.system.periodLength
    property on the server or the weblogic.system.idlePeriodsUntilTimeout on the client.
    However, the thread was referring to older versions of WLS (5 & 6). Is this
    still a valid approach for WLS 7.0? I couldn't find the weblogic.properties file
    on the server, and if I try to use the client system property, my client doesn't
    start.
    If anyone has any guidance on this, I would be very grateful.
    Thanks,
    Ed

    Hello Ed,
    It appears that the config.dtd is bundled in the weblogic.jar archive. I don't
    believe that the exact location of the DTD/Schema is specified at the top of the
    config.xml file. I hope that you are able to figure out how to solve your problem.
    Perhaps you could investigate the issue further with a BEA Engineer.
    Take care,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    "Ed Hillmann" <[email protected]> wrote:
    >
    Thanks for the help, Ryan. What is the address for the config.xml Schema/DTD?
    It doesn't appear in the file.
    That JTA settings is already handled. This error doesn't seem to be
    due to a
    Transaction being left open (I believe it spits out another exception).
    Thanks,
    Ed
    "Ryan LeCompte" <[email protected]> wrote:
    Hello Ed,
    I am not very familiar with this particular error, but I did a bit of
    research
    and it appears that most of these kinds of issues occured in the WLS
    5/6 days
    (as you mentioned, various parameters are set in the weblogic.properties
    file).
    However, weblogic.properties is not really used in WLS 6+. There isa
    document
    describing how to convert the old weblogic.properties to the currently
    used config.xml
    file:
    http://edocs.bea.com/wls/docs70/ConsoleHelp/conversion.html
    Also, you may wish to look at the DTD for the config.xml file, as you
    may find
    various parameters that you can set which may help solve your problem
    (for example):
    http://edocs.bea.com/wls/docs70/config_xml/JTA.html#536936
    There is a TimeoutSeconds parameter which defaults to 30. You may try
    changing
    this value.
    Hope this helps!
    Best regards,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    Try adding the -classic parameter along with the other parameters in
    the startWebLogic.cmd
    file (with the other parameters for remot debugging).

  • RJVM Signaling peer 3688822629303549796C160.96.179.40 gone: weblogic.rjvm.PeerGoneException:

    Hi,
    We are using WebLogic Server 5.1 SP8 as our AppServer.
    The server is killed abruptly with the following message :
    Mon Aug 20 14:44:39 GMT+08:00 2001:<I> <RJVM> Signaling peer 3688822629303549796C160.96.179.40
    gone: weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException]
    What should be the possible reasons?
    Is it something to do with the N/W breakups ?
    Regards,
    TejoKiran.Y

    Dear Kumar,
    Thanks for your interest in answering the Q.
    Well, there is no other stack trace available.
    The last message we saw is ,
    Mon Aug 20 14:44:39 GMT+08:00 2001:<I> <RJVM> Signaling peer 3688822629303549796C160.96.179.40
    gone: weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException]
    The server was killed completely.
    Infact, 160.96.179.40 is the IP Address of our Application Server (WebLogic Server
    is runnning at port 7001).
    That is the last statement.
    We observed this error few times before in our log file, but it
    didnot bring down the server.
    Would U mind explaining me what exactly does that error mean?
    For your info:
    We also saw this message few times,
    Fri Aug 17 15:08:36 GMT+08:00 2001:<I> <CliCon-#|ccls|0.998032002043> Connection
    to client for ClientContext - id: '#|ccls|0.998032002043', bound: 'true', dead:
    'false' has been unexpectedly lost because weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException].
    Initiating hard disconnect.
    Regards,
    TejoKiran.Y
    Kumar Allamraju <[email protected]> wrote:
    Are you sure that the server is killed (crashed)?
    The following informative message only says that the client
    with IP 160.96.179.40 has peer gone'd
    Could you post complete stack trace?
    TejoKiran wrote:
    Hi,
    We are using WebLogic Server 5.1 SP8 as our AppServer.
    The server is killed abruptly with the following message :
    Mon Aug 20 14:44:39 GMT+08:00 2001:<I> <RJVM> Signaling peer 3688822629303549796C160.96.179.40
    gone: weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.io.EOFException]
    What should be the possible reasons?
    Is it something to do with the N/W breakups ?
    Regards,
    TejoKiran.Y

  • RMI client losing connection and weblogic.rjvm.PeerGoneException

    What causes PeerGoneExceptions? We are seeing this very often on our
    production and test systems. We use WLS RMI clients connected to WLS 4.5.1
    servers w/ service pack 10. I understand that there is a heartbeat between
    the client JVM and the server JVM. Is there any documentation that explains
    how this actually works. For example, how often does the client send its
    heartbeat. Is it configurable? What could cause it to stop or drop the
    connection. We are using straight T3 (no T3S or HTTP).
    thanks for your help,
    Edwin Marcial
    Intercontinental Exchange

    What causes PeerGoneExceptions? We are seeing this very often on our
    production and test systems. We use WLS RMI clients connected to WLS 4.5.1
    servers w/ service pack 10. I understand that there is a heartbeat between
    the client JVM and the server JVM. Is there any documentation that explains
    how this actually works. For example, how often does the client send its
    heartbeat. Is it configurable? What could cause it to stop or drop the
    connection. We are using straight T3 (no T3S or HTTP).
    thanks for your help,
    Edwin Marcial
    Intercontinental Exchange

  • Javax.naming.AuthenticationException.  Root exception is java.lang.SecurityException: Authentication for user system denied in realm weblogic

    We have started getting the above error message in a system that has worked happily
    for the past 6 months or so (and continues to work happily from our disaster recovery
    environment). I should probably add that this occurs when we are attempting to
    write to the database via the connection pool.
    Anyone have any ideas?
    Thanks
    Andrew
    The full stack trace is
    javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
    Authentication for user system denied in realm weblogic
         <<no stack trace available>>
    31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
    thrown by rmi server(class com.esure.ibis.a
    ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
    [265127279722
    6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
    prdwls/296]: [BaseEJBObject]
    home: com.esure.ibis.accesslaye
    r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
    com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
    Bean::validateUser()
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    We have started getting the above error message in a system that has worked happily
    for the past 6 months or so (and continues to work happily from our disaster recovery
    environment). I should probably add that this occurs when we are attempting to
    write to the database via the connection pool.
    Anyone have any ideas?
    Thanks
    Andrew
    The full stack trace is
    javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
    Authentication for user system denied in realm weblogic
         <<no stack trace available>>
    31-Jan-02 00:04:41 GMT Warning Adapter RuntimeException
    thrown by rmi server(class com.esure.ibis.a
    ccesslayer.sb.useraccess.UserAccessBeanEOImpl)
    [265127279722
    6064825S:hfxesure17:[7005,7005,7002,7002,7005,7002,-1]:esure
    prdwls/296]: [BaseEJBObject]
    home: com.esure.ibis.accesslaye
    r.sb.useraccess.UserAccessBeanHomeImpl@4b741e
    com.esure.ibis.util.IbisException: NamingException occurred in UserAccess Session
    Bean::validateUser()
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBean.validateUser(UserAccessBean.java:192)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanImpl.validateUser(UserAccessBeanImpl.java:110)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl.validateUser(UserAccessBeanEOImpl.java:31)
         at com.esure.ibis.accesslayer.sb.useraccess.UserAccessBeanEOImpl_WLSkel.invoke(UserAccessBeanEOImpl_WLSkel.java:202)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
         at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:128)
         at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
         at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

  • Getting javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory.  Root exception is java.lang.ClassCastException: weblogic.jndi.WLInitialContextFactory

    We have an Issue in Weblogic6.1/7.0, while accessing a bean through Java Client. In the Code, i am providing the Initial Context factory and provider url to
    InitialContext Constructor. Weblogic.jar WILL NOT be availabe in the classpath.We are Loading the classes through CustomClassLoader which was written by us by extending java.lang.ClassLoader.
    While Constructing the InitialContext, it throws NoInitialContextException, the root exception it says ClassCastException.
    With this i am attaching the code snippet:
    JarAndClassFileLoader customLoader = JarAndClassFileLoader.getLoaderInstance();
    customLoader.pathFileVec.addElement(new ZipFile("c:\\FDRIVE\\bea\\wlserver6.1\\lib\\weblogic.jar"));               
    Thread.currentThread().setContextClassLoader(customLoader);
    Properties prop = new Properties();
    prop.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    prop.put(Context.PROVIDER_URL,"t3://localhost:7001");
    InitialContext itl = new InitialContext(prop) ---> Getting the above said NoInitialContextException..
    Kindly provide the necessary solutions to overcome this.

    I guess you did something wrong implementing your classloader(s).
    This works with 7.0:
         ClassLoader weblogicClassLoader;
         Thread.currentThread().setContextClassLoader(
         weblogicClassLoader = new URLClassLoader(
         new URL[] { new URL("http://localhost:7001/classes/") }
         Hashtable env = new Hashtable();
    env.put("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
    env.put("java.naming.provider.url", "t3://localhost:7001");
         InitialContext ctx = new InitialContext(env);     
    You may also look at these examples:
    http://dima.dhs.org/misc/ThinClient.jsp
    http://dima.dhs.org/misc/ThinClient2.jsp
    B.Ravikumar <[email protected]> wrote:
    We have an Issue in Weblogic6.1/7.0, while accessing a bean through Java Client. In the Code, i am providing the Initial Context factory and provider url to
    InitialContext Constructor. Weblogic.jar WILL NOT be availabe in the classpath.We are Loading the classes through CustomClassLoader which was written by us by extending java.lang.ClassLoader.
    While Constructing the InitialContext, it throws NoInitialContextException, the root exception it says ClassCastException.
    With this i am attaching the code snippet:
    JarAndClassFileLoader customLoader = JarAndClassFileLoader.getLoaderInstance();
    customLoader.pathFileVec.addElement(new ZipFile("c:\\FDRIVE\\bea\\wlserver6.1\\lib\\weblogic.jar"));               
    Thread.currentThread().setContextClassLoader(customLoader);
    Properties prop = new Properties();
    prop.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    prop.put(Context.PROVIDER_URL,"t3://localhost:7001");
    InitialContext itl = new InitialContext(prop) ---> Getting the above said NoInitialContextException..
    Kindly provide the necessary solutions to overcome this.--
    Dimitri

  • Application Deployment in Managed Node Failed with the error - ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.ne

    2013-06-24 21:16:28,551 [bxapp2.healthnet.com] [  STANDARD] [                    ] (l.access.RuleCandidateIterator) INFO    - Single candidate rule resolution optimization is enabled
    Error retrieving JNDI initial context:
    2013-06-24 21:16:28,952 [bxapp2.healthnet.com] [  STANDARD] [                    ] (    pegarules.resadap.RAClient) ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
    javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:175)
    at com.pega.pegarules.priv.util.JNDIUtil.getInitialContext(JNDIUtil.java:106)
    at com.pega.pegarules.priv.util.JNDIUtil.lookupUsingRealContextClassLoader(JNDIUtil.java:128)
    at com.pega.pegarules.resadap.RAClient.init(RAClient.java:102)
    at com.pega.pegarules.resadap.RAClient.<init>(RAClient.java:84)
    at com.pega.pegarules.resadap.RAClientContainer.get(RAClientContainer.java:47)
    at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:146)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.callRAClient(ListenerWrapper.java:358)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:233)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:713)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startServiceTypeListeners(ListenerStateManagerImpl.java:464)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListenerType(ListenerStateManagerImpl.java:423)
    at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.initServices(PRIntegrationEngineProviderImpl.java:166)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.initServices(PREnvironment.java:620)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:522)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
    at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
    at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
    at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
    ... 94 more
    2013-06-24 21:16:28,952 [bxapp2.healthnet.com] [  STANDARD] [                    ] (tener.ListenerStateManagerImpl) ERROR   - Unexpected exception.
    java.lang.NullPointerException
    at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:150)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.callRAClient(ListenerWrapper.java:358)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerWrapper.launchListener(ListenerWrapper.java:233)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startOneListener(ListenerStateManagerImpl.java:713)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startServiceTypeListeners(ListenerStateManagerImpl.java:464)
    at com.pega.pegarules.integration.engine.internal.services.listener.ListenerStateManagerImpl.startListenerType(ListenerStateManagerImpl.java:423)
    at com.pega.pegarules.integration.engine.internal.PRIntegrationEngineProviderImpl.initServices(PRIntegrationEngineProviderImpl.java:166)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.initServices(PREnvironment.java:620)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:522)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
    at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
    at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
    at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    2013-06-24 21:16:28,956 [bxapp2.healthnet.com] [  STANDARD] [                    ] (          internal.async.Agent) INFO    - Agents will be executed via the enterprise tier.
    2013-06-24 21:16:28,956 [bxapp2.healthnet.com] [  STANDARD] [                    ] (          internal.async.Agent) INFO    - Passivation will be done on a per-page basis.
    2013-06-24 21:16:30,023 [bxapp2.healthnet.com] [  STANDARD] [                    ] (    pegarules.resadap.RAClient) ERROR   - Caught exception while looking up Connection Factory with JNDI Name: java:comp/env/eis/PRAdapterConnectionFactory, javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
    javax.naming.ServiceUnavailableException [Root exception is java.net.UnknownHostException: Unknown protocol: 'TCP']
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:34)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:787)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:368)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:175)
    at com.pega.pegarules.priv.util.JNDIUtil.getInitialContext(JNDIUtil.java:106)
    at com.pega.pegarules.priv.util.JNDIUtil.lookupUsingRealContextClassLoader(JNDIUtil.java:128)
    at com.pega.pegarules.resadap.RAClient.init(RAClient.java:102)
    at com.pega.pegarules.resadap.RAClient.<init>(RAClient.java:84)
    at com.pega.pegarules.resadap.RAClientContainer.get(RAClientContainer.java:47)
    at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:146)
    at com.pega.pegarules.monitor.internal.UsageDaemonImpl.initialize(UsageDaemonImpl.java:546)
    at com.pega.pegarules.session.internal.async.Agent.start(Agent.java:1400)
    at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.startNode(PRNodeImpl.java:1520)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:533)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
    at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
    at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
    at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.net.UnknownHostException: Unknown protocol: 'TCP'
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:216)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
    at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:353)
    ... 84 more
    2013-06-24 21:16:30,038 [bxapp2.healthnet.com] [  STANDARD] [                    ] (      etier.impl.EngineStartup) ERROR   - PegaRULES initialization failed. Server: pg-sbxapp2.healthnet.com
    com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:387)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.getThreadAndInitialize(PRSessionProviderImpl.java:1516)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:619)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:165)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:138)
    at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.doStartup(EngineBean.java:120)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
    at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.doStartup(EngineBeanBoot.java:130)
    at com.pega.pegarules.internal.etier.ejb.EngineBMT_h449u3_ELOImpl.doStartup(EngineBMT_h449u3_ELOImpl.java:124)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:259)
    at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:167)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
    at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:439)
    at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1863)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1045)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:765)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.getThreadAndInitialize(PREnvironment.java:379)
    ... 60 more
    Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1043)
    ... 62 more
    Caused by: java.lang.NullPointerException
    at com.pega.pegarules.session.internal.async.BatchUtils.callRAClient(BatchUtils.java:150)
    at com.pega.pegarules.monitor.internal.UsageDaemonImpl.initialize(UsageDaemonImpl.java:546)
    at com.pega.pegarules.session.internal.async.Agent.start(Agent.java:1400)
    at com.pega.pegarules.session.internal.mgmt.PRNodeImpl.startNode(PRNodeImpl.java:1520)
    at com.pega.pegarules.session.internal.mgmt.PREnvironment.finishInit(PREnvironment.java:533)
    ... 67 more
    2013-06-24 21:16:30,051 [bxapp2.healthnet.com] [  STANDARD] [                    ] (      etier.impl.EngineStartup) INFO    - PegaRULES initialization failed. Server: pg-sbxapp2.healthnet.com
    2013-06-24 21:16:30,164 [bxapp2.healthnet.com] [  STANDARD] [                    ] (ervlet.WebAppLifeCycleListener) ERROR   - Enterprise tier failed to initialize properly, PegaRULES not available
    2013-06-24 21:16:30,190 [bxapp2.healthnet.com] [  STANDARD] [                    ] (ervlet.WebAppLifeCycleListener) INFO    - Web Tier initialization is complete.
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 167.238.162.41:8008 for protocols iiop, t3, ldap, snmp, http.>
    <Jun 24, 2013 9:16:30 PM PDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "pegamanaged2" for domain "sbxdomain8" running in Production Mode>
    <Jun 24, 2013 9:16:31 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Jun 24, 2013 9:16:31 PM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

    Greetings,
    javax.naming.NameNotFoundException. Root exception is
    org.omg.CosNaming.NamingContextPackage.NotFound
    =================
    Below is the line of my LoginServlet class which is
    referred to in the stack trace - Object object =
    context.lookup
                        ( "java:comp/env/ejb/WarehouseClerk" );The root of the naming context is 'java:comp/env' and this is where lookup automatically begins for EJBs and resources. IOW, by specifying "java:comp/env/ejb/WarehouseClerk" as the EJB lookup name the server is actually treating this as "java:comp/env/java:comp/env/ejb/WarehouseClerk". Specify only the ejb context ("ejb/WarehouseClerk") in your lookup and you should be fine.
    Any help would be most appreciated.
    SeanRegards,
    Tony "Vee Schade" Cook

  • Javax.naming.NamingException.  Root exception is java.lang.NoSuchMethodError

    I am using WLS5.1 inside visualage environment. I am trying to run
    a Simple EJB which connects to the database and executes two simple
    queries. The client code is as shown below:
    try{
    Context ic = getInitialContext();
    System.out.println("Initial Context created......"); java.lang.Object
    objref = ic.lookup("simpleBean.AtmHome"); System.out.println("objref
    created......");
    AtmHome home = (AtmHome) PortableRemoteObject.narrow(objref, AtmHome.class);
    System.out.println("home created......");
    Atm atm = home.create();
    System.out.println("atm created......");
    atm.transfer(8, 9, 100000);
    catch (NamingException ne)
    ne.printStackTrace(System.out);
    finally {
         try {
              ic.close();
              System.out.println("Closed the connection");
         catch (Exception e) {
              System.out.println("Exception while closing context....." );
    The above code executes fine for the first time but second time
    it throws an exception "javax.naming.NamingException.
    Root exception is java.lang.NoSuchMethodError"
    javax.naming.NamingException. Root exception is java.lang.NoSuchMethodError
         java.lang.Throwable()
         java.lang.Error()
         java.lang.LinkageError()
         java.lang.IncompatibleClassChangeError()
         java.lang.NoSuchMethodError()
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         javax.naming.NameImpl(java.util.Properties)
         javax.naming.CompositeName()
         weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
         weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
         weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
    int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
         java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
    weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
         void weblogic.kernel.ExecuteThread.run()
    --------------- nested within: ------------------
    weblogic.rmi.ServerError: A RemoteException occurred in the server
    method
    - with nested exception:
    [java.lang.NoSuchMethodError:
    Start server side stack trace:
    java.lang.NoSuchMethodError
         java.lang.Throwable()
         java.lang.Error()
         java.lang.LinkageError()
         java.lang.IncompatibleClassChangeError()
         java.lang.NoSuchMethodError()
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         javax.naming.NameImpl(java.util.Properties)
         javax.naming.CompositeName()
         weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
         weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
         weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
    int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
         java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
    weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
         void weblogic.kernel.ExecuteThread.run()
    End  server side stack trace
         weblogic.rmi.extensions.WRMIInputStream weblogic.rmi.extensions.AbstractRequest.sendReceive()
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.WLContextStub.lookup(java.lang.String)
         java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
         void simpleBean.AtmClient.main(java.lang.String [])
    NamingException is caught....
    I found out that it hangs at lookup function in the above code.
    Please let me know if I am missing any environment settings.
    Thanks
    Shailaja

    This problem is solved after installing service pack 8 for weblogic
    5.1
    -shailaja
    "shailaja" <[email protected]> wrote:
    >
    I am using WLS5.1 inside visualage environment. I am trying
    to run
    a Simple EJB which connects to the database and executes
    two simple
    queries. The client code is as shown below:
    try{
    Context ic = getInitialContext();
    System.out.println("Initial Context created......"); java.lang.Object
    objref = ic.lookup("simpleBean.AtmHome"); System.out.println("objref
    created......");
    AtmHome home = (AtmHome) PortableRemoteObject.narrow(objref,
    AtmHome.class);
    System.out.println("home created......");
    Atm atm = home.create();
    System.out.println("atm created......");
    atm.transfer(8, 9, 100000);
    catch (NamingException ne)
    ne.printStackTrace(System.out);
    finally {
         try {
              ic.close();
              System.out.println("Closed the connection");
         catch (Exception e) {
              System.out.println("Exception while closing context....."
    The above code executes fine for the first time but second
    time
    it throws an exception "javax.naming.NamingException.
    Root exception is java.lang.NoSuchMethodError"
    javax.naming.NamingException. Root exception is java.lang.NoSuchMethodError
         java.lang.Throwable()
         java.lang.Error()
         java.lang.LinkageError()
         java.lang.IncompatibleClassChangeError()
         java.lang.NoSuchMethodError()
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         javax.naming.NameImpl(java.util.Properties)
         javax.naming.CompositeName()
         weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
         weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
         weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
    int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
         java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
    weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
         void weblogic.kernel.ExecuteThread.run()
    --------------- nested within: ------------------
    weblogic.rmi.ServerError: A RemoteException occurred in
    the server
    method
    - with nested exception:
    [java.lang.NoSuchMethodError:
    Start server side stack trace:
    java.lang.NoSuchMethodError
         java.lang.Throwable()
         java.lang.Error()
         java.lang.LinkageError()
         java.lang.IncompatibleClassChangeError()
         java.lang.NoSuchMethodError()
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         void javax.naming.NameImpl.recordNamingConvention(java.util.Properties)
         javax.naming.NameImpl(java.util.Properties)
         javax.naming.CompositeName()
         weblogic.jndi.toolkit.NormalName(java.lang.String, javax.naming.NameParser)
         weblogic.jndi.toolkit.NormalName weblogic.jndi.toolkit.BasicWLContext.normalizeName(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext.lookup(java.lang.String)
         weblogic.rmi.extensions.OutgoingResponse weblogic.jndi.toolkit.BasicWLContext_WLSkel.invoke(weblogic.rmi.extensions.ServerObjectReference,
    int, weblogic.rmi.extensions.IncomingRequest, weblogic.rmi.extensions.OutgoingResponse)
         java.lang.Throwable weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(int,
    weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.extensions.BasicRequestHandler.handleRequest(weblogic.rmi.extensions.IncomingRequest)
         void weblogic.rmi.internal.BasicExecuteRequest.execute(weblogic.kernel.ExecuteThread)
         void weblogic.kernel.ExecuteThread.run()
    End  server side stack trace
         weblogic.rmi.extensions.WRMIInputStream weblogic.rmi.extensions.AbstractRequest.sendReceive()
         java.lang.Object weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(java.lang.String)
         java.lang.Object weblogic.jndi.toolkit.WLContextStub.lookup(java.lang.String)
         java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
         void simpleBean.AtmClient.main(java.lang.String [])
    NamingException is caught....
    I found out that it hangs at lookup function in the above
    code.
    Please let me know if I am missing any environment settings.
    Thanks
    Shailaja

  • Javax.naming.LinkException: .  Root exception is javax.naming.NameNotFoundException

    Hi
    I have a startup class which needs to access a local entity bean. It used to work
    in weblogic 6.1, i am currently migrating to 8.1 and i get a Link Exception. I
    tried to make the startup class as a listener with in the application (EAR), it
    still complains.
    Since it worked in 6.1 i am sure there should be a way for a startup class to
    access a local EJB, please help, i have seen lot of posting regarding this issue
    in the newsgroup but no clear answer.
    Any one who faced this problem before and had it solved please do repsond ASAP.
    U can mail to me at [email protected]
    Thanks
    Siju

    Are you sure the EJB deployed with that JNDI name?
    Can you show me your weblogic-ejb-jar.xml?
    -- Rob
    Arun wrote:
    Hi,
    Do we have a solution for this problem? I am encountering this problem with an
    Applciation Lifecycle Listener. I have deployed this Listener with my EAR file
    and it accesses a local ejb (stateful) in its postStart() method. The JNDI look
    up is causing a LinkException (root exception is NameNotFoundException)
    I am not at my work PC but the application was something like this.
    "weblogic-application.xml" had something like.
    <listener>
    <listener-class>MyListener</listener-class>
    <listener-uri>mylistener.jar</listener-uri>
    </listener>
    where mylistener.jar was placed at the root of the EAR file.
    MyListener.java was something like,
    import weblogic.application.ApplicationLifecycleListener;
    import weblogic.application.ApplicationLifecycleEvent;
    import mypackage.mylocalhome;
    import mypackage.mylocal;
    import javax.naming.*;
    public class MyListener extends ApplicationLifecycleListener {
    public void preStart(ApplicationLifecycleEvent evt) {
    System.out.println
    ("MyListener(preStart) -- we should always see you..");
    } // preStart
    public void postStart(ApplicationLifecycleEvent evt) {
    try {
    System.out.println
    ("MyListener(postStart) -- we should always see you..");
    Context ctx = new InitialContext();
    mylocalhome localhome = (mylocalhome)ctx.lookup("MYLOCALJNDINAME");
    mylocal localobj = localhome.create();
    } catch (Exception e) {
    e.printStackTrace();
    } // postStart
    public void preStop(ApplicationLifecycleEvent evt) {
    System.out.println
    ("MyListener(preStop) -- we should always see you..");
    } // preStop
    public void postStop(ApplicationLifecycleEvent evt) {
    System.out.println
    ("MyListener(postStop) -- we should always see you..");
    } // postStop
    public static void main(String[] args) {
    System.out.println
    ("MyListener(main): in main .. we should never see you..");
    } // main
    Any help is greatly appreciated.
    Thanks,
    Arun
    Rob Woollen <[email protected]> wrote:
    We'll need some more info. Can you show me your weblogic-ejb-jar.xml,
    the code you are using to lookup the bean, and the full exception?
    -- Rob
    Siju Hariharan wrote:
    Hi
    I have a startup class which needs to access a local entity bean. Itused to work
    in weblogic 6.1, i am currently migrating to 8.1 and i get a Link Exception.I
    tried to make the startup class as a listener with in the application(EAR), it
    still complains.
    Since it worked in 6.1 i am sure there should be a way for a startupclass to
    access a local EJB, please help, i have seen lot of posting regardingthis issue
    in the newsgroup but no clear answer.
    Any one who faced this problem before and had it solved please do repsondASAP.
    U can mail to me at [email protected]
    Thanks
    Siju

Maybe you are looking for

  • Performance issues with ID CS5

    Am working on netowkred Windows XP Pro Intel Core 2 6300 1.83GHz 3 MB RAM computer and just installed CS5 Premium. Am having issues with moving linked objects such as eps or jpegs (especially larger ones or grouped bunches of small jpeg pictures at o

  • Ipod cannot be updated. Unknown error -1417

    Hi Everyone, When i try to update to 1.2 of my Video iPod (30GB), i always receive "ipod cannot be updated. Unknown error -1417" I use Windows 2000 SP4 (with latest patches&updates) + iTunes 7.0. Is this a known bug with iTunes or something wrong wit

  • Using USB Keyboard and Mouse with S6000-f Ideatab

    First you need a Microusb to USB adaptor pluged in, then plug in a usb hub I'm using a 4 port unpowered mini hub then plug in a usb keyboaed and mouse.   it works good in Kingsoft office and AndrOpen office or any app that needs you to type it does d

  • Why are not  pop up  message window when message type I and W

    Hi All, I am working in BADI ( me_purchdoc_posted~posted) for t-code ME21N. Actually i want show material number, material description  and ABC indicator of material at saving point of PO if material is significant. code is properly working  but does

  • Change Object Server in SLD after system copy and SLD move?

    Hello, we did the following: - we migrated the SLD to the production system in our landscape - we copied the NWDI to a new system - the old object server was named sapsrv88 (object server attribute in the SLD) which was the hostname of the old SLD se