IBM Support

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

Subscribe

You can track all active APARs for this component.

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 number

    PI75160

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-18

  • Closed date

    2017-03-16

  • Last modified date

    2017-03-16

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI75160

Modified date: 16 March 2017


Translate this page: