Fixing poor system performance and events that are not processing
If the system is performing very slowly and system events
are not processing, there may be a problem with the WebSphere MQ
publish/subscribe broker.
Note:
this only applies to UNIX systems.
- Open the file /var/mqm/qmgrs/<queue manager name>/qm.ini
and look for the following entry:
MaxActiveChannels=1000Broker:
If you see this entry, replace the Channels and Broker parameters
with the following:
Channels:
- MaxChannels=1000
- MaxActiveChannels=1000
- SyncPointIfPersistent=yes
- Save your changes.
- Shut down WebSphere Partner Gateway (see Stopping
the Community Console and Stopping
the Receiver and Document Manager).
- Stop WebSphere MQ using the following steps:
- Stop the publish/subscribe broker, by entering the following:
endmqbrk -m <hostname>.queue.manager
- Stop the listener, by entering the following:
endmqlsr -m <hostname>.queue.manager
- Stop the queue manager, by entering the following:
endmqm <hostname>.queue.manager
- Create and start WebSphere MQ, using the instructions in the WebSphere Partner Gateway Installation Guide.
However, do not perform steps 2 through 4 in the procedure.
- Restart WebSphere Partner Gateway, using the instructions in
the WebSphere Partner Gateway Installation Guide.
