PM82147: When running an app in same JVMas container/catalog, if a failure occurs, a reconnection may not happen.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • When running a user application in the same
    JVM container/catalog and if the connection is dropped, then
    the remote server does not attempt to reconnect to what appears
    to be a client only system.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users that have enabled the eXtremeIO       *
    *                  protocol.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: An exception                            *
    *                      ConnectionRefusedException              *
    *                      is encounterd by eXtreme Scale clients  *
    *                      connecting to a newly started           *
    *                      server.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    eXtreme Scale clients, or servers, may encounter a
    ConnectionRefusedException exception  when attempting to
    contact an eXtreme Scale server that has just started.  The
    "causedby" tag in the exception message will include a
    host:port where the port is a zero value.
    

Problem conclusion

  • There was a timing window on startup where outbound traffic
    can happen in the server prior to the inbound eXtremeIO
    transport listener starting. The remote targets contacted
    during this window will then be informed of an incorrect
    server listening port of zero, which means that remote target
    cannot later open a socket back to this server. This has been
    fixed in eXtremeScale 8.6.0.1 and higher.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82147

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-05

  • Closed date

    2013-06-21

  • Last modified date

    2013-06-21

  • 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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

  • R860 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere eXtreme Scale

Software version:

860

Reference #:

PM82147

Modified date:

2013-06-21

Translate my page

Machine Translation

Content navigation