IBM Support

PM64146: IMPROVE THE ERROR MESSAGE WHEN SYNCNODE FAILS AFTER FIPS UPDATE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With additional FIPS options avaiable in the V8 security
    configuration it is more likely that customers could miss
    updating ssl.client.props and see this error when running
    syncNode.
    
    ADMU0113E: Program exiting with error:
    
    com.ibm.websphere.management.exception.ConnectorException:
    ADMC0016E: The system cannot create a SOAP
    connector to connect to
    host localhost at port 8881., resulting from:
    [SOAPException:
    faultCode=SOAP-ENV:Client; msg=Error parsing HTTP
    status line
    "??? ??": java.util.NoSuchElementException;
    targetException=java.lang.IllegalArgumentException:
    Error parsing
    HTTP status line "??? ??":
    java.util.NoSuchElementException]
    ADMU4123E: Ensure that the Deployment Manager is running on
    the specified host and port.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server v8.0 and V8.5 Network Deployment     *
    *                  edition.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the security configuration at      *
    *                      the deployment manager is modified to   *
    *                      enable or modify FIPS, it is required   *
    *                      for the administrator to make also      *
    *                      update to the ssl.client.props file     *
    *                      at all nodes in the cell. If this is    *
    *                      not done, attempts to connect to the    *
    *                      deployment manager from the node will   *
    *                      fail.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When this situation is present the following error will be
    logged in syncNode.log:
    ADMU0113E: Program exiting with error:
    com.ibm.websphere.management.exception.ConnectorException:
    ADMC0016E: The system cannot create a SOAP
    connector to connect to
    host localhost at port 8881., resulting from:
    [SOAPException:
    faultCode=SOAP-ENV:Client; msg=Error parsing HTTP
    status line
    "??? ??": java.util.NoSuchElementException;
    targetException=java.lang.IllegalArgumentException:
    Error parsing
    HTTP status line "??? ??":
    java.util.NoSuchElementException]
    ADMU4123E: Ensure that the Deployment Manager is running on
    the specified host
    and port.
    and trace of com.ibm.*=all from syncNode.sh/.bat will show:
    [2/20/12 16:35:02:202 EST] 00000000 SOAPConnector <  reconnect
    Exit
    [SOAPException:
    faultCode=SOAP-ENV:Client; msg=Error opening socket:
    javax.net.ssl.SSLHandshakeException: Received fatal alert:
    handshake_failure;
    targetException=java.lang.IllegalArgumentException: Error
    opening socket: javax.net.ssl.SSLHandshakeException: Received
    fatal alert: handshake_failure]
    at
    org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPC
    onnection.java:475)
    at org.apache.soap.rpc.Call.WASinvoke(Call.java:451)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(S
    OAPConnectorClient.java:372)
    at
    com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
    troller.java:118)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconne
    ct(SOAPConnectorClient.java:365)
    ...
    

Problem conclusion

  • Message ADMU4123E was augmented to suggest checking the FIPS
    configuration on the node as a possible cause of the problem.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.4 and 8.5.0.1.  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

    PM64146

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-08

  • Closed date

    2012-07-24

  • Last modified date

    2012-07-24

  • 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

  • R800 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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021