Re: java.rmi.RemoteException: EJB Exception:nested exception is: java.lang.java.lang.NoClassDefFoundError
Andreas Berg <[email protected]> Sat, 7 Oct 2006 08:30:20 +0200
| Newsgroups | gmane.comp.java.sun.ejb.general |
|---|---|
| Message-ID | <[email protected]> |
Murali, a NoClassDefFoundError occurs, when a class is present in the classloader= , but there was some problem loading the class. This can be a static initializer that throws a runtime exception, a wrong classloader (there are a lot of different classloaders in an EJB environment), or a lot of other reasons. Have a look that all the JARs are in their proper places (it's not enough, if they are in some classpath), make a static initializer failsafe (always, or at least decent logging) - and if all doen't help, try to explain the problem here in more detail (is SAPIAgent part of an external JAR, ...). Kind regards, Andreas Berg Zelfi AG Hechtsheimer Stra=DFe 33 55131 Mainz Telefon: 06131-9064850 Telefax: 06131-9064853 [email protected] http://www.zelfi.com/ Murali said: > Hi All, > > Please some out help me out, > i have a written a stateless session bean, which is compiled with out > errors, and i deployed it in wblogic server. > > when i run my client program, i get this exceptions. please some one he= lp > me how to tackle this, > > Thanks in advance, > > > > java.rmi.RemoteException: EJB Exception: ; nested exception is: > java.lang.NoClassDefFoundError: secure/SDK/SAPIAgent > > Start server side stack trace: > java.rmi.RemoteException: EJB Exception: ; nested exception is: > java.lang.NoClassDefFoundError: SDK/SAPIAgent > java.lang.NoClassDefFoundError: SDK/SAPIAgent > at SAPI.SAPIBean.<init>(SAPIBean.java:18) > at SAPI.SAPIBean_163r2w_Impl.<init>(SAPIBean_163r2w_Impl.java:31) > at java.lang.Class.newInstance0(Native Method) > at java.lang.Class.newInstance(Class.java:232) > at weblogic.ejb20.manager.BaseEJBManager.allocateBean > (BaseEJBManager.java:129) > at weblogic.ejb20.manager.StatelessManager.createBean > (StatelessManager.java:266) > at weblogic.ejb20.pool.StatelessSessionPool.createBean > (StatelessSessionPool.java:148) > at weblogic.ejb20.pool.StatelessSessionPool.getBean > (StatelessSessionPool.java:101) > at weblogic.ejb20.manager.StatelessManager.preInvoke > (StatelessManager.java:142) > at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:1= 38) > at weblogic.ejb20.internal.StatelessEJBObject.preInvoke > (StatelessEJBObject.java:70) > at valyd.SAPI.SAPIBean_163r2w_EOImpl.getSession > (SAPIBean_163r2w_EOImpl.java:234) > at valyd.SAPI.SAPIBean_163r2w_EOImpl_WLSkel.invoke(Unknown Source) > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:455) > at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke > (ReplicaAwareServerRef.java:114) > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:396) > at weblogic.security.service.SecurityServiceManager.runAs > (SecurityServiceManager.java:731) > at weblogic.rmi.internal.BasicServerRef.handleRequest > (BasicServerRef.java:391) > at weblogic.rmi.internal.BasicExecuteRequest.execute > (BasicExecuteRequest.java:30) > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:261) > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:223) > End server side stack trace > ; nested exception is: java.lang.NoClassDefFoundError: SDK/SAPIAgent > > Murali > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D > To unsubscribe, send email to [email protected] and include in the > body > of the message "signoff EJB-INTEREST". For general help, send email to > [email protected] and include in the body of the message "help". > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D To unsubscribe, send email to [email protected] and include in the bo= dy of the message "signoff EJB-INTEREST". For general help, send email to [email protected] and include in the body of the message "help".