PK40693: SUBSEQUENT PROFILE AUGMENTATIONS FAILED IN THE SAME PMT SESSION AFTER THE FIRST AUGMENTATION SUCCEEDED.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
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: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris

APAR status

• Closed as program error.

Error description

• Subsequent profile augmentation failed with
  NumberFormatException within the same PMT session after the f
  irst augment has succeeded.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users using IBM WebSphere Extended           *
  *                 Deployment profile templates to create       *
  *                 profiles.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Profile augmentation using the same     *
  *                      PMT session using WebSphere Extended    *
  *                      Deployment profile templates fails on   *
  *                      a second augment action.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WSAdmin requester caches the initialization message of the
  listener during the second profile augmentation. The same
  requester is used but the new listener is initialized.
  The requester expects to parse a return code for the request
  made from the listener, instead it is receiving an
  initialization message resulting in a parsing error.
  

Problem conclusion

• Capability was added to the requeter to proccess the second
  initialization message and to wait for the correct response
  for the request made.
  
  The fix for this APAR is currently targeted for inclusion
  in fixpack 6.1.0.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:

Modules/Macros

• PROFILE
  

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