PI72518: Web services call failed with 500 (Internal Server Error) response and Content-Length 0.

Fixes are available

APAR status

Closed as program error.

Error description

When an error occurred during a Web services call,
500 (Internal Server Error) was returned and the Content-Length
was set to 0, without detailed error message.  The following
exception may occur:

AxisEngine    E org.apache.axis2.engine.AxisEngine receive
java.lang.IllegalStateException:
WSEJBEndpointManager.ejbPostInvoke already called.
org.apache.axis2.AxisFault:
java.lang.IllegalStateException:
WSEJBEndpointManager.ejbPostInvoke already called.
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWS
MessageReceiver.java:242)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:212)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPo
stRequest(HTTPTransportUtils.java:172)
at
com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis
2Servlet.java:1606)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1230)
...
Caused by: javax.xml.ws.WebServiceException:
java.lang.IllegalStateException:
WSEJBEndpointManager.ejbPostInvoke already called.
at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:175)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:70)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:128)
at
org.apache.axis2.jaxws.server.EndpointController.responseReady(E
ndpointController.java:710)
at
org.apache.axis2.jaxws.server.EndpointController.handleResponse(
EndpointController.java:439)
at
org.apache.axis2.jaxws.server.EndpointController.invoke(Endpoint
Controller.java:130)
at
org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWS
MessageReceiver.java:161)
... 29 more
Caused by: java.lang.IllegalStateException:
WSEJBEndpointManager.ejbPostInvoke already called.
at
com.ibm.ejs.container.WSEJBWrapper.ejbPostInvoke(WSEJBWrapper.ja
va:246)
at
com.ibm.ws.websvcs.server.WSEJBInvocationListener.responseReady(
WSEJBInvocationListener.java:420)
at
com.ibm.ws.websvcs.server.WSEJBInvocationListener.notify(WSEJBIn
vocationListener.java:106)
at
org.apache.axis2.jaxws.server.EndpointController.responseReady(E
ndpointController.java:707)
... 32 more

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server JAX-WS Web services.                 *
****************************************************************
* PROBLEM DESCRIPTION: Web services call failed with 500       *
*                      (Internal Server Error) response and    *
*                      Content-Length 0.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an error occurred during a Web services call,
500 (Internal Server Error) was returned and the Content-Length
was set to 0, without detailed error message.  The following
exception may occur:
AxisEngine    E org.apache.axis2.engine.AxisEngine receive
java.lang.IllegalStateException:
WSEJBEndpointManager.ejbPostInvoke already called.
org.apache.axis2.AxisFault:
java.lang.IllegalStateException:
WSEJBEndpointManager.ejbPostInvoke already called.
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at
org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWS
MessageReceiver.java:242)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:212)
... ...
Caused by: javax.xml.ws.WebServiceException:
java.lang.IllegalStateException:
WSEJBEndpointManager.ejbPostInvoke already called.
at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:175)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:70)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:128)
at
org.apache.axis2.jaxws.server.EndpointController.responseReady(E
ndpointController.java:710)
... ...
Caused by: java.lang.IllegalStateException:
WSEJBEndpointManager.ejbPostInvoke already called.
at
com.ibm.ejs.container.WSEJBWrapper.ejbPostInvoke(WSEJBWrapper.ja
va:246)
at
com.ibm.ws.websvcs.server.WSEJBInvocationListener.responseReady(
WSEJBInvocationListener.java:420)

Problem conclusion

The problem was caused by duplicate EJB postInvoke calls,
which has been corrected.

The fix for this APAR is currently targeted for inclusion in
fix pack 8.0.0.14, 8.5.5.12, and 9.0.0.4.  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
PI72518
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-17
Closed date
2017-02-21
Last modified date
2017-02-21

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

R800 PSY
UP
R850 PSY
UP
R900 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI72518: Web services call failed with 500 (Internal Server Error) response and Content-Length 0.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?