• Entries (RSS)
  • Comments (RSS)

Unable to initialize deferred EJB error in WID

Posted by | Posted in WebSphere, Websphere Process Server / Integration Developer | Posted on 07-04-2008

Tagged Under : , , , , ,

com.ibm.websphere.csi.EJBContainerException: Unable to initialize deferred EJB.
at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:186)
at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.setupEnvironment(J2ee14EJBDispatcher.java:125)
at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler.invoke(JAXRPCHandler.java:144)
at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke(WrappedHandler.java:64)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:226)

This is a common error message in WebSphere Integration Developer after making some changes in a module. I think this error is because of some synchronization issues in the project.

Anyways the solution to this problem is to remove the project from the process server and add it once again.

  • Share/Bookmark

Read More

Comments

3 comments posted onUnable to initialize deferred EJB error in WID

  1. Thanks. This works in many cases.

  2. I got the same problem in the Websphere 5.1 when the application tries to connect to the remote service. Any idea about that. Happens only few times in 1000 transactions.

  3. I am sorry I have no clue about this issue in WAS 5.1.

    Try rebuilding the module.

Post a Comment