IBM Support

PH01829: LRCMD COMMAND FAILS WITH SOCKETTIMEOUTEXCEPTION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using url:
    https://localhost:49080/LongRunningJobSchedulerWebSvcRouter/serv
    ices/JobScheduler
    WebServicesFault
    faultCode:
    {http://schemas.xmlsoap.org/soap/envelope/}Server.generalExcepti
    on
    faultString: WSWS3713E: Connection to the remote host
    localhost:49080 failed.Received the following error:
    java.net.SocketTimeoutException: Socket operation timed out
    before it could be completed
    faultActor: null
    faultDetail:
    
    WSWS3713E: Connection to the remote host localhost:49080
    failed.Received the following error:
    java.net.SocketTimeoutException: Socket operation timed out
    before it could be completed
    at
    com.ibm.ws.webservices.engine.transport.http.HttpOutboundChannel
    Connection.connect(HttpOutboundChannelConnection.java:992)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Java Batch                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Using the lrcmd tool fails with a       *
    *                      SocketTimeoutException and never        *
    *                      completes the operation                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The lrcmd tool does not currently retry its connection attempt
    to the Job Scheduler using http if its initial https
    connection attempt fails with a SocketTimeoutException.  It
    only currently retries on an SSLHandshakeException.
    

Problem conclusion

  • The lrcmd tool has been updated to retry using http if the
    initial https invocation fails with a SocketTimeoutException.
    Previously, this retry would not happen.  Additionally, if no
    user and password were specified on the invocation, the tool
    has been updated to use http and not do the initial secure
    attempt (since there would be no credentials specified).
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 9.0.5.0 and 8.5.5.16.  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

    PH01829

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-16

  • Closed date

    2019-04-18

  • Last modified date

    2019-04-18

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021