技术咨询：Queue Manager是否可能加载旧配置？通道出现旧ciphers

Absolutely, your Queue Manager can end up loading an older configuration if it picked up a backup—this is almost certainly why your channel cipher suites are showing the old values instead of your recent changes. Let’s break down the key reasons and steps to fix this:

• Backup was taken before your cipher changes: If the backup configuration file was created prior to when you modified the two channels’ cipher suites, restoring that backup will roll back all settings (including your channel configs) to the state they were in when the backup was made. That’s the most likely culprit here.
• Channel config activation might not have been completed (less likely here): While unrelated to the backup, it’s worth noting that sometimes cipher changes require restarting the channel or forcing the Queue Manager to refresh its configuration. But since you explicitly mentioned the Queue Manager loaded a backup, this is probably not the issue.

Steps to Resolve: #

1. Verify backup timing: Check the timestamp of the backup configuration the Queue Manager loaded. If it’s earlier than your cipher modification timestamp, that confirms the backup overwrote your changes.
2. Reapply your cipher suite changes: Use the MQ command line tools to update the channels again. For example:

   ALTER CHANNEL(YOUR_CHANNEL_NAME) CHLCIPH(your-new-cipher-suite)
   

   After running this, restart the affected channels to ensure the new settings take effect.
3. Create a fresh backup: Once your changes are confirmed to be working, generate a new backup of the Queue Manager configuration. This ensures that if any future backup loads happen, it will use your updated settings.

If you’re unsure how the Queue Manager ended up loading the backup in the first place, you can also check its logs for events related to configuration restoration—this might reveal if it was triggered manually, via an automated process, or due to a failure recovery.

内容的提问来源于stack exchange，提问作者Rinak