| Author |
Message
|
| MQ_Lover |
 Posted: Wed Dec 04, 2013 4:42 am Post subject: FDC files |
 |
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi All,
Seeing lot of FDC files generating with resource issues, it is a new MQ install with MQ 7.5.0.1 strange bit it it has 16 GB RAM and used currently is 6 GB only. As this is evergreen project the old equivalent server has MQ 7.0.1.6 and no issues seen at all same app tests there same way though its a bad bad app not doing a clean close of MQ channel but still the issue is not seen there and seen only on the new server. Please see below the FDC file details any help appreciated as not much details available on this. It's Window Server 2008.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon December 02 2013 20:18:06 GMT Standard Time |
| UTC Time :- 1386015486.723000 |
| UTC Time Offset :- 0 (GMT Standard Time) |
| Host Name :- GBW07534 |
| Operating System :- Windows Server 2008 R2 Server Enterprise Edition, |
| Build 7601: SP1 |
| PIDS :- 5724H7220 |
| LVLS :- 7.5.0.1 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Installation Path :- C:\Program Files (x86)\IBM\WebSphere MQ |
| Installation Name :- Installation1 (1) |
| Probe Id :- XC035007 |
| Application Name :- MQM |
| Component :- xcsCreateThread |
| SCCS Info :- F:\build\slot1\p750_P\src\lib\cs\amqxeida.c, |
| Line Number :- 5071 |
| Build Date :- Mar 8 2013 |
| Build Level :- p750-001-130308 |
| Build Type :- IKAP - (Production) |
| UserID :- hbeu-svc-ohtp-sys |
| Process Name :- D:\Program Files\CADIS Software\CADIS\CADIS.Servic |
| e.Host.exe |
| Addressing mode :- 32-bit |
| Process :- 00045132 |
| Thread :- 00022351 |
| UserApp :- TRUE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- xecP_E_NO_RESOURCE |
| Minor Errorcode :- OK |
| Probe Type :- INCORROUT |
| Probe Severity :- 2 |
| Probe Description :- AMQ6090: MQM could not display the text for error |
| 536895781. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 12 c |
| Comment1 :- Not enough space |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Dec 04, 2013 5:23 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Google the Probe Id...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Wed Dec 04, 2013 7:25 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi Exerk,
I did and doesn't seems to be much of help as it says as below
http://www-01.ibm.com/support/docview.wss?uid=swg21196094
| Quote: |
Resolving the problem
Make corrections to your security exit so that it does not leak system resources like handles and memory. |
- I have not enabled any security exits at all, not sure if there could be another reason for this error still |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 04, 2013 7:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQ_Lover wrote: |
| not sure if there could be another reason for this error still |
Not sure? Well there might be this (from the link you posted):
| Quote: |
| The FDCs indicate a shortage of system resources |
Is there such a shortage?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 04, 2013 7:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| The Process Name of the FDC header is interesting. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Dec 04, 2013 7:40 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| MQ_Lover wrote: |
Hi Exerk,
I did and doesn't seems to be much of help as it says as below |
Funny, because I Googled "probe id XC035007" and got THIS. I'm not saying that's the cause but you never know...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Wed Dec 04, 2013 8:20 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi Vitor - Thanks for the reply, could be as the FDC also indicates that but I am unable to locate which system resource it shouting about I checked the RAM which was at 6 GB consumption though it has 12GB still free and available, one thing which is pretty common with this server is the CPU utilization keeps touching 100% every now and then and when I raised a voice against this I have been told this is common for this app and same happens on old servers also and to my surprise I did see that it was almost 100% every now and then and no such error reported there, so we know definitely there is some system resource MQ is compaining but which one how could we find out for sure?
Hi Exerk - Thanks for the reply, I checked that and the channel already had SHARECNV(0) - as I created it from the existing backup of old server I believe it already had that so seems this was known before as by default the value is 10, not sure why still it's complaining. |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Wed Dec 04, 2013 8:22 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi mqjeff - what's interesting in the process name  have you come across this app before also? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 04, 2013 8:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| MQ_Lover wrote: |
| Hi mqjeff - what's interesting in the process name have you come across this app before also? |
What's interesting is that it's not a process that's shipped with MQ. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 04, 2013 11:24 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
UserID :- hbeu-svc-ohtp-sys |
| Process Name :- D:\Program Files\CADIS Software\CADIS\CADIS.Servic |
| e.Host.exe | |
What's interesting is that this application is installed and running in your system, and you seem to know nothing about it.
_________________
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 |
|
|
| wmbwmq |
| Posted: Thu Dec 05, 2013 2:01 pm Post subject: |
|
|
Acolyte
Joined: 18 Jul 2011
Posts: 66
|
mqjeff brought up a very good point. I don't remember seeing a non-mqm process name in FDC. Does anyone know if this is normal?
Or does AMQ6090 ( could not display the text for error) has something to do with this? |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Dec 05, 2013 2:32 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
| Process Name :- D:\Program Files\CADIS Software\CADIS\CADIS.Servic |
| e.Host.exe |
| Major Errorcode :- xecP_E_NO_RESOURCE |
| Probe Description :- AMQ6090: MQM could not display the text for error | |
I suspect there is something wrong with the CADIS app process environment. It is not even able to display an MQ error message!
_________________
Glenn |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Fri Dec 06, 2013 3:15 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi Exerk - Problem resolved, it was the SHARECNV parameter which was 10 only and by the time I checked as many were working on the issue someone applied the change as per the old environment and it was 0 there also, this was an interesting issue, but looks to be solved for now and no more FDC files, thanks for your help.
All - Thanks for your help on this basically this app CADIS is crap and legacy and no one wants to touch it and hence all boils down to MQ to make it cope with such bad application as it is supposed to be same way till now, as of now I have enabled the DISCINT on the serverconn channel also as seems this is not closing the connection at all and within 3 hrs it reached 5000 instances of channel, really a bad bad app.
But, once again thanks all for the help. |
|
| Back to top |
|
|
|
|
