| Author |
Message
|
| vmcgloin |
 Posted: Mon Jan 18, 2010 1:35 am Post subject: |
 |
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
| LVLS :- 6.0.2.1 |
I an pretty sure this line means that you actually have fixpack 1 for 6.0.2 not fixpack 3 installed which might explain why you are still seeing these FDC's. |
|
| Back to top |
|
 |
| manojsu |
| Posted: Mon Jan 18, 2010 1:49 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006
Posts: 147
Location: Bangalore
|
My Mistake.. The snapshot is before the upgrade
Put the wrong FDC snap shot..
WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Sunday January 17 22:17:27 GMT 2010 |
| Host Name :- beirut (AIX 5.3) |
| PIDS :- 5724H7201 |
| LVLS :- 6.0.2.3 |
| 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.9 |
| Line Number :- 1865 |
| Build Date :- Jan 23 2008 |
| CMVC level :- p600-203-080123 |
| Build Type :- IKAP - (Production) |
| UserID :- 00006001 (siebel) |
| Program Name :- siebmtshmw |
| Addressing mode :- 32-bit |
| Process :- 549254 |
| Thread :- 105 |
| QueueManager :- SEFFNG01 |
| ConnId(4) App :- 0 |
| Last HQC :- 1.0.0-30232 |
| Last HSHMEMB :- 1.1.0-2176928 |
| 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 :- 1049177 100259 |
| Arith2 :- 24 18 |
| Comment1 :- Failed to attach shared memory segment: shmat(ShmId |
| 0x00100259) [rc=-1 errno=24] Too many open files |
| Comment2 :- Too many open files | |
|
| Back to top |
|
|
| dutchman |
| Posted: Mon Jan 18, 2010 3:50 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Hi - on a previous post a reference was made to this website: http://www-01.ibm.com/support/docview.wss?uid=swg1IY99425 .
This shows that more is required above and beyond MQ V6.0.2.3 :
The following changes are required to accompany the application
of this APAR in order for MQ V6 to be able to exploit EXTSHM:
1. To ensure that hyper APAR IY66127 (for AIX5.2) or IY66147
(for AIX5.3) is present on the system;
2. To start the WMQ v6 queue managers with EXTSHM set.
Regards ... Ruud |
|
| Back to top |
|
|
| manojsu |
| Posted: Mon Jan 18, 2010 4:32 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006
Posts: 147
Location: Bangalore
|
The prereq have been taken care off...
instfix -ivk IY66147
IY66147 Abstract: 32-bit AIO applications fail with EXTSHM=ON
Fileset bos.mp:5.3.0.11 is applied on the system.
Fileset bos.mp64:5.3.0.11 is applied on the system.
All filesets for IY66147 were found.
And before starting the Queue Managers i did set the EXTSHM parameter. |
|
| Back to top |
|
|
| dutchman |
| Posted: Mon Jan 18, 2010 5:08 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
okidoki, just humor for a moment as we continue checking things... can u pls go to /var/mqm/errors where your FDC files are stored and issue the following unix command:
fgrep EXTSHM *
and paste results here. Hopefully the list of files being reported will include the FDC you mentioned earlier on.
Cheers ... Ruud |
|
| Back to top |
|
|
| manojsu |
| Posted: Mon Jan 18, 2010 5:15 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006
Posts: 147
Location: Bangalore
|
Did execute the command, there has been no output at all.
i have set the EXTSHM variable in the .profile file. |
|
| Back to top |
|
|
| dutchman |
| Posted: Mon Jan 18, 2010 5:27 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
Hmm ... interesting. I does suggest that you are not setting it. From my end I see:
/var/mqm/errors>fgrep EXTSHM *
AMQ1089764.0.FDC:EXTSHM=ON
AMQ1204268.0.FDC:EXTSHM=ON
AMQ1667090.0.FDC:EXTSHM=ON
AMQ835708.0.FDC:EXTSHM=ON
AMQ851968.0.FDC:EXTSHM=ON
AMQ974858.0.FDC:EXTSHM=ON
The good thing about the FDCs is that they tend to dump the value of the various environment variables at the time of the error. How are you setting this variable? ... from within the profile of the mqm account?
Regards ... Ruud |
|
| Back to top |
|
|
| manojsu |
| Posted: Mon Jan 18, 2010 5:40 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006
Posts: 147
Location: Bangalore
|
Yup, I am setting the variable in the profile.
export EXTSHM=ON
and after that in a new shell started the queue managers. |
|
| Back to top |
|
|
| dutchman |
| Posted: Mon Jan 18, 2010 5:43 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
yeah ... I've just noticed that the env var display is for an MQ V7.0.1 system; on my other systems which are MQ V5.3.x I can't see them in the FDCs eventough it is explicitly set - so looks like MQ V7.x is 'better' in terms of capturing certain types of data.
I'm out of ideas at the moment, so the next question is: when r u going to upgrade 
Ruud |
|
| Back to top |
|
|
| manojsu |
| Posted: Mon Jan 18, 2010 5:53 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006
Posts: 147
Location: Bangalore
|
i have upgraded from 6.0.2.1 to 6.0.2.3 yesterday. which has not solved the purpose of my upgrade..
are you speaking on the migration to v7.. not in the new future as of now |
|
| Back to top |
|
|
| dutchman |
| Posted: Mon Jan 18, 2010 6:05 am Post subject: |
|
|
Acolyte
Joined: 15 May 2001
Posts: 71
Location: Netherlands
|
|
| Back to top |
|
|
| mvic |
| Posted: Mon Jan 18, 2010 8:41 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| manojsu wrote: |
i have upgraded from 6.0.2.1 to 6.0.2.3 yesterday. which has not solved the purpose of my upgrade..
are you speaking on the migration to v7.. not in the new future as of now |
v6 FDCs do tend to contain a dump of the environment.
Do you have environment dumps at the end of your FDC records? They will probably contain mentions of SHELL= and PWD= and HOME= for example.
If you do have environment dumps yet EXTSHM is missing from them, then somehow and for some reason the setting was not effective. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jan 18, 2010 9:01 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| manojsu wrote: |
| i have upgraded from 6.0.2.1 to 6.0.2.3 yesterday. |
What do you have against 6.0.2.4, 6.0.2.5, 6.0.2.6, 6.0.2.7 and 6.0.2.8?They include hundreds of fixes to problems that are in 6.0.2.1 or 6.0.2.3. Apply 6.0.2.8 if you are applying a Fix Pack. Its been out for weeks and does not have any major problems.
You added that variable to the mqm profile. Are you sure the profile is being executed? How are you switching to the mqm ID when you want to start the QM?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| issac |
| Posted: Wed Apr 14, 2010 9:46 pm Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
so have you solved the problem? am i late?
I suppose you are not bothering with SH segments, rather the number of open files.
I suggest you change ULIMIT of your mqm account. Setting entry "nofiles" somewhere remarkably high, or unlimited.
Please come back to tell if it works.
| Comment1 :- Failed to attach shared memory segment: shmat(ShmId |
| 0x00100259) [rc=-1 errno=24] Too many open files |
| Comment2 :- Too many open files |
_________________
Bazinga! |
|
| Back to top |
|
|
| manojsu |
| Posted: Tue Aug 17, 2010 5:54 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006
Posts: 147
Location: Bangalore
|
Apologies for the delay in getting back, although we are still generating FDC's with the same reason.
we have set ulimited for all the procceses, threads, stack, file etc.
we are on fixpack 6.0.2.3 which should have fixed all the issues.. but hasnt.
any inputs of whether i am missing anything. |
|
| Back to top |
|
|
|
|
