MQSeries.net :: View topic

DeanR · Posted: Fri Mar 17, 2006 7:33 am Post subject:

Hi all,

We're using a .NET client app to post messages to an MQSeries (Version: 5.3) queue using the amqmdnet.dll library.

We're occassionally getting the following errors in the client event log when we attempt a Put:

Event Log Entry 1
"An internal WebSphere MQ error has occurred.

An error has been detected, and the MQ error recording routine has been called.

Details of the error have been stored at C:\Program Files\IBM\WebSphere MQ\errors\AMQ02328.19.FDC. A synopsis is given in the data section below. 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."
Wed March 08 12:05:40 GMT Standard Time 2006 ,
Host Name :- TEST0020 (Windows XP Build 2600: Service Pack 1),
PIDS:- 5724B4100 ,
LVLS :- 530.9 CSD09,
Product Long Name :- WebSphere MQ for Windows,
Vendor :- IBM,
Probe Id :- XC381010,
Application Name :- MQM ,
Component :- xcsDisplayMessageForSubpool,
Build Date :- Dec 13 2004,
CMVC level :- p530-09-L041213,
Build Type :- IKAP - (Production),
UserID :- TESTUSER20,
Process Name :- SystemTray.exe,
Process :28,
Thread :- 8,
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 (WinNT error 5 from DosOpen.),
FDCSequenceNumber :- 1,
Comment1 :- WinNT error 5 from DosOpen.
Comment2 :- Access is denied.
Component Dumps (Thread 00000008),-------------------------------------,

Event Log Entry 2
"Allocate failed to host '31.130.192.175'.

The attempt to allocate a conversation using TCP/IP to host <<ip address removed>> was not successful.

The error may be due to an incorrect entry in the TCP/IP parameters contained in the channel definition to host <<ip address removed>>. Correct the error and try again. If the error persists, record the error values and contact your systems administrator. The return code from the TCP/IP (connect) call was 10065 (X'2751'). It may be possible that the listening program at host <<ip address removed>> is not running. If this is the case, perform the relevant operations to start the listening program for protocol TCP/IP and try again."

Now I (think) can explain these errors with sporadic network connectivity because subsequent message submissions appear to work. But the real problem is that we're losing the message that we're trying to post when these errors do occur. Unfortunately the calling .NET code never get's an exception, and so believes the .Put() has succeeded and removes the message from the Source queue.

Is it possible that the amqmdnet.dll API is "swallowing" errors and thus never reporting it back to the client?

Further compounding the debugging of this problem is the location where the AMQ02328.19.FDC file is written to is empty?! It seems to be cleared every time the machine re-boots?

I'd appreciate any help you can offer, becuase the Business aren't happy with "dissapearing messages"

Thanks,
Dean