Hi all !
I've problems with MQ 5.2 on Solaris 8
There is an application which sends messages with the MQ-Java-Client to our MQServer. This connection produces many errors and FDC-Files.
But I don't understand the entries in the LOG-Files.
The entries are : AMQ6118: An internal MQSeries error has occurred (0) and AMQ6184: An internal MQSeries error has occurred on queue manager XY.
If I make a "netstat -na | grep 1414" on our machine I can see, that the client tries to make a connetion. Then the connetion is ESTABLISHED and after a second or shorter the connection is gone. But ther are round about 15 connections in the status : TIME_WAIT. Nearly every second there is a new connetion in status TIME_WAIT and another one is gone.
How can this be ? Do anyone have an idea ?
The users of the application have no errors.
I think the Channelconnetion produces the FDC-Files but my colleague don't think so.
Here is a cliping from an FDC-File :
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Friday January 25 09:08:33 MET 2002 |
| Host Name :- myhost (SunOS 5. |
| PIDS :- 5765B75 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) |
| Vendor :- IBM |
| Probe Id :- ZL000028 |
| Application Name :- MQM |
| Component :- zlaMain |
| Build Date :- Nov 7 2000 |
| CMVC level :- p000-L001106 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000325 (root) |
| Program Name :- amqzlaa0_nd |
| Process :- 00026804 |
| Thread :- 00000001 |
| QueueManager :- XY |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal MQSeries error has occurred (0) |
| |
+-----------------------------------------------------------------------------+
Posted: Mon Jul 15, 2002 6:24 am Post subject: Same Problems
Newbie
Joined: 25 Oct 2001 Posts: 2
Hi we have same problems with the same FDC, but we are not useing Java.
Here the result from IBM:
ZL000028 zlaMain xecF_E_UNEXPECTED_RC
This isn't really a problem it happens when applications terminate before fully connecting to the agent. When cleanup process sees it, it throwes an FDC.
--> Customer should exactly check what their applications do in regards
to MQ? Do they perform an explicit MQDISC in the code?
------------------------------------------------------------------------
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