Modification of client prefix ignored in IS 9.5 admin UI

, ,
1

Hello all,

I’ve stumbled upon what I think is a bug in the administration interface of IS 9.5.1, observed both with an unfixed IS and with IS_9.5_SP1_Core_Fix2.

Here’s the scenario:

I go to Settings > Messaging > webMethods Messaging Settings
I click on the default system generated Broker Connection alias
I click on Edit Broker Connection Alias
I fill in the form with the parameters to connect to the Broker, specifying a custom client prefix at the same time
I click on Save Changes

Result:
When the page reloads after the Save Changes button is clicked, I see my custom value for the client prefix, but when I click on Edit Broker Connection Alias, the old value is back again.
I checked the dispatch.cnf file and it contains the old value, and the Default Client created on the broker has the old value as client prefix too, so it looks like my custom value was ignored.

I plan to open an incident with SAG support for this, but I would like to know if anyone has encountered it before because it would surprise me if I were the first to raise the issue, since this is a pretty basic configuration operation. Has it been corrected in a recent fix?

2

Hi Fab,

Let me re-produce the same scenario on wM 9.5 and I will update you the results.

3

Hi,

did you restart the IS after saving?

This is still necessary otherwise the settings will not be persisted and activated.

There should be an info box on top of the page after saving which indicates that the restart is required.

HTH,
Holger

4

After saving, I activated the Connection Alias, activation status was “Yes (Pending Restart)” on the UI, then I restarted IS from the Shutdown & Restart page.

After restart, the Connection Alias activation status was “Yes”, but the client prefix was still the old value, and the Default Client created on the Broker had the old value as client prefix.

EDIT:

I just ran some more tests and managed to pinpoint exactly how to replicate it.

1st test:

Broker connection activation status is “No” at the start of the procedure.
Edit broker connection settings and modify the client prefix value, save changes, then restart.

Result: Client prefix value is updated correctly on the admin UI.

2nd test:

Broker connection activation status is “Yes” at the start of the procedure.
Edit broker connection settings and modify the client prefix value, save changes, then restart.

Result: Client prefix value is updated correctly on the admin UI, clients on the Broker are created with the new client prefix.

3rd test:

Broker connection activation status is “No” at the start of the procedure.
Edit broker connection settings and modify the client prefix value, save changes.
Activate the Broker connection alias (set activation status to “Yes”), then restart.

Result: Client prefix value retains its old value on the admin UI, Broker connection alias activation status is “Yes” on the admin UI, and clients on the Broker are created using the old value.

4th test:

Broker connection activation status is “No” at the start of the procedure.
Activate the Broker connection alias (set activation status to “Yes”).
Edit broker connection settings and modify the client prefix value, save changes.
Restart IS

Result: Client prefix value is updated correctly on the admin UI, clients on the Broker are created with the new client prefix.

Conclusion:

It looks like when you switch the activation status of the Broker connection alias from “No” to “Yes”, any changes previously made to the client prefix in the connection alias configuration is ignored after restart.
I also tested when switching from “Yes” to “No” and had the same result.

On the other hand, if you modify the client prefix after swtiching activation status, it is taken into account.