PM09699: PROFILE MANAGEMENT TOOL (PMT) HANGS IF IT DOES NOT HAVE PERMISSION TO READ SERVERINDEX.XML IN OTHER PROFILES

6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
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.47: WebSphere Application Server V6.1 Fix Pack 47
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

APAR status

• Closed as program error.

Error description

• The Profile Management Tool (PMT) can potentially hang after
  choosing the port assignments for a new profile.  The hang will
  occur after pressing the "Next" button on the port assignments
  panel.
  
  The pmt.log file indicates what the issue is.  An exception
  appears near the bottom of the log, which looks like the
  following:
  
  com.ibm.wsspi.profile.WSProfileException:
  java.io.FileNotFoundException: <profile_path>\config\cells\
  cell_name\nodes\node_name\serverindex.xml
  (Access is denied.)
  com.ibm.ws.profile.utils.PortResolutionUtils.createPortConflictR
  esolver(PortResolutionUtils.java:872)
  com.ibm.ws.profile.utils.PortResolutionUtils.recommendPorts(Port
  ResolutionUtils.java:214)
  ...
  
  This error occurs when PMT is attempting to check the ports
  selected for the profile.  PMT will compare the selected ports
  with the ports which are defined in other WebSphere Application
  Server profiles.  To do this, the PMT tool reads the
  serverindex.xml file in each profile that the PMT tool is aware
  of.  It is possible that other profiles are owned by different
  users, and therefore PMT does not have permission to read the
  serverindex.xml files in other profiles.  When PMT encounters a
  serverindex.xml file that it does not have permission to read,
  it will hang.
  

Local fix

• The issue can be avoided by changing the permissions or
  ownership of other profiles in a manner that allows the current
  user to read files in those other profiles.
  
  Alternatively, this issue can be avoided by using the
  command-line manageprofiles tool to create a new profile.  When
  using the command-line manageprofiles tool to avoid this issue,
  be sure not to use the "-validatePorts" option.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All non-root users of IBM WebSphere         *
  *                  Application Server V6.1                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Profile Management Tool (PMT) can   *
  *                      potentially hang after clicking         *
  *                      'next' on "Environment Selection" panel.*
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  All the "serverindex.xml" files located at
  {WAS_HOME}/profiles/{profile_name}/cells/{cell_name}/nodes/{node
  _name}from existing profiles are checked to avoid port conflict
  during profile creation.
  If a user has no read access to any of the "serverindex.xml"
  files, PMT £â‚¬â‚¬will hang. The pmt.log will show which
  "serverindex.xml" file that the user has no read access to.
  

Problem conclusion

• To fix this, the user access right is checked before accessing
  any of the serverindex.xml files during port conflict
  resolution to avoid inaccessible cases. Any inaccessible
  serverindex.xml files will be logged to pmt.log.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.33.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Grant user the read access to all necessary "serverindex.xml"
  file(s)
  

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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP