IBM Support

PH41044: AN AGENT USING AN AGENT-RELAY THAT FAILS-OVER TO A COLD STANDBY SERVER URI, WILL NOT SWITCH BACK TO ANOTHER SERVER.

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

  • If an Agent has been configured with a Relay and multiple
    server WSS URIs, an IOException while communicating with
    one of the URIs may cause it to switch to an alternate URI.
    
    If the relay can not connect to the alternate URI, e.g. a
    cold-standby,
    the agent will not automatically switch to a valid WSS URI until
    restarted.
    
    Stack Trace:
    YYYY-MM-DD HH:MM.SS,MILLI EDT INFO  netty-pool-0
    com.urbancode.air.devilfish.agentcomm.ServerConnectionInfo - Set
    preferred path: {. -> <Preffered Host>:20080 -> wss://<Preffered
    Host>:7920}
    YYYY-MM-DD HH:MM.SS,MILLI EDT ERROR netty-pool-0
    com.urbancode.air.devilfish.agentcomm.GenericExceptionHandler -
    Closing channel on exception: ch=e7c6462b local=<IP
    Address>:51433 remote=<IP Address>:20080 peer=<unknown>
    cause=ProxyConnectException message={http, none, <Host Name>/<IP
    Address>:20080 => <Host Name>/<IP Address>:7921, status: 502 Bad
    Gateway}
    YYYY-MM-DD HH:MM.SS,MILLI EDT INFO  netty-pool-1
    com.urbancode.air.devilfish.agentcomm.ServerConnectionInfo -
    Unset preferred path: {. -> <Preffered Host>:20080 ->
    wss://<Preffered Host>:7920}
    YYYY-MM-DD HH:MM.SS,MILLI EDT DEBUG netty-pool-1
    com.urbancode.air.devilfish.agentcomm.ServerConnectionInfo -
    Path demotion reason: no cause provided
    java.lang.Exception: no cause provided
        at
    com.urbancode.air.devilfish.agentcomm.ServerConnectionInfo.pathI
    sBad(ServerConnectionInfo.java:144)
        at
    com.urbancode.air.agent.comm.AgentWSClient.pathIsBad(AgentWSClie
    nt.java:162)
        at
    com.urbancode.air.agent.comm.AgentWSClient.channelClosed(AgentWS
    Client.java:297)
        at
    com.urbancode.air.agent.comm.AgentWSClient.lambda$1(AgentWSClien
    t.java:203)
        at
    io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultP
    romise.java:578)
        at
    io.netty.util.concurrent.DefaultPromise.notifyListenersNow(Defau
    ltPromise.java:552)
        at
    io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultP
    romise.java:491)
        at
    io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise
    .java:616)
        at
    io.netty.util.concurrent.DefaultPromise.setSuccess0(DefaultPromi
    se.java:605)
        at
    io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromis
    e.java:104)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Agents connecting through relays                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If an Agent has been configured with a Relay and multiple    *
    * server WSS URIs, an IOException while communicating with     *
    * one of the URIs may cause it to switch to an alternate URI.  *
    *                                                              *
    * If the relay can not connect to the alternate URI, e.g. a    *
    * cold-standby,                                                *
    * the agent will not automatically switch to a valid WSS URI   *
    * until                                                        *
    * restarted.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in 7.2.1.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH41044

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-10-01

  • Closed date

    2021-12-17

  • Last modified date

    2021-12-17

  • 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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"712"}]

Document Information

Modified date:
18 December 2021