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

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 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