Fixes are available
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The following error might occur when an EJB-based JAX-WS service is invoked: 06/12/10 12:58:43:687 CET] 00000017 ExceptionFact 1 org.apache.axis2.jaxws.ExceptionFactory logRootCause stack:javax.ejb.EJBException: Unable to find EJB component: ear#hello-ejb.jar#HelloWorldBean at com.ibm.ejs.container.util.ExceptionUtil.EJBException(ExceptionU til.java:395) at com.ibm.ejs.container.EJSContainer.createWebServiceEndpointManag er(EJSContainer.java:1407) at com.ibm.ws.runtime.component.EJBContainerImpl.createWebServiceEn dpointManager(EJBContainerImpl.java:4562) at com.ibm.ws.websvcs.server.WSInvocationListener.requestReceived(W SInvocationListener.java:291) at com.ibm.ws.websvcs.server.WSInvocationListener.notify(WSInvocati onListener.java:86) at org.apache.axis2.jaxws.server.EndpointController.requestReceived (EndpointController.java:645) at org.apache.axis2.jaxws.server.EndpointController.handleRequest(E ndpointController.java:212) at org.apache.axis2.jaxws.server.EndpointController.invoke(Endpoint Controller.java:102) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWS MessageReceiver.java:159) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:188) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPo stRequest(HTTPTransportUtils.java:275) at com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis 2Servlet.java:1351) ... This exception would appear on the service, not the client.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IBM WebSphere Application Server * * V7.0 EJB-based JAX-WS services * **************************************************************** * PROBLEM DESCRIPTION: A "javax.ejb.EJBException: Unable to * * find EJB component" error may occur * * when invoking a JAX-WS service. * **************************************************************** * RECOMMENDATION: Install a fix pack that includes this APAR. * **************************************************************** When an EJB-based JAX-WS service is installed with the Rational Application Developer "loose config" option, or installed in WebSphere Application Server with the "Use Binary Configuration" option, the following error might occur when the service is invoked: 06/12/10 12:58:43:687 CET] 00000017 ExceptionFact 1 org.apache.axis2.jaxws.ExceptionFactory logRootCause stack:javax.ejb.EJBException: Unable to find EJB component: ear#hello-ejb.jar#HelloWorldBean at com.ibm.ejs.container.util.ExceptionUtil.EJBException(ExceptionU til.java:395) at com.ibm.ejs.container.EJSContainer.createWebServiceEndpointManag er(EJSContainer.java:1407) at com.ibm.ws.runtime.component.EJBContainerImpl.createWebServiceEn dpointManager(EJBContainerImpl.java:4562) at com.ibm.ws.websvcs.server.WSInvocationListener.requestReceived(W SInvocationListener.java:291) at com.ibm.ws.websvcs.server.WSInvocationListener.notify(WSInvocati onListener.java:86) at org.apache.axis2.jaxws.server.EndpointController.requestReceived (EndpointController.java:645) at org.apache.axis2.jaxws.server.EndpointController.handleRequest(E ndpointController.java:212) at org.apache.axis2.jaxws.server.EndpointController.invoke(Endpoint Controller.java:102) at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWS MessageReceiver.java:159) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:188) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPo stRequest(HTTPTransportUtils.java:275) at com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis 2Servlet.java:1351) ... This exception would appear on the service side, not the client's.
Problem conclusion
The JAX-WS runtime was fixed to create a correct J2EE name for the EJB bean that is the implementation of the JAX-WS service. This name is used by the EJB container when locating the bean. This APAR supercedes PM15201. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.17. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM28686
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-12-10
Closed date
2010-12-27
Last modified date
2010-12-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
27 October 2021