Hi all I have been running my Bea fine until today when I cannot even run the EJB client. It gives the below problem. I tried many ways to troubleshoot the problem but in vain. Anyone has any idea to fix this ? Thanks ! javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.Factory. Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInory at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:191) at java.lang.ClassLoader.loadClass(ClassLoader.java:290) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:275) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:199) at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.jav at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:250 at javax.naming.InitialContext.init(InitialContext.java:226) at javax.naming.InitialContext.<init>(InitialContext.java:202) at ReportTest.main(ReportTest.java:49)
George Brown
Ranch Hand
Joined: Sep 26, 2000
Posts: 919
posted
0
Looks like a classpath problem to me, but I'm not familiar with the weblogic.jndi.WLInory class so I can't be sure. Are you sure nothing has changed since the last time you ran it?
Kodo Tan
Ranch Hand
Joined: Aug 14, 2001
Posts: 105
posted
0
Yes, I did not change anything. I can run the console tool.
Kodo Tan
Ranch Hand
Joined: Aug 14, 2001
Posts: 105
posted
0
Hi all After ensuring the classpath is correct, I have the following error: Beginning beanManaged.Client... java.io.StreamCorruptedException: Type code out of range, is 0 at java.io.ObjectInputStream.peekCode(ObjectInputStream.java:1280) at java.io.ObjectInputStream.SkipToEndOfBlockData(ObjectInputStream.java:1211) at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:776) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:353) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:232) at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:978) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:232) at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream .java:107) at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream .java:115) at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:685) at weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManagerClient. java:140) at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:626) at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454) at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:311) 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) --------------- nested within: ------------------ weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception: [java.io.StreamCorruptedException: Type code out of range, is 0] at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:687) at weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManagerClient. java:140) at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:626) at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454) at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:311) 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)
satyendra adhikari
Ranch Hand
Joined: Aug 17, 2001
Posts: 51
posted
0
hi! this looks purely a enviroment problem .The best way to ensure correct enviroment i have been using is to run setenv script supplied by weblogic itself..you will find these at setenv.cmd or .sh for NT or Unix so if you are working on Win9x open these and save as .bat and edit it(i mean correct it at weblogic_home and java_home as per your machine).Once you do that I hope you will be able to invoke your bean.
0
