PK65472: WSPROFILE API LOCKS THE PROFILE IN PROFILEREGISTRY.XML AND DOES NOT RELEASE FOR NEXT ACTION OF WSPROFILE API AGAINST PROFILE

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

APAR status

• Closed as program error.

Error description

• When the WSProfile API is operating on a profile (ex: augmenting
  it) a lock is placed on that profile in the
  profileRegistry.xml file. If a subsquent operation is
  attempted through the WSProfile API to modify that profile
  (and this operation requires the profile not to be locked)
  it will return failure.  If a process which places a lock on a
  profile is killed at the wrong time, the lock remains.
  After that point the user is unable to augment/delete the
  profile because the lock exists. The user is not supposed to
  manually modify the contents of the profileRegistry.xml.  In
  the 6.1 code stream there is no documented set of recovery
  steps.  Nor is there a tool to remedy the situation.
  

Local fix

• Currently there is no documented workaround.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Application Server   *
  *                  V6.1                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When an operation being performed on    *
  *                      a profile terminates in an              *
  *                      unrecoverable fashion, the profile      *
  *                      stays locked.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  As a result of the profile being locked, any further
  operations on the profile are prohibited.
  

Problem conclusion

• By specifying the new "unlock" parameter when invoking the
  manageprofiles script, the user can unlock the profile that is
  currently locked, and hence be able to perform other
  operations on the profile.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.19.  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

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP