PI45449: EXCEPTION MESSAGE IS NOT INCLUDED IN THE SOAP FAULT WHEN THE APPLICATION EXPLICITLY THROWS A RUNTIMEEXCEPTION.

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• A user-defined runtime exception is handled as "Internal
  Error".
  

Local fix

• You can set com.ibm.ws.websvcs.ResetBuffer=false to disable the
  functionality of PI33437.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server users of   *
  *                  JAX-WS web services.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Runtime exception is incorrectly        *
  *                      wrapped in an "Internal Error" soap     *
  *                      fault when                              *
  *                      com.ibm.ws.websvcs.ResetBuffer is set   *
  *                      to true.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When com.ibm.ws.websvcs.ResetBuffer is set to true, although
  webservices.unify.faults is set to false, the
  RuntimeException thrown during attachment writing is
  wrapped in the "Internal Error" soap fault. But if the
  RuntimeException is coming from Application code, this
  Exception information should be included in the soap fault.
  Currently WebServices engine doesn't differentiate these two
  kinds of RuntimeExceptions, and that causes the incorrect
  behavior.
  

Problem conclusion

• The WebServices engine is changed to check if the
  RuntimeException comes from the attachment writing phase or
  not, in this way it corrects the issue.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.9.  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 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

• R850 PSY

     UP