| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue Manager's channels hang-up issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| vnreddy |
 Posted: Thu Sep 29, 2005 11:21 am Post subject: Queue Manager's channels hang-up issue |
 |
|
Novice
Joined: 01 May 2003
Posts: 23
Location: UK
|
All,
We are facing the queue manager's channels hang-up issue many times in our Solaris system with a WMQ 5.3 CSD10 installed. We found no response when we issue dis chs(*) command.
We have received channels hang-up issue for only one queue manager which used a gateway queue manager to communicate to the end-points.
Is any experienced this kind of issue?. Is there any thing that I can tune up in system configuration.?
Do we need to change any semaphores and file descriptor values for this issue.? Currently the file descriptor value is set to 1024.
The current system semaphores values are as below. we have more than 20 queueu managers are running in the same system.
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmseg=16384
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=16384
*
set semsys:seminfo_semmni=2048
set semsys:seminfo_semaem=16384
set semsys:seminfo_semvmx=32767
set semsys:seminfo_semmns=147456
set semsys:seminfo_semmsl=16384
set semsys:seminfo_semmnu=2048
set semsys:seminfo_semume=256
set semsys:seminfo_semmap=2000
set semsys:seminfo_semopm=750
*
set msgsys:msginfo_msgmap=1026
set msgsys:msginfo_msgmax=32768
set msgsys:msginfo_msgmnb=65536
set msgsys:msginfo_msgmni=256
set msgsys:msginfo_msgssz=32
set msgsys:msginfo_msgseg=8192
set msgsys:msginfo_msgtql=512
*
set rlim_fd_cur=1024
Thanks in advance
N Reddy |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Sep 29, 2005 11:38 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| We found no response when we issue dis chs(*) |
So all your channels are in an "Inactive" state. This doesn't show any channel issues.
| Quote: |
| We are facing the queue manager's channels hang-up issue |
I think we need a little more information about what you are seeing, and why you think it is an "issue".
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| vnreddy |
| Posted: Thu Sep 29, 2005 12:01 pm Post subject: |
|
|
Novice
Joined: 01 May 2003
Posts: 23
Location: UK
|
We did not know what was the channel status as this is because we never get any respone received from dis chs(*) command.
But we can see all MQ processes appear in the system when we issue ps -ef ! grep mq command
All the messages ended up at endsite queue manager side to deliver to our queue manager.
Later found that channels are hanp-up, so we stopped the queue managers,then we cleared the semaphores and then started queue manager back.After restart we found channels are running fine.
We faced this issue many times,in all the times we were stopping,clear the sempaphores and start the queue manager back.
Thanks in Advance
N reddy |
|
| Back to top |
|
|
| csmith28 |
| Posted: Thu Sep 29, 2005 12:50 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
an inactive channel does not equate to a hung channel, if you are seeing
| Code: |
| Channel Status not found. |
when you run the dis chs(*) is simply means the channel has ended normally.
Look in your /opt/mqm/qmgrs/MQMGR/error/AMQERR01.LOG and you will likely see an entry for the channel ending normally unless it is a SVRCONN channel.
If you enter runmqsc then execute the dis chs(*) and get no response at all then it's not just the channels that are hung but the MQManager itself is likely hung. If that is the case you should be able to find out why by looking for FFST in /opt/mqm/errors.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| JT |
| Posted: Thu Sep 29, 2005 1:03 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| We did not know what was the channel status as this is because we never get any respone received from dis chs(*) command |
Do you have a Windows server or desktop available with MQ installed ?
If so, add the Solaris queue manager to the WebSphere MQ Explorer. From there you can display the status of your channels, regardless of their state (inactive, active, binding, retrying, etc...). |
|
| 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
|
|
|
|
