| Author |
Message
|
| srikanthc60 |
 Posted: Wed Dec 09, 2015 6:56 am Post subject: one FDC is getting generated each minute with XY324103 |
 |
|
Voyager
Joined: 21 Jul 2013
Posts: 79
|
Hi all,
could someone help us to identify and resolve the issue.
We have MQ 7.0.1.12 running on HACMP active -active servers with total of 22 qmgrs (13 qmgrs on one node - 9 qmgrs on another node). We are not sure which queue manager is causing the issue.
On one node, an FDC is getting generated with Probe Id :- XY324103 each minute. Below are some more details.
Probe Id :- XY324103
Component :- xstGetSubpoolsLock
Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred
('22 - Invalid argument' from semop.)
Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC
Minor Errorcode :- OK
Comment1 :- '22 - Invalid argument' from semop.
Below link explains the similar situation but not the exact one which we are facing.
http://www-01.ibm.com/support/docview.wss?uid=swg1IV47710
we are thinking the possible solution might be restart of the queue managers and clear the IPC resources (semaphores / shared memory) for the qmgr.
But in the other IBM tech note says, it is not recommended process to clean IPC.
[url]
http://www-01.ibm.com/support/docview.wss?uid=swg21414283 [/url]
Thanks in advance!! |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Dec 09, 2015 7:02 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Did you open a PMR with IBM support?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Dec 09, 2015 7:42 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| bruce2359 wrote: |
| Did you open a PMR with IBM support? |
IBM would most likely not want to know. Apparently the system is running MQ 7.0.1.12
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 09, 2015 7:50 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| smdavies99 wrote: |
| bruce2359 wrote: |
| Did you open a PMR with IBM support? |
IBM would most likely not want to know. Apparently the system is running MQ 7.0.1.12 |
IBM would want to provide service to all its customers. It's possible there is an APAR fix or circumvention. It's also possible that the customer has an extended support agreement.
It costs the OP nothing to contact IBM support for this.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| srikanthc60 |
| Posted: Wed Dec 09, 2015 8:53 am Post subject: |
|
|
Voyager
Joined: 21 Jul 2013
Posts: 79
|
Yes!! we did opened a PMR.. Obvious answer from support team was MQ version we are running on is out of support and we need Service Extension agreement for support!!
Can some one help me on this issue  |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 09, 2015 9:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| srikanthc60 wrote: |
| Can some one help me on this issue |
You can (in decreasing order of merit):
- upgrade to a supported version and raise a PMR if the problem persists (you should be thinking about upgrading anyway, just accelerate the process)
- buy the Extended Support and re-raise the PMR
- set up a cron job to remove the FDC files before they fill the file system
- cross your fingers and clean the IPC
Note that all of the advice here comes from a group of random anonymous strangers on the Internet who refuse accountability. So make the decision you can support and defend when challenged.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 09, 2015 9:17 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And make sure that all your applications using MQ Resources also use MQOO and MQGMO FAIL_IF_QUIESCE...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 09, 2015 9:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You should also review the installation parts of the MQ documentation for the version you're running.
For your OS there should be a section describing OS resource limits. You may need to change these for the number of queue managers you have.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| srikanthc60 |
| Posted: Wed Dec 09, 2015 9:50 am Post subject: |
|
|
Voyager
Joined: 21 Jul 2013
Posts: 79
|
| Thank you all for pitching in!! Will propose the client about upgrading the product |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 09, 2015 10:07 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Go with Jeff's suggestion above. Check first for sufficient o/s resources.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
