Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Problems with deployment of an EAR

 
Sarat Burle
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am trying to deploy an EAR on WAS 4.0. The EAR has Web and EJB components. While deploying the EJB, I get the following error:

[04.08.12 18:33:49:867 GMT+05:30] 6dd12eeb Server W WSVR0013W: Module, com.ibm.ejs.models.base.config.applicationserver.impl.EJBModuleRefImpl (desiredExecutionState: START) (uri: InterfacesEngineEJB.jar), failed to start
java.io.FileNotFoundException: InterfacesEngineEJB.jar
at com.ibm.etools.commonarchive.impl.ContainerImpl.getFile(ContainerImpl.java(Compiled Code))
at com.ibm.etools.commonarchive.impl.EARFileImpl.getModuleFile(EARFileImpl.java(Compiled Code))
at com.ibm.ws.runtime.Server.startModule(Server.java:570)
at com.ibm.ws.runtime.Server.startApplication(Server.java:399)
at com.ibm.ejs.sm.util.debug.DrAdminServer.basicStartApplication(DrAdminServer.java:2311)
at com.ibm.ejs.sm.util.debug.DrAdminServer.startApplication(DrAdminServer.java:2276)
at com.ibm.ejs.sm.util.debug.DrAdminServer.handleStartApplication(DrAdminServer.java:1272)
at com.ibm.ejs.sm.util.debug.DrAdminServer.processMethod(DrAdminServer.java:744)
at com.ibm.ejs.sm.util.debug.DrAdminServer.processRequest(DrAdminServer.java:603)
at com.ibm.ejs.sm.util.debug.DrAdminServer.processRequest(DrAdminServer.java:555)
at com.ibm.ejs.sm.util.debug.DrAdminServer.listen(DrAdminServer.java:504)
at com.ibm.ejs.sm.util.debug.DrAdminServer$ServerRunner.run(DrAdminServer.java:243)

Any idea??
 
somkiat puisungnoen
Ranch Hand
Posts: 1312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Your EAR file can deploy in another application server such as JBoss, J2EE RI or not ???

And

Please check in xml file such as application.xml
 
Nicholas Cheung
Ranch Hand
Posts: 4982
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Did you include all necessary JAR file in MANIFEST.MF as well?

It seems that WAS cannot locate your JAR files. Please check also the classpath and the project dependency to make sure that you have included the JAR files.

Nick
 
Vijay S. Rathore
Ranch Hand
Posts: 449
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sharat,

This definitely is the problem of classpath. If your web module is making a reference to some ejb modules then you must include the ejb modules in the Manifest.mf file of web module, under Class-Path
Failed to start java.io.FileNotFoundException: InterfacesEngineEJB.jar

For example: update the Web module�s Manifest.mf like this:
Manifest-Version: 1.0
Class-Path: InterfacesEngineEJB.jar
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic