IBM Support

PM35691: COMMENTING OUT PROPERTIES FOR LOGING IN SOAP.CLIENT.PROPS CAUSES SERVER NOT TO STOP

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Commenting out the following properties in soap.client.props
    causes the server not to stop.
    
    #com.ibm.SOAP.loginUserid=xxxxxxxx
    
    #com.ibm.SOAP.loginPassword=xxxxxxxx
    
    The following error is displayed and security prompt will not
    occur.
    
    $ ./stopManager.sh
    
    ADMU0116I: Tool information is being logged in file
    
    /hosting/configs/WebSphereD06/DeploymentManager/logs/dmgr/stopSe
    rver.log
    ADMU3100I: Reading configuration for server: dmgr
    ADMU0111E: Program exiting with error: javax.management.
    JMRuntimeException:
    ADMN0022E: Access is denied for the stop operation on
    Server MBean because of insufficient or empty credentials.
    ADMU4113E: Verify that username and password information is
    correct.  If running tool from the command line, pass in the
    correct -username and -password.  Alternatively, update the
    <conntype>.client.props file.
    ADMU1211I: To obtain a full trace of the failure, use the -trace
    option.
    ADMU0211I: Error details may be seen in the file:
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
    *                  who comment out the userid and password     *
    *                  properties in soap.client.props.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: A user stopping a server will not get   *
    *                      prompted to enter userid and            *
    *                      password. The command fails with        *
    *                      access denied.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere Application Server command line tools that have
    username and password parameters do not prompt for these when
    the corresponding properties are commented out in
    soap.client.props. Here is an example:
    $ ./stopManager.sh
    ADMU0116I: Tool information is being logged in file
    /hosting/configs/WebSphereD06/DeploymentManager/logs/dmgr/stopSe
    rver.log
    ADMU3100I: Reading configuration for server: dmgr
    ADMU0111E: Program exiting with error: javax.management.
    JMRuntimeException:
    ADMN0022E: Access is denied for the stop operation on Server
    MBean because of insufficient or empty credentials.
    ADMU4113E: Verify that username and password information is
    correct. If running tool from the command line, pass in the
    correct - username and -password. Alternatively, update the
    <conntype>.client.props file.
    ADMU1211I: To obtain a full trace of the failure, use the
    -trace option.
    ADMU0211I: Error details may be seen in the file:
    /hosting/configs/WebSphereD06/DeploymentManager/logs/dmgr/stopSe
    rver.log
    

Problem conclusion

  • The code has been updated to handle the case of missing
    com.ibm.SOAP.loginUserid and com.ibm.SOAP.loginPassword
    properties in soap.client.properties.
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.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 number

    PM35691

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-25

  • Closed date

    2011-04-18

  • Last modified date

    2011-08-03

  • 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

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021