IBM Support

PK90174: ADDNODE FAILS WITH COM.IBM.CORBA.LOGINSOURCE=NONE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • addNode fails with FileNotFoundException when
    com.ibm.CORBA.loginSource=none in both the the Deployment
    Manager and AppServer.
    .
    BBOO022I: ADFS0119E: An unexpected exception occurred:
    java.io.FileNotFoundException: File download failed:
    java.io.IOException: Can not authorize
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Customers of IBM WebSphere Application       *
    *                 Server V7.0 for z/OS who use the             *
    *                 addNode command with conntype RMI and        *
    *                 property com.ibm.CORBA.loginSource=none      *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: On z/OS, addNode command fails when     *
    *                      using conntype RMI, loginSource=none,   *
    *                      and with no username/password on the    *
    *                      command line.                           *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When running the addNode command using conntype RMI, and
    com.ibm.CORBA.loginSource=none in the sas.client.props file
    it is necessary to provide a username and password on the
    command line EXCEPT on the z/OS platform. On z/OS, this
    scenario should work without a username and password,
    since the logged-in user's credentials are inherited.
    However, the Application Server code is not handling this
    scenario correctly. On z/OS, the inherited credentials are not
    being passed to the filetransfer service, and as a result a
    TransferFailedException is thrown. Here is a sample excerpt of
    the output from the addNode.sh command on z/OS under this
    scenario:
    
    ADMU0026I: An error occurred during federation; rolling back
    to original configuration.
    ADMU0113E: Program exiting with error:
    com.ibm.websphere.management.exception.AdminException:
    com.ibm.websphere.management.filetransfer.client.TransferFailedE
    xception:
    Credentials are not authenticated:
    com.ibm.ws.security.auth.WSCredentialImpl@4d1e4d1e, resulting
    from:
    com.ibm.websphere.management.filetransfer.client.TransferFailedE
    xception:
    Credentials are not authenticated:
    com.ibm.ws.security.auth.WSCredentialImpl@4d1e4d1e
    

Problem conclusion

  • The code was updated to allow the necessary credentials to be
    inherited by the filetransfer client during the addNode
    operation. With this fix in place, addNode will work on z/OS
    with conntype RMI, com.ibm.CORBA.loginSource=none in
    sas.client.props, and no username or password provided on the
    command line.
    
    This fix does not affect the outcome of this scenario on
    non-z/OS platforms ?- on such platforms, when running addNode
    using conntype RMI and com.ibm.CORBA.loginSource=none in
    sas.client.props, a username and password is required on the
    command line, as stated in the Information Center documentation.
    
    APAR PK90174 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.5 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK90174

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-29

  • Closed date

    2009-07-08

  • Last modified date

    2009-08-03

  • APAR is sysrouted FROM one or more of the following:

    PK73686

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK48201

       UP09/07/27 P F907

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022