PI75160: ADMINTASK.EXTRACTCONFIGPROPERTIES IS FAILED WITH WASRESOURCEEXCEPTION: JAVA.UTIL.NOSUCHELEMENTEXCE

9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• Trying to run the AdminTask.extractConfigProperties wsadmin
  command line to extract cell configuration and getting an error
  as follows:
  
  [wasadm@hkl101607 ~]$
  /opt/IBM/WebSphere85/AppServer/profiles/dmgrprofile/bin/wsadmin.
  sh -lang jython
  WASX7209I: Connected to process "dmgr" on node dmgrnode using
  SOAP connector;  The type of process is: DeploymentManager
  WASX7031I: For help, enter: "print Help.help()"
  wsadmin>AdminTask.extractConfigProperties('[propertiesFileName
  ConfigProperties_cell.props]')
  WASX7015E: Exception running command:
  "AdminTask.extractConfigProperties
  ('[-propertiesFileName ConfigProperties_cell.props]')";
  exception
  information:
  com.ibm.ws.management.wasresource.common.WASResourceException:
  com.ibm.ws.management.wasresource.common.WASResourceException:
  com.ibm.ws.management.wasresource.common.WASResourceException:
  com.ibm.ws.management.wasresource.common.WASResourceException:
  java.util.NoSuchElementException
  
  The default for SERVER_LOG_ROOT is ${LOG_ROOT}/${serverName}
  and the default LOG_ROOT is ${USER_INSTALL_ROOT}/logs which is
  ${WAS_HOME}/profiles/${profileName}/logs directory.  But, the
  console allows user to change to other path, so the
  extractConfigProperties command should not expect its value is
  always ${LOG_ROOT}/${serverName}.
  

Local fix

• The fix will be available in next fixpack release
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: AdminTask.extractConfigProperties       *
  *                      is failed when SERVER_LOG_ROOT is       *
  *                      not set to                              *
  *                      ${LOG_ROOT}/{serverName}                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  AdminTask.extractConfigProperties() command failed with
  com.ibm.ws.management.wasresource.common.WASResourceException:
  java.util.NoSuchElementException
  When user set the SERVER_LOG_ROOT to non default path (default
  path is ${LOG_ROOT}/<serverName>.
  

Problem conclusion

• It is a bug in AdminTask.extractConfigPropeties() command and
  it should not expect the SERVER_LOG_ROOT path always set to
  default ${LOG_ROOT}/<serverName> as the console allows users
  to change to other path.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.12/9.0.0.4.  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

• R850 PSY

     UP

• R900 PSY

     UP