| Author |
Message
|
| jhidalgo |
 Posted: Tue Jan 20, 2009 7:12 am Post subject: Subpool server has terminated while application connected |
 |
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
I am having
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon January 19 17:24:11 Central America Standard Time |
| Host Name :- xxxxxxxxx(Windows Server 2003, Build 3790: Service |
| Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.3 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XC371020 |
| Application Name :- MQM |
| Component :- xstServerRequest |
| SCCS Info :- lib/cs/pc/winnt/amqxstpn.c, 1.18.1.3 |
| Line Number :- 664 |
| Build Date :- Jan 23 2008 |
| CMVC level :- p600-203-080123 |
| Build Type :- IKAP - (Production) |
| UserID :- wsadmin |
| Process Name :- D:\WebSphere\AppServer\java\bin\java.exe |
| Addressing mode :- 32-bit |
| Process :- 00008824 |
| Thread :- 00000498 |
| QueueManager :- XXXXXX |
| 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 |
| (Subpool Server 1 pid[8300] has terminated while application connected.) |
| FDCSequenceNumber :- 0 |
| Arith2 :- 8300 206c |
| Comment1 :- Subpool Server 1 pid[8300] has terminated while |
| application con |
| |
+-----------------------------------------------------------------------------+
.................
...............
...........
-----{ xcsResetEventSem
-----} xcsResetEventSem rc=OK
-----{ xcsPostEventSem
-----} xcsPostEventSem rc=OK
----} zcpSendOnPipe rc=OK
----{ zcpReceiveOnPipe
-----{ xcsWaitEventSem
-----} xcsWaitEventSem rc=xecL_W_TIMEOUT
----} zcpReceiveOnPipe rc=zrcC_E_TIMEOUT
----{ ziiHealthCheck
-----{ xcsCheckHandle
-----} xcsCheckHandle rc=xecP_E_INVALID_PID
----} ziiHealthCheck rc=xecP_E_INVALID_PID
---} ziiVSendReceiveAgent rc=lrcE_CONNECTION_BROKEN
--} ziiMQPUT rc=xecP_E_INVALID_PID
--{ ziiBreakConnection
---{ zcpDetachPipe
|
Later on
| Code: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon January 19 17:24:11 Central America Standard Time |
| Host Name :- xxxxxxx(Windows Server 2003, Build 3790: Service |
| Pack 2) |
| PIDS :- 5724H7200 |
| LVLS :- 6.0.2.3 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XY205001 |
| Application Name :- MQM |
| Component :- xstConnectionRequest |
| SCCS Info :- lib/cs/pc/winnt/amqxstpn.c, 1.18.1.3 |
| Line Number :- 450 |
| Build Date :- Jan 23 2008 |
| CMVC level :- p600-203-080123 |
| Build Type :- IKAP - (Production) |
| UserID :- wsadmin |
| Process Name :- D:\WebSphere\AppServer\java\bin\java.exe |
| Addressing mode :- 32-bit |
| Process :- 00008824 |
| Thread :- 00000498 |
| QueueManager :- XXXXXX |
| 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 |
| (Failed to complete request to Shared Storage Server) |
| FDCSequenceNumber :- 1 |
| Comment1 :- Failed to complete request to Shared Storage Server |
| |
| |
+-----------------------------------------------------------------------------+
|
The application says it lost connection with MQ, any clue ??[/code] |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jan 20, 2009 7:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Mr Google, with reference to that probe id, suggests the box has run out of shared memory and this has had a devistating effect on the queue manager.
Naturally your first course of action should be to reboot. 
Failing that, follow some of Mr Google's other suggestions. Or port to Unix!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Tue Jan 20, 2009 7:26 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
Can you point me to the URL where it says it is a memory issue ?
I didn't find it, but it seems weird to have a memory problem because the server has 25GB of RAM and most of it is not being used. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 20, 2009 7:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jhidalgo wrote: |
| Can you point me to the URL where it says it is a memory issue ? |
There's this, plus also if you cast your eyes to the bottom of the 2nd FDC it's complaining that it's call to the Shared Memory Server didn't complete.
| jhidalgo wrote: |
| I didn't find it, but it seems weird to have a memory problem because the server has 25GB of RAM and most of it is not being used. |
Ah - I didn't say you were out of memory, I said you were out of shared memory. Different thing, different use. Similar (as I understand it) to the Unix shared memory/semaphore components.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Tue Jan 20, 2009 8:08 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jan 20, 2009 8:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Why do you think the memory error has anything to do with MQ?
The process involved is not an MQ process. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 20, 2009 8:21 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jhidalgo wrote: |
| since I don't tune the shared memory and memory is available, what else can be done !? |
- Tune the shared memory
- Upgrade to Unix
- Check the MSoft knowledge base
I agree with my most worthy associate that the FDC is a symptom, not a cause. WMQ has attempted to get shared memory, and this attempt has failed at an OS level, resulting in the queue manager problem.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 20, 2009 8:21 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Or viewed this way: is MQ the cause of this problem, or the victim?
_________________
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 |
|
|
| jhidalgo |
| Posted: Tue Jan 20, 2009 8:44 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
let me see if I am following,
the issue here is to determine if MQ and the application couldn't get connected and what I have to identify is what end failed ?, meaning that maybe the application got out of resources and then MQ started the connection process but couldn't complete it successfully ?
In that case I didn't receive the out of memory error but MQ couldn't allocate the connection ?
the other option is that MQ couldn't get the resources it needed to complete the connection, in this case the error should be different(like out of memory or something more appropiate right ???)
thanks |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 20, 2009 9:00 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Causes of MQRC_CONNECTION_BROKEN are many and varied.
The application gets the Reason for the MQI call that encountered the lost connection, regardless of the underlying cause. The FDC created helps you determine the underlying cause.
_________________
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 |
|
|
| jhidalgo |
| Posted: Tue Jan 20, 2009 9:03 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
| The FDC is the first thing I've posted but it didn't help on identifing the problem as you can see since nobody knows for sure, maybe you can light the path a little more ? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 20, 2009 9:10 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
|
| Back to top |
|
|
| jhidalgo |
| Posted: Tue Jan 20, 2009 9:24 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
| I dont see any relation to this issue..... |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jan 20, 2009 9:26 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I assume you already opened a PMR?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Tue Jan 20, 2009 9:36 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
|
| Back to top |
|
|
|
|
