| Author |
Message
|
| btjo |
 Posted: Wed Jul 07, 2004 10:14 am Post subject: AMQ8101 and '22 - Invalid argument' from semop |
 |
|
Novice
Joined: 07 Jul 2004
Posts: 19
|
i have gone through all the posts which have AMQ8101 error ( and or " Invalid argument from semop " error ). All of which is related to the kernel parameters on UNIX systems. this was confirmed by searching the IBM tech support site also. i modified the following params but i still get the same error ( AMQ8101: WebSphere MQ error (893) has occurred.) when i try to start the queue manager (strmqm FMCQM).
set shmsys:shminfo_shmmni=2048 (was 1024)
set shmsys:shminfo_shmseg=2048 (")
set semsys:seminfo_semume=512 (was 256)
set rlim_fd_cur=2048 (was 1024)
set rlim_rd_cur=2048 (was 1024)
set rlim_fd_max=32768
all of these were bumped from their previous values and the Sun box was restarted. queue manager used to be up and running prior to this error so it has worked before.
the FDC generated is shown below.
Environment : Sun OS 8, MQ 5.3 CSD 06.
anyone has any ideas.
| Code: |
/var/mqm/errors>more AMQ01162.0.FDC
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday July 07 11:43:37 CDT 2004 |
| Host Name :- appserv (SunOS 5.8) |
| PIDS :- 5724B4103 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- XY324192 |
| Application Name :- MQM |
| Component :- GetSubpoolsLock |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000886 (mqm) |
| Program Name :- setmqaut |
| Process :- 00001162 |
| Thread :- 00000001 |
| 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 - Invalid argument' from semop.) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 22 16 |
| Comment1 :- '22 - Invalid argument' from semop. |
| |
| |
+-----------------------------------------------------------------------------+
|
|
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Jul 07, 2004 11:09 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| btjo |
| Posted: Wed Jul 07, 2004 11:19 am Post subject: |
|
|
Novice
Joined: 07 Jul 2004
Posts: 19
|
Vennela: Thanks for the reply. Yes i had seen that thread as well.
from that thread
| Quote: |
The parameter is semume on HP-UX and it is
seminfo_semume on Solaris. When the customer changed semume from
10 (too low) to 256 (as recommended in both QB books).
|
i have this as :
set semsys:seminfo_semume=512 (was 256)
as this seemed to have fixed one guy's problem when i searched IBM tech support site with keyworde AMQ8101 and Invalid error from semop and some other combinations.
some guys fixed the issue with some other params that i mentioned earlier also. (lucky!).
Very weird problem. |
|
| Back to top |
|
|
| bbburson |
| Posted: Wed Jul 07, 2004 1:16 pm Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| Quote: |
| i still get the same error ( AMQ8101: WebSphere MQ error (893) has occurred.) when i try to start the queue manager (strmqm FMCQM). |
Is this on UNIX? If so, use ipcs and ipcrm to find and remove memory, semaphores, and queues used by mqm. |
|
| Back to top |
|
|
| btjo |
| Posted: Wed Jul 07, 2004 2:34 pm Post subject: |
|
|
Novice
Joined: 07 Jul 2004
Posts: 19
|
| bbburson wrote: |
| Quote: |
| i still get the same error ( AMQ8101: WebSphere MQ error (893) has occurred.) when i try to start the queue manager (strmqm FMCQM). |
Is this on UNIX? If so, use ipcs and ipcrm to find and remove memory, semaphores, and queues used by mqm. |
bbburson: Thanks for the reply. Yes the system is a solaris box. i used ipcs and ipcrm to remove the shared mem and semaphores which were used by mqm like you suggested.
tried strmqm FMCQM after that and the error is still there. It did not produce new error log or FDC though. |
|
| Back to top |
|
|
| kman |
| Posted: Wed Jul 07, 2004 6:22 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
How many queue managers do you have in your solaris system? Some of the kernel parameters is dependent on the number of queue managers on the system, so you might want to check that. The QB would mention that.
You said you still get the same error.. AMQ8101 but no new FDC. If the error is there, FDC must also be there. Maybe you are seeing and old one. Clear all your FDC and strmqm again. |
|
| Back to top |
|
|
| btjo |
| Posted: Wed Jul 07, 2004 8:11 pm Post subject: |
|
|
Novice
Joined: 07 Jul 2004
Posts: 19
|
| kman wrote: |
How many queue managers do you have in your solaris system? Some of the kernel parameters is dependent on the number of queue managers on the system, so you might want to check that. The QB would mention that.
You said you still get the same error.. AMQ8101 but no new FDC. If the error is there, FDC must also be there. Maybe you are seeing and old one. Clear all your FDC and strmqm again. |
@kman: Thanks for the reply. have 2 queue managers. i think all the relevant kernel parameters are set high enough to accomodate the two QM (thats what makes this weird).
is deleting any old FDC a critical step? (lame question, i wouldnt ask this if i were at the box and have the chance to try it myself).
thanks all. |
|
| Back to top |
|
|
| kman |
| Posted: Wed Jul 07, 2004 8:15 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
FDC is a diagnostic file. You can delete them.. and they will create new ones. If you don't delete them, they will stay there.
If you delete them... well you won't get confused .. that's all. |
|
| Back to top |
|
|
| btjo |
| Posted: Fri Jul 09, 2004 10:04 am Post subject: |
|
|
Novice
Joined: 07 Jul 2004
Posts: 19
|
| Backed out of CSD06 , rebooted. mqm commands started working again. reapplied CSD06. (had the whole mqm folder backed up before). everything is normal. |
|
| Back to top |
|
|
|
|
