PM26583: @WEBSERVICE ANNOTATION PREVENTS APPLICATION'S ABILITY TO WRITE TO SYSTEMERR.LOG AFTER INITIAL JAX-WS APPLICATION DEPLOYMENT

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

• A JAX-WS service application contains the @WebService
  annotation. The application also contains code to write custom
  entries to the SystemErr.log.
  
  After the application is initially installed, the application is
  unable to write entries to the SystemErr.log.
  
  The application is only able to write to the SystemErr.log after
  the application server is restarted.
  
  This problem only occurs in a stand-alone Base environment.
  This problem does not occur in a federated Deployment Manager
  environment.
  
  There are no errors generated when this problem occurs.
  

Local fix

• Restart the application server
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V7.0 and JAX-WS web services.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: After deploying a JAX-WS application,   *
  *                      attempts to write to SystemErr.log do   *
  *                      not appear in the log file.             *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack containing this APAR.    *
  ****************************************************************
  A JAX-WS application contains the @WebService annotation.
  The application also contains code to write custom entries to
  the SystemErr.log.
  
  After the application is initially installed, the application is
  unable to write entries to the SystemErr.log.
  
  The application is only able to write to the SystemErr.log after
  the application server is restarted.
  
  This problem only occurs in a stand-alone Base environment.
  This problem does not occur in a federated Deployment Manager
  environment.
  
  There are no errors generated when this problem occurs.
  

Problem conclusion

• This problem was introduced in 7.0.0.7 by APAR PK92522.
  Output to SystemErr.log was temporarily redirected to a
  printStream, but not correctly restored to the original
  location.  This APAR ensures that error output location is
  always restored to SystemErr.log.
  
  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 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