Topic
  • 1 reply
  • Latest Post - ‏2010-06-09T20:15:21Z by Tom.Seelbach
Rohit_R
Rohit_R
24 Posts

Pinned topic Problems with SCA EJB3 binding

‏2010-05-24T21:50:42Z |
We are facing some issues with SCA EJB3 binding. Client is a business process created in WID.
1) To be able to invoke the SCA generated EJB firstly we have to copy auto-generated EJB jar from the WAS deployment folder. Also after we copy the EJB jar file to the WID project we are not able invoke the EJB unless we explicitly create EJB stubs using the "createEJBStubs.cmd" utility which is present in WAS bin folder. Then we deploy the EJB Client process to a WPS server

2) The invoke works fine after till we restart the server. If we restart we have end up repeating the step 1) all over again. Without which we get the exception


Exception:com.ibm.websphere.sca.ServiceRuntimeException SourceId:com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI ProbeId:720 Reporter:com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl@567b567b javax.ejb.EJBException: nested exception is: java.lang.NullPointerException java.lang.NullPointerException at com.ibm.websphere.soa.sca.binding.ejb.BaseEJB3SessionBeanImpl.getModuleClassLoader(Unknown Source) at com.ibm.websphere.soa.sca.binding.ejb.BaseEJB3SessionBeanImpl.invoke(Unknown Source)

The exception details have been attached.
Updated on 2010-06-09T20:15:21Z at 2010-06-09T20:15:21Z by Tom.Seelbach
  • Tom.Seelbach
    Tom.Seelbach
    11 Posts

    Re: Problems with SCA EJB3 binding

    ‏2010-06-09T20:15:21Z  
    hi Rohit,

    You probably need to ask this question over on the WebSphere Process Server forum: http://www.ibm.com/developerworks/forums/forum.jspa?forumID=820
    Specifically I don't know if the WPS use case you describe (create business process in WID, copy auto-generated EJB to WID project, run createEJBStubs, deploy EJB Client to WPS server) is a supported use case.
    If it turns out to be a supported use case then let us know and we can dig deeper into the exception...

    thanks,
    Tom