Automatic client reconnection
You can make your client applications reconnect automatically, without writing Table 1 lists the earliest release of IBM® WebSphere® MQ client support that. Problem Description: JMS Connector does not reestablish connection to the queue when a queue on a live MQ QManager is disabled and then. stops after all applications have disconnected. Control returns WebSphere MQ client applications do not need to change to connect to new versions of a queue manager. It also means that an End of Service dates for WebSphere MQ - url.
To learn how to configure these options, use the information in this note and in the attached PDF document.MQ: Security: Message Channel Agent MCA authentication basics, CHLAUTH basics
Content The processes described here have been tested with the following configurations: The amqsputc sample MQ application, with the automatic client reconnect option disabled. The amqsphac high availability put sample MQ application, with the automatic client reconnect option enabled. MQ Explorer, with the automatic client reconnect option disabled.
If you already have some knowledge and experience in this area, here is a set of example commands for using runmqsc to identify MQ client connections and stop them: Ensure to replace QMGR with the proper values for your system: One possible way to apply this information is to create a cron job that issues the mentioned command and if the number of running channels is getting closer to the MaxChannels, then an MQ Administrator might be notified.
The following technote could be used as a reference for creating a cron job: A system that is busy serving connections from the network might need a higher number than the default setting.
IBM How to identify MQ client connections and stop them - United States
Determine the value that is correct for your environment, ideally by observing the behavior of your system during testing.
You do not have to specify this. If you do not, a transmission queue with the same name as the target queue manager is used, or, if this does not exist, the default transmission queue is used.
The XMITQ name must match the remote queue manager name in order for remote administration to work, unless you are using a queue manager alias. System Admin, SC, page 62 You are advised to create a DLQ for any queue manager you define You are advised to know the name of the default queue manager and verify it exists: It could be a problem in a cluster MQS How to dump a queue to a file?
- IBM MQ Connector
Display queue status details. DSPMQ - display all queue manages names and status.
There is no default. Default value is Default is milliseconds, more than 11 days.
The default is no dead-letter queue. Default value is 10 uncommitted messages.
Min 64, maxthis is MB This determines on which queue the queue manager performs subsequent operations.