Author |
Message
|
lehare |
Posted: Tue Jun 24, 2008 3:44 am Post subject: AMQ6119: Failed to complete request to Shared Storage Server |
|
|
 Apprentice
Joined: 25 Jul 2005 Posts: 48
|
Hi Guys,
I'm running windows 2003 Ent. with Websphere MQ 5.3 CSD14 - i get the below error in the FDC and AMQErrorxx.log
the machine is running in a VMware server and ALL storage is on a SAN storage machine.
the Qmgr is configured to write its activity log is writing to one of the SAN partition!
as soon as i get the error - the box becomes NON responsive - the queue manager is reported as "unavailable" -
the only way to 'temporarily resolve' the error is to RESTART the server - now this is happening EVERY day - and my boss is getting mad
please assist.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri June 20 16:45:24 South Africa Standard Time 2008 |
| Host Name :- VCIBJNBSBLHUV2 (Windows Ver 5.2 Build 3790: Service |
| Pack 1) |
| PIDS :- 5724B4100 |
| LVLS :- 530.14 CSD14 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XY205001 |
| Application Name :- MQM |
| Component :- xstConnectionRequest |
| Build Date :- Dec 15 2007 |
| CMVC level :- p530-14-L071214 |
| Build Type :- IKAP - (Production) |
| UserID :- usb_fot |
| Process Name :- K:\uddsbyn7\logicalhosts\lhUatBatHKM\jre\bin\java. |
| exe |
| Process :- 00005668 |
| Thread :- 00000091 |
| QueueManager :- tsblhv7_qmgr |
| 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 |
| |
| |
+-----------------------------------------------------------------------------+
bit of the FDC tracing
-----{ xcsFreeMem
-----} xcsFreeMem rc=OK
-----{ xcsBuildDumpPtr
------{ xcsFreeMem
------} xcsFreeMem rc=OK
-----} xcsBuildDumpPtr rc=OK
----} xcsFFST rc=OK
---} xstServerRequest rc=xecF_E_UNEXPECTED_SYSTEM_RC
---{ xcsFFST
regards
lehare. |
|
Back to top |
|
 |
dp111443 |
Posted: Tue Jul 05, 2016 11:39 pm Post subject: |
|
|
Voyager
Joined: 25 Feb 2004 Posts: 82
|
Hi,
We are getting the same problem - did you get to the root cause of this?
Thanks, _________________ Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
Back to top |
|
 |
exerk |
Posted: Wed Jul 06, 2016 12:01 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
dp111443 wrote: |
We are getting the same problem - did you get to the root cause of this? |
Bear in mind that you're asking about an 8-year old post, which states a very old and unsupported OS and MQ version, so the Original Poster's solution would most likely be invalid for your set up - unless of course you also are on an unsupported OS and MQ version? _________________ 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 |
|
 |
dp111443 |
Posted: Wed Jul 06, 2016 12:03 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004 Posts: 82
|
Hi Exert,
Yes indeed - it's an environment that we have that we are looking to decommission but it's directly related to the same version as this. Windows 2003 with MQ v6.
I'm not expecting a response from the original poster but it's worth a try!  _________________ Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
Back to top |
|
 |
exerk |
Posted: Wed Jul 06, 2016 12:06 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
dp111443 wrote: |
Windows 2003 with MQ v6. |
Is MQ at the latest FixPack? _________________ 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 |
|
 |
dp111443 |
Posted: Wed Jul 06, 2016 1:20 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004 Posts: 82
|
Hi,
No we're not. We are on 6.0.2.6.
We have different environments (i.e. dev, 2xtest, production).
Dev and production are fine, but one of the test environments seem to suffer from this so it tells me it's local or environmental causing the issue rather than code/fixpack related. _________________ Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
Back to top |
|
 |
exerk |
Posted: Wed Jul 06, 2016 2:16 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Time to get a Windows Sys Admin to do a compare-and-contrast with a 'working' system methinks  _________________ 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 |
|
 |
fjb_saper |
Posted: Wed Jul 06, 2016 8:05 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
exerk wrote: |
Time to get a Windows Sys Admin to do a compare-and-contrast with a 'working' system methinks  |
Also time to get a network engineer involved to make sure there are no problems with the network card, protocols, etc ... for the connection to the SAN...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|