PM27844: WSWS3163E: ERROR: THE WEB SERVICES ENGINE COULD NOT FIND A TARGET SERVICE TO INVOKE! TARGETSERVICE IS XXXXXX AFTER PM08816

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 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

• After upgrading WebSphere Application Server version to
  6.1.0.33 or 7.0.0.13 from previous versions, JAX-RPC web
  services might experience the following error:
  
  WSWS3163E: Error: The Web services engine could not find a
  target service to invoke!  targetService is xxxxxx
  
  Note: The error only occurs after upgrading WebSphere
  Application Server to the 6.1.0.33 or 7.0.0.13 fix packs. Prior
  to upgrading, the same application works without any issues.
  The error is especially likely to occur when a mixture of
  clients and server requests are running on an application
  server.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V6.1 and V7.0 JAX-RPC web services.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: JAX-RPC web services might receive a    *
  *                      WSWS3163E error after upgrading to      *
  *                      6.1.0.33 or 7.0.0.13.                   *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack containing this APAR.    *
  ****************************************************************
  After upgrading to 6.1.0.33 or 7.0.0.13 from previous
  versions, JAX-RPC web services might experience the following
  error:
  
  WSWS3163E: Error: The Web services engine could not find a
  target service to invoke!  targetService is xxxxxx
  
  Note: Above error only occurs after upgrading to the 6.1.0.33
  or 7.0.0.13 fix packs. Prior to upgrading, the same
  application works without any issues.  The error is especially
  likely to occur when a mixture of clients and server requests
  are running on a server.
  

Problem conclusion

• The problem was introduced by APAR PM08816 in WebSphere
  Application Server 6.1.0.33 and 7.0.0.13.
  PM08816 improved performance by caching some configuration
  information for JAX-RPC web services.  There was a problem
  with the fix such that old cached information was sometimes
  returned.  The stale cache information lead to the WSWS3163
  error.  This was especially true if JAX-RPC client and server
  requests were running on the same thread.
  
  This APAR corrects the stale cache problem so that the correct
  configuration information is returned.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.1.0.37 and 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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM33877 PM34849

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP

• R700 PSY

     UP