| Author |
Message
|
| matuwe |
 Posted: Wed Dec 17, 2008 10:07 pm Post subject: |
 |
|
Master
Joined: 05 Dec 2007
Posts: 296
|
 Thanks a mill times, My server has been rebooted and now MQ is responding perfectly. Now I need to get to the root cause of the probem.
I have been reading this article
http://www.ibm.com/developerworks/websphere/library/techarticles/0801_cui/0801_cui.html
and it suggest that I change my /var/mqm/qmgrs/(<queue_manager_name>)/qm.ini and increase
MaxChannels=<channel_no>
MaxActiveChannels=<channel_no>
This values do not exist on my stanza and will it help if I increase LogBufferPages=0 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Dec 18, 2008 12:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
To be specific the post referenced said:
| Quote: |
Input/output count too high
First check if there are any exceptions in the flow using the procedures described above. If system performance is okay, increase the maximum connection parameter of the queue manager: edit the file /var/mqm/qmgrs/(<queue_manager_name>)/qm.ini and modify the following lines to change <channel_no> to the desired number:
CHANNELS:
MaxChannels=<channel_no>
MaxActiveChannels=<channel_no>
|
From the probe Id and other things you posted, you have given us no hint that this would be the problem you are facing. So why do you think that this would solve it?
What is the output of
| Code: |
| echo 'dis chs(*)' | runmqsc QMGR | grep CONNAME |cat -n |tail -5 |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| matuwe |
| Posted: Thu Dec 18, 2008 12:50 am Post subject: |
|
|
Master
Joined: 05 Dec 2007
Posts: 296
|
|
| Back to top |
|
|
| matuwe |
| Posted: Thu Dec 18, 2008 1:02 am Post subject: |
|
|
Master
Joined: 05 Dec 2007
Posts: 296
|
Sorry I ran the runmqc command and the display channel. this is my results
DISPLAY CHANNEL (*) CONNAME
6 : DISPLAY CHANNEL (*) CONNAME
AMQ8414: Display Channel details.
CHANNEL(HUB.ADMIN.SVRCONN) CHLTYPE(SVRCONN)
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.AUTO.RECEIVER) CHLTYPE(RCVR)
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.AUTO.SVRCONN) CHLTYPE(SVRCONN)
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.BKR.CONFIG) CHLTYPE(SVRCONN)
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.DEF.CLUSRCVR) CHLTYPE(CLUSRCVR)
CONNAME( )
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.DEF.CLUSSDR) CHLTYPE(CLUSSDR)
CONNAME( )
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.DEF.RECEIVER) CHLTYPE(RCVR)
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.DEF.REQUESTER) CHLTYPE(RQSTR)
CONNAME( )
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.DEF.SENDER) CHLTYPE(SDR)
CONNAME( )
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.DEF.SERVER) CHLTYPE(SVR)
CONNAME( )
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN)
AMQ8414: Display Channel details.
CHANNEL(SYSTEM.DEF.CLNTCONN) CHLTYPE(CLNTCONN)
CONNAME( ) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 18, 2008 1:07 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY
|
Ah but you did not run the command as I asked for it.
This is a list of the channels... I asked for a list of the channel STATUS....
Increasing the number of log files (primary and secondary) is a good start. Make sure you have the filespace for it. And remember this will only take effect after a qmgr restart.
Also you should take a hard look at your MQ and broker transaction management and the max size of a single transaction, max time of a single transaction, plan and add safety margins for concurrency...
Would not have switched the log from triplewrite to singlewrite. This is an OS reliability and HIGH throughput consideration. Does not look like you are hitting any of those.
Just because stuff exists does not mean that implementing it will fix your problem.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| matuwe |
| Posted: Thu Dec 18, 2008 1:56 am Post subject: |
|
|
Master
Joined: 05 Dec 2007
Posts: 296
|
Ohhh I see. I just emplimented as the exaple suggested..  Thanks.
If I run the command as you send it, it doesn't return any results. 
Would it help if I deployed my http input flow twice? I don't think I have perfomance problems but this semaphone...  always make me cry.  |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 18, 2008 2:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| matuwe wrote: |
| If I run the command as you send it, it doesn't return any results. |
And what does this tell you......?
| matuwe wrote: |
| Would it help if I deployed my http input flow twice? |
Why not deploy it while holding a lucky rabbit's foot? Or with arcane symbols chalked on the back of the server to conjure the positive energies? All are unlikely to help but can't hurt. Well, might hurt your reputation.
(Don't deploy while sprinkling holy water on the server. That doesn't help. And does hurt if you don't jump back quickly enough....  )
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| matuwe |
| Posted: Thu Dec 18, 2008 2:14 am Post subject: |
|
|
Master
Joined: 05 Dec 2007
Posts: 296
|
 ooowwwwccchhh!!! I get it. Will not try it. I am just trying to find solution and better ways to do load distribution.
Okay i guess it means I just need to wait and see if I donot get this problem again. Thanks for all you help. Much appreciated  |
|
| Back to top |
|
|
|
|
