Hi, My deployable ear file seems to deploy successfully. When try to start up the EJB's from the WAS admin client GUI, a window pops-up saying that it was successfully started, but the log shows the error below. [7/19/02 11:14:23:127 EDT] 3d120a1e EJBEngine I WSVR0037I: Starting EJB jar: /usr/WebSphere/AppServer/installedApps/UAE11.ear/UAEAdminEJB11.jar [7/19/02 11:14:23:187 EDT] 3d120a1e EJBEngine X WSVR0040E: addEjbModule failed for com.ibm.ejs.models.base.config.applicationserver.impl.EJBModuleRefImpl (desiredExecutionState: START) (uri: UAEAdminEJB11.jar) java.lang.NoClassDefFoundError: com/ibm/ejs/container/EJSHome at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) Help is appriciated. -Ashok.
What version of Websphere are you using and are you using Visual Age for Java to deploy your beans? If so.. try exporting the deployed jar version of your bean. Also another problem could be that the class path at the application server level is incorrect. Make sure that you have the class path defined to all the classes of your project and also all the jars being used by your project
Commentary From the Sidelines of history
posted 17 years ago
I am using WAS 4.0 & no visual age for deployment.
hi this is basically the exception which is generated when u don't have all the dependent classes or the classes which u r importing in ur ej bean class. so make sure that u have added all the importing classes, packages into the same jar file as the bean. since when the server is started it will try to create the pool of the ejbs and at that time it will ask for all these classes.
hope this helps :roll:
Thanks<br /> <br />Kiran <br /> <br />SCEA, SCJP 1.4,<br /> <br />"First they ignore u, then they laugh at u, then they fight u, <br />then u will win<br /> <br />Mahatma Gandhi"
I had this problem when I made a new POJO project that my EJB project (the one that my server failed to raise) depended on, and entered it into the server. I am working with WSAD, and the solution was actually simple, go into the server settings, environment tab, and choose the "Add External Folder" button, to add the top level of the "out" folder that contained the classes in my POJO project. This is a semi-obvious thing, but the error was confusing, because it complained about basic stuff, whereas the real problem was that the EJB failed to load because the server couldn't find stuff from the POJO project.
Actually I have added the required output path to the server configurations through the Add External Path option. However it is still giving me the same error The user-provided class "com.americanexpress.ppmis.ejb.partnersetup.EJSStatelessPartnerSetUpServiceHomeBean_8c2652eb" needed by the EnterpriseBean could not be found or loaded. java.lang.NoClassDefFoundError: com/ibm/ejs/container/EJSHome Was this setting working only coz POJOs were used in the application instead of EJB? Btw I am working on WSAD 5.1 (migrating code from 3.5 to 5.1.x).
catch it before it slithers away! Oh wait, it's a tiny ad:
Devious Experiments for a Truly Passive Greenhouse!