| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ6150 : MQSeries semaphore is busy |
« View previous topic :: View next topic » |
| Author |
Message
|
| Giraf |
 Posted: Thu Apr 18, 2002 9:14 pm Post subject: |
 |
|
Newbie
Joined: 17 Apr 2002
Posts: 4
Location: Belgium
|
We run an MQserver on AIX with about 100 clients. When the system is heavy loaded, the runmqlsr sometimes shows the AMQ6150 : MQSeries semaphore is busy ( xecL_W_LONG_LOCK_WAIT ) and the client fails connection.
Is there a parameter which we can set to raise the timeout on the wait ? |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Fri Apr 19, 2002 3:39 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
One possibility is the max active channels is 100 hundred in the qm.ini file. This parm is set in the qm.ini file /var/mqm/qmgrs/QMGR_NAME/
see http://publibfp.boulder.ibm.com/epubs/html/amqzag02/amqzag02tfrm.htm
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| DEEPThought |
| Posted: Tue Jun 04, 2002 4:48 am Post subject: I have 12 defined channels and only one client |
|
|
Newbie
Joined: 04 Jun 2002
Posts: 4
|
Hi, i have 12 channels defined on my qmanager and a Domino app as client, but i have the same problem. On my linux box i have 16 Qmanagers with default parms in INI files.
If the default value si 100, i think my average is lower!
After several months without problems, and no changes in the application, i found this in the error log:
-------------------------------------------------------------------------------
06/01/02 05:07:01
AMQ6150: MQSeries semaphore is busy.
EXPLANATION:
MQSeries was unable to acquire a semaphore within the normal timeout period of
0 minutes.
ACTION:
MQSeries will continue to wait for access. If the situation does not resolve
itself and you suspect that your system is locked then investigate the process
which owns the semaphore. The PID of this process will be documented in the
accompanying FFST.
-------------------------------------------------------------------------------
06/01/02 05:07:01
AMQ6184: An internal MQSeries error has occurred on queue manager M1S07000PRDE.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 1173.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
for every qmanager in my box.
today, the qmanagers are unreachables....
now i try to restart them, but i know this is not a solution!
Any idea?
Thanks in advance, Alessandro
_________________
"Under my flag, i live free." - Captain Harlock |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Jun 04, 2002 9:53 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well client channels are different than other channels just because you have 12 defined that does not mean that you can only have 12 active, one svrconn channel can have as many connections as allowed by MAX Channels
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
