Author |
Message
|
manojsu |
Posted: Thu Dec 06, 2007 4:05 am Post subject: EXTSHM property for MQ |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Hi Guys,
WMQ is dumpin FDC files, an the log says me to set the EXTSHM=ON property,
but as per the mq doc.. it says for wmq v6, its makes not effect..
WebSphere MQ Version 5.3 recommended the use of the environment variable EXTSHM to allow 32-bit applications to connect to more than 10 WebSphere MQ memory segments at a time. With WebSphere MQ Version 6, the setting of the EXTSHM variable has no effect on the shared memory used by WebSphere MQ.
I am not a little confused, also apologies for my ignorance, wats this property, i meant wats a shared memory, and wat do i need to pre check on my aix machine before setting this property.
Thanks
Manoj |
|
Back to top |
|
 |
Gaya3 |
Posted: Thu Dec 06, 2007 4:15 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
|
Back to top |
|
 |
Vitor |
Posted: Thu Dec 06, 2007 4:37 am Post subject: Re: EXTSHM property for MQ |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
manojsu wrote: |
wats this property, i meant wats a shared memory, |
Ask your AIX admin - you'll need a diagram to fully grasp it.
manojsu wrote: |
wat do i need to pre check on my aix machine before setting this property.
|
Nothing - your admin should set it, having referred to the QB manual for AIX and the existing settings of the box. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
manojsu |
Posted: Thu Dec 06, 2007 4:42 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Hi,
Please find the same.. (2 sets)
| Vendor :- IBM |
| Probe Id :- XY129037 |
| Application Name :- MQM |
| Component :- xstConnectExtent |
| SCCS Info :- lib/cs/unix/amqxstex.c, 1.83 |
| Line Number :- 1829 |
| Build Date :- May 19 2005 |
| CMVC level :- p000-L050519 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000000 (root) |
| Program Name :- java |
| Addressing mode :- 32-bit |
| Process :- 680112 |
| Thread :- 518 |
| ConnId(4) App :- 0 |
| Major Errorcode :- xecX_E_SEGMENT_TABLE_FULL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6207 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6207: Failed to attach shared memory segment as |
| Segment table is Full. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 174 ae |
| Arith2 :- 24 18 |
| Comment1 :- Failed to attach shared memory segment: shmat(ShmId |
| 0x000000ae) [rc=-1 errno=24] The process file table is full. |
| Comment2 :- The process file table is full. |
| Probe Id :- XY129037 |
| Application Name :- MQM |
| Component :- xstConnectExtent |
| SCCS Info :- lib/cs/unix/amqxstex.c, 1.83 |
| Line Number :- 1829 |
| Build Date :- May 19 2005 |
| CMVC level :- p000-L050519 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000000 (root) |
| Program Name :- java |
| Addressing mode :- 32-bit |
| Process :- 680112 |
| Thread :- 519 |
| ConnId(4) App :- 0 |
| Major Errorcode :- xecX_E_SEGMENT_TABLE_FULL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6207 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6207: Failed to attach shared memory segment as |
| Segment table is Full. |
| FDCSequenceNumber :- 1 |
| Arith1 :- 174 ae |
| Arith2 :- 24 18 |
| Comment1 :- Failed to attach shared memory segment: shmat(ShmId |
| 0x000000ae) [rc=-1 errno=24] The process file table is full. |
| Comment2 :- The process file table is full. |
Thanks
Regards
Manoj |
|
Back to top |
|
 |
Gaya3 |
Posted: Thu Dec 06, 2007 4:46 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
|
Back to top |
|
 |
manojsu |
Posted: Thu Dec 06, 2007 7:06 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Seems that i need to upgrade my MQ to the latest fix pack as per the doc...
Thank you
Regards
Manoj |
|
Back to top |
|
 |
Gaya3 |
Posted: Thu Dec 06, 2007 7:10 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
What MQ 6 level that you are now
Good to apply latest fixpack...
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
manojsu |
Posted: Thu Dec 06, 2007 9:13 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
I am on base level version.. still... 6.0.0.0....
havin too many issues.. hopefully the fix pack installation should end my worries... |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri Dec 07, 2007 12:24 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
|
Back to top |
|
 |
manojsu |
Posted: Fri Dec 07, 2007 1:31 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Yup, have done this and downloaded the fixpack to upgrade from 6 to 6.0.2.1..
Thanks for the suggestion..
Regards
Manoj |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Dec 07, 2007 3:48 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
manojsu wrote: |
Yup, have done this and downloaded the fixpack to upgrade from 6 to 6.0.2.1..
Thanks for the suggestion..
Regards
Manoj |
You really should go to 6.0.2.2 lots of things fixed in 6.0.2.2. compared to 6.0.2.1  _________________ MQ & Broker admin |
|
Back to top |
|
 |
manojsu |
Posted: Fri Dec 07, 2007 6:15 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Would always safer to be one fix pack behind.. so suggest to be on lines for 6.0.2.1 |
|
Back to top |
|
 |
mvic |
Posted: Fri Dec 07, 2007 6:56 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
manojsu wrote: |
Would always safer to be one fix pack behind.. so suggest to be on lines for 6.0.2.1 |
Depends how you define "safe". Also IY99425 (the problem being experienced above) is fixed in 6.0.2.3 not 6.0.2.1. |
|
Back to top |
|
 |
manojsu |
Posted: Mon Dec 10, 2007 3:33 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Hi,
I have installed the fix pack, but still the FDC's are getting generated, and asl per the link, the solution is based out in fix pack 6.0.2.3 or do some modification before restarting the qmgr. (Setting the EXTSHM)...
now i need to wait for anothe downtime or fix pack release.,...
Regards
Manoj |
|
Back to top |
|
 |
manojsu |
Posted: Mon Jan 18, 2010 1:25 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Hi,
I have installed fixpack 3 on wmq 6.0.0.0 and set the env EXTSHM=ON before starting the queue managers, but we are still getting FDC's being generated.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Saturday January 16 21:59:44 GMT 2010 |
| Host Name :- beirut (AIX 5.3) |
| PIDS :- 5724H7201 |
| LVLS :- 6.0.2.1 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XY129037 |
| Application Name :- MQM |
| Component :- xstConnectExtent |
| SCCS Info :- lib/cs/unix/amqxstex.c, 1.83.1.7 |
| Line Number :- 1849 |
| Build Date :- Mar 7 2007 |
| CMVC level :- p600-201-070307 |
| Build Type :- IKAP - (Production) |
| UserID :- 00006001 (siebel) |
| Program Name :- siebmtshmw |
| Addressing mode :- 32-bit |
| Process :- 475412 |
| Thread :- 14 |
| QueueManager :- SEFFNG01 |
| ConnId(4) App :- 0 |
| Last HQC :- 1.0.0-23464 |
| Last HSHMEMB :- 1.1.0-2129528 |
| Major Errorcode :- xecX_E_SEGMENT_TABLE_FULL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6207 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6207: Failed to attach shared memory segment as |
| Segment table is Full. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 230 e6 |
| Arith2 :- 24 18 |
| Comment1 :- Failed to attach shared memory segment: shmat(ShmId |
| 0x000000e6) [rc=-1 errno=24] Too many open files |
| Comment2 :- Too many open files |
Any clue.. cos i thought the segmentation issues were solved in fixpack 3.
Regards
Manoj |
|
Back to top |
|
 |
|