ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » MQ semop error for AIX

Post new topic  Reply to topic
 MQ semop error for AIX « View previous topic :: View next topic » 
Author Message
Shalini
PostPosted: Mon Mar 14, 2005 1:26 am    Post subject: MQ semop error for AIX Reply with quote

Master

Joined: 30 Apr 2002
Posts: 224
Location: India
Hi,

MQ 5.3 AIX: 5.1

I need your input for FDC generated for your valid input


I have received the FDC with probe Description of: - AMQ6119: An internal MQSeries error has occurred ('22

| - Invalid argument' from semop.)
| Application Name :- MQM |
| Component :- GetSubpoolsLock |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000204 (mqadm) |
| Program Name :- amqrmppa |
| Process :- 00052928 |
| Thread :- 00000008 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| ('22 - A system call received a parameter that is not val' from semop.) |

The IBM link for the same Probe ID gives the following info
(http://www-1.ibm.com/support/docview.wss?uid=swg21052056) with same FDC suggest that

Comment1:
A system call received a parameter that is not val from semop. The failure was caused by an ipcrm command. It appears someone did an ipcrm and removed The semaphore we are trying to lock when we have this failure.


But no one given the ipcrm command.

Still we are getting the same FDC in production and it resolves only when we restart QMGR.

Please let me know which OS/MQ parameter to tune....

Back to top
View user's profile Send private message Send e-mail
bower5932
PostPosted: Mon Mar 14, 2005 7:21 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
The link that you have posted is for a sempahore error against the user agent running MQ 5.1. Your FDC isn't against the agent. However, if you are running 5.1 code (and I doubt it based on amqrmppa), then you need to upgrade. If you are running 5.3 code, I'd like to see the entire top of the FDC (specifically the probe id but really all of it).
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
Shalini
PostPosted: Tue Mar 15, 2005 12:15 am    Post subject: Reply with quote

Master

Joined: 30 Apr 2002
Posts: 224
Location: India
Hi,

Please find the detailed FDC generated

+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sunday March 13 21:29:33 SAUST 2005 |
| Host Name :- JunkServer (AIX 5.1) |
| PIDS :- 5724B4101 |
| LVLS :- 530 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XY324192 |
| Application Name :- MQM |
| Component :- GetSubpoolsLock |
| Build Date :- Oct 12 2002 |
| CMVC level :- p000-L021011 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000007 (mqadm) |
| Program Name :- amqrmppa |
| Process :- 00050146 |
| Thread :- 00000018 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| ('22 - A system call received a parameter that is not val' from semop.) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 22 16 |
| Comment1 :- '22 - A system call received a parameter that is not |
| val' from |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
ccxResponder
rrxResponder
rriAcceptSess
lpiSPIMQConnect
zstMQConnect
zstInitCS
xcsInitialize
xcsFFST

MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xcsInitialize
-{ xcsRequestThreadMutexSem
-} xcsRequestThreadMutexSem rc=OK
-{ xcsStartPersistentTimerThread
-} xcsStartPersistentTimerThread rc=OK
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
} xcsInitialize rc=OK
{ cccGetMem
-{ xcsGetMem
-} xcsGetMem rc=OK
} cccGetMem rc=OK
{ cccCSRegister
-{ xcsRegComp
-} xcsRegComp rc=OK
} cccCSRegister rc=OK
{ xcsRequestThreadMutexSem
} xcsRequestThreadMutexSem rc=OK
{ xcsReleaseThreadMutexSem
} xcsReleaseThreadMutexSem rc=OK
{ ccxResponder
-{ ccxNetWorkInit
--{ ccxParseIni
--} ccxParseIni rc=OK
--{ cciLoadLibrary
---{ cccGetMem
----{ xcsGetMem
----} xcsGetMem rc=OK
---} cccGetMem rc=OK
---{ xcsLoadFunction
----{ xcsQueryValueForSubpool
----} xcsQueryValueForSubpool rc=OK
---} xcsLoadFunction rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
---{ xcsQueryProcAddr
---} xcsQueryProcAddr rc=OK
--} cciLoadLibrary rc=OK
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} ccxNetWorkInit rc=OK
-{ ccxAcceptConv
--{ cciTcpAcceptConv
---{ ioctl
---} ioctl rc=OK
--} cciTcpAcceptConv rc=OK
-} ccxAcceptConv rc=OK
-{ rrxResponder
--{ cccGetConfig
--} cccGetConfig rc=OK
--{ rriAcceptSess
---{ cccGetMem
----{ xcsGetMem
----} xcsGetMem rc=OK
---} cccGetMem rc=OK
---{ ccxSetTimeOut
---} ccxSetTimeOut rc=OK
---{ ccxReceive
----{ cciTcpReceive
-----{ ccxAllocMem
------{ cccGetMem
-------{ xcsGetMem
-------} xcsGetMem rc=OK
------} cccGetMem rc=OK
-----} ccxAllocMem rc=OK
-----{ recv
-----} recv rc=Unknown(84)
----} cciTcpReceive rc=OK
---} ccxReceive rc=OK
---{ lpiSPIMQConnect
----{ xcsInitialize
----} xcsInitialize rc=OK
----{ zstMQConnect
-----{ zutBlankPad
-----} zutBlankPad rc=OK
-----{ zutLockLocalThreads
-----} zutLockLocalThreads rc=OK
-----{ zutIsItBlank
-----} zutIsItBlank rc=OK
-----{ zutCheckQMName
------{ zutCheckValidName
------} zutCheckValidName rc=OK
-----} zutCheckQMName rc=OK
-----{ zutCvtMQName2Str
-----} zutCvtMQName2Str rc=OK
-----{ zstGetPCDbyTID
-----} zstGetPCDbyTID rc=OK
-----{ zstInitCS
------{ xcsInitialize
-------{ xcsRequestThreadMutexSem
-------} xcsRequestThreadMutexSem rc=OK
-------{ xcsBuildDumpPtr
--------{ xcsGetMem
--------} xcsGetMem rc=OK
-------} xcsBuildDumpPtr rc=OK
-------{ xcsStrerror
-------} xcsStrerror rc=OK
-------{ xcsFFST

Please suggest/comment

Back to top
View user's profile Send private message Send e-mail
fschofer
PostPosted: Tue Mar 15, 2005 2:19 am    Post subject: Reply with quote

Knight

Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
Hi,
are you running MQ without any fixes / CSDs ?
=>
Code:
  | LVLS :- 530 |


The first thing i would do is installing one of the latest CSDs
=>
http://www-306.ibm.com/software/integration/mqfamily/support/summary/

Greetings
Frank
Back to top
View user's profile Send private message Send e-mail
Shalini
PostPosted: Tue Mar 15, 2005 7:02 am    Post subject: Reply with quote

Master

Joined: 30 Apr 2002
Posts: 224
Location: India
Hi,

Thanks for Reply.

Hpw do really prove that the CSD 9 will resolve my issue....

The FDC Comment:
"Comment1 :- '22 - A system call received a parameter that is not |
| val' from | "

search in both IBM and Google does not clue me the same....

Please suggest...

Back to top
View user's profile Send private message Send e-mail
fschofer
PostPosted: Tue Mar 15, 2005 8:17 am    Post subject: Reply with quote

Knight

Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
Hi,
no prove at all, but since the initial release in 2002 about 500 or more problems were fixed.
=>
http://www-306.ibm.com/software/integration/mqfamily/support/memos/aix/memo.txt

Greetings
Frank
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » MQ semop error for AIX
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.