IBM Support

PH38723: JMS UPGRADE FROM 7.1.0.3 TO 7.1.2.1 FORCES JMS TO WEB UPGRADE WITH INVALID DEFAULT SERVER.URI 'LOCALHOST'

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 upgrading a JMS agent from 7.1.0.3 to 7.1.2.1 through the
    UI without using an Agent Configuration Template, the agent
    fails to connect and it is upgraded to web by adding these
    properties:
    agentcomm.enabled=true
    agentcomm.server.uri=random\:(wss\://localhost\:7919)
    
    Issues:
    1. The agent version upgrade enforces the JMS to Web migration
    with default value of
    "agentcomm.server.uri=random\:(wss\://localhost\:7919)" when no
    "Agent Configuration Template" is configured for the upgrade.
    2. When an "Agent Configuration Template" is configured for the
    agent upgrade with a specific server URL
    "wss//<UCD_server_host>:7919", the upgrade doesn't respect the
    config template and still uses the default value of
    "agentcomm.server.uri=random\:(wss\://localhost\:7919)".
    

Local fix

  • Manually upgrade the agent to stay with JMS, or finish the JMS
    to Web migration by manually changing the server.uri to the
    correct value.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When upgrading a JMS agent from 7.1.0.3 to 7.1.2.1 through   *
    * the                                                          *
    * UI without using an Agent Configuration Template, the agent  *
    * fails to connect and it is upgraded to web by adding these   *
    * properties:                                                  *
    * agentcomm.enabled=true                                       *
    * agentcomm.server.uri=random\:(wss\://localhost\:7919)        *
    *                                                              *
    * Issues:                                                      *
    * 1. The agent version upgrade enforces the JMS to Web         *
    * migration                                                    *
    * with default value of                                        *
    * "agentcomm.server.uri=random\:(wss\://localhost\:7919)" when *
    * no                                                           *
    * "Agent Configuration Template" is configured for the         *
    * upgrade.                                                     *
    * 2. When an "Agent Configuration Template" is configured for  *
    * the                                                          *
    * agent upgrade with a specific server URL                     *
    * "wss//<UCD_server_host>:7919", the upgrade doesn't respect   *
    * the                                                          *
    * config template and still uses the default value of          *
    * "agentcomm.server.uri=random\:(wss\://localhost\:7919)".     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 7.1.2.3                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 7.1.2.3
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH38723

  • 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-07-06

  • Closed date

    2021-09-02

  • Last modified date

    2021-09-02

  • 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":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"712"}]

Document Information

Modified date:
03 September 2021