| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| RetryConnectToSharedSubpool Mercator error |
« View previous topic :: View next topic » |
| Author |
Message
|
| tjfunny1 |
 Posted: Wed Jan 08, 2003 9:36 am Post subject: RetryConnectToSharedSubpool Mercator error |
 |
|
Apprentice
Joined: 17 Jun 2002
Posts: 35
Location: Atlanta
|
I'm getting huge FDC's from a mercator application called launcher, running on a AIX 4.3 box. We have MQ version 5.2 installed.
It seems this mercator process kicks off threads to check the status of queues. From my research, I found that it creates over 556 errors in 189 seconds. I think it's using MQCONNX to connect to the qmgr (the reason I think that is due to options it has regarding whether to use client or server connections w/o recompiling their code).
The major error is 6206, xstConnectSegmentViaFile rc=Unknown(6206), but you will notice a IPCC error above it. I didn't include the full printout, just the lines that had RC >0. Since MQ will not give an exact description of the error (Unknown), we can't locate the problem.
I don't have a TuningParameters stanza in the qm.ini of the qmgr used. I've seen some posts that refer to adding:
IPCCECSetSize = 1000000
IPCCExtensionSize = 128000
DefaultQMemSetSize= 2000000
IPCCBaseAddress=11
Should I try these in the qm.ini file of the qmgr or the mqs.ini file in /var/mqm, under the TuningParameter stanza?
Thanks for any help, TJ
=====================================
|
| Date/Time :- Tuesday January 07 16:27:44 EST 2003
| Host Name :- testbox (AIX 4.3)
| PIDS :- 5765B73
| LVLS :- 520
| Product Long Name :- MQSeries for AIX
| Vendor :- IBM
| Probe Id :- XY341019
| Application Name :- MQM
| Component :- RetryConnectToSharedSubpool
| Build Date :- Nov 7 2000
| CMVC level :- p000-L001106
| Build Type :- IKAP - (Production)
| UserID :- 00000207 (mercator)
| Program Name :- launcher
| Process :- 00045966
| Thread :- 00000004
| Major Errorcode :- Unknown(20806206)
| Minor Errorcode :- OK
| Probe Type :- INCORROUT
| Probe Severity :- 2
| Probe Description :- AMQ6125: An internal MQSeries error has occurred.
|
MQM Function Stack
MQCONN
zstMQCONN
zstMQConnect
ConnectToSharedSubpool
RetryConnectToSharedSubpool
xcsFFST
--------} xusGetLineType rc=Unknown(2)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(2)
--------} xusGetLineType rc=Unknown(2)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
--------} xusGetLineType rc=Unknown(1)
IPCCMQSIniCallback rc=Unknown(9)
xstConnectSegmentViaFile rc=Unknown(6206)
3147be90 00000001 6C61756E 63686572 00000000 ....launcher....
3163b710 316390C8 00000000 6D657263 61746F72 1c.È....mercator
_________________
TJ
IBM Certified System Administrator Websphere MQ v5.3 |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Wed Jan 08, 2003 12:49 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
The FDC that you are getting is for the segment 8 problem. The tuning parameter that you want is the IPCCBaseAddress. You add it to the QueueManager stanza of the mqs.ini file:
QueueManager:
IPCCBaseAddress=11
Valid values are 4 to 12 except 6 and 7. I've had the best luck using 11. Another work-around is to have your code do a client connect rather than a bindings connect.
You can also move forward to WebSphere MQ 5.3 which makes use of AIX extended shared memory. If the IPCCBaseAddress doesn't work, there are some other things that you can do, but they aren't neat..... |
|
| Back to top |
|
|
| tjfunny1 |
| Posted: Wed Jan 08, 2003 1:56 pm Post subject: are you sure? |
|
|
Apprentice
Joined: 17 Jun 2002
Posts: 35
Location: Atlanta
|
I thought you added the IPCCBaseAddress=11 under the TuningParameters: stanza of the qm.ini file for each qmgr
There isn't any mq docs that address this issue or where to put it. I know we add the TuningParameter: stanza in the qm.ini files. I've put DefaultQBufferSize and added the TCP: stanza for KeepAlive.
Also, why would you require a server-based application use client connections instead of server connections (bindings)? It seems the client connect would take more overhead (use the TCP stack).
Thanks |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Jan 09, 2003 10:38 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
To be honest, I'm not sure where the IPCCBaseAddress parameter is documented. I'm sure that I read it somewhere, but I'm not sure where. It does go under the QueueManager stanza.
As far as the client working vs. the bindings not working, the reason is that the client doesn't use inter-process communication the same way that bindings does. The client uses tcp/ip to get to its queue manager agent. Bindings uses inter-process communication and is more sensitive to the segment 8 issue. |
|
| Back to top |
|
|
| tjfunny1 |
| Posted: Thu Jan 09, 2003 5:39 pm Post subject: Problem solved |
|
|
Apprentice
Joined: 17 Jun 2002
Posts: 35
Location: Atlanta
|
We added the IPCCBaseAddress=12 in the mqs.ini /var/mqm/mqs.ini
under the stanza for the Qmgr name.
We tried every possible value (starting at the low end, 4), and discovered the setting 12 would stop the FDC errors. The Mercator process, called a launcher, is part of their eventserver service. It does a heartbeat to a queue. For some reason, it doesn't create overhead (-8% cpu used), which is surprising to me.
I also added the TuningParameter stanza in the qmgr ini file, qm.ini, with the settings for
IPCCECSetSize=4000000
IPCCExtensionSize=128000
DefaultQBufferSize=2000000
After the IPCCBaseAddress=12 was set, the shutdown, restart of a qmgr was much clearer & quicker.
Thanks for the input and help |
|
| 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
|
|
|
|
