|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Error while connecting to MQ manager |
« View previous topic :: View next topic » |
Author |
Message
|
mreddington |
Posted: Mon Nov 27, 2006 8:17 am Post subject: Error while connecting to MQ manager |
|
|
Voyager
Joined: 14 Aug 2006 Posts: 78
|
Hi all,
An application is trying to connect (via MQ Client) to a queue manager.
The application folks, when trying to connect to a manager and put messages on a remote queue, seems like their application is running perfectly fine (because there are no AMQ errors returning in their code and their application behaves like as if it had put messages on the queue).
But when i check the queues for messages, they are not there at all ( CURDEPTH is 0)
I checked the log files in the /var/mqm/errors directory and this is what i found...
************************************************************
----- amqxfdcx.c : 713 --------------------------------------------------------
11/27/06 08:15:01
AMQ6118: An internal WebSphere MQ error has occurred (40806007)
EXPLANATION:
An error has been detected, and the MQ error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 673 --------------------------------------------------------
11/27/06 08:15:01
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 14918.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcx.c : 713 --------------------------------------------------------
************************************************************
And there are some FDC files in the error directory as well. What should i do now to resolve this issue? Please help me out. Thank you very much in advance... |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 27, 2006 8:26 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
You should look in the System Administraion manual (or online equivalent) which discusses the FDC files.
You'll find they contain a probe id; it's worth doing a search on the forum to see if it's cropped up before, also Google it.
If all else fails, follow the steps in the manual. Which will take you in short order to PMR Land. Seriously, there are some steps in there which are worth following just to make sure you've gone down the laundry list of usual suspects.
Or (radically) you can post the salient bits in here & see if anyone recognies it. It's happened before....
May good fortune lead to a swift resolution. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mreddington |
Posted: Mon Nov 27, 2006 8:31 am Post subject: Thank you |
|
|
Voyager
Joined: 14 Aug 2006 Posts: 78
|
Thank you for your advise... I will dig into it and if i find something resolvable or interesting i will post it here... |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 27, 2006 8:34 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
FDC files are nothing to be ashamed of - we've all had them. And hence there's a lot of material in here about them!!
In a good majority of cases the probe id is highly indicative. One of the cases where a search engine is more useful than a manual. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|