| Author |
Message
|
| julianm |
 Posted: Fri Jun 06, 2008 7:16 pm Post subject: .Net application generating MQ runtime error |
 |
|
Newbie
Joined: 05 Jun 2008
Posts: 3
|
Hi,
Please redirect if I'm in the incorrect forum. I have a dotNet application using the amqmdnet.dll interface DLL to read and write messages from a queue. The version of the DLL that I am using is 1.0.0.3 and the MQ version is 530.7 CSD07. {I have noticed that in the CSD11 patch that the amqmdnet.dll has increased in size but is still the same version. I'm currently using that newer version DLL in a test system to see if the situation improves}
I have and extract from the FDC dump below.
The impact my program gets is neglegible. However, over a period of time we have seen an impact with MQ to the level where the server needs to be bounced to get everthing functioning correctly again. We are running around 800 servers all over Australia processing real time information of a volume of several milliion messages per day so the impact of this problem would be widespread. Existing applications are not experiencing similar problems.
Does anyone have any advice on what might be causing this problem and what we could try to address it? We are not able to replicate the problem, it occurs intermittently.
Thanks in advance
Julian
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri June 06 11:34:12 AUS Eastern Standard Time 2008 |
| Host Name :- SV0667NA001 (Windows Ver 5.2 Build 3790: ) |
| PIDS :- 5724B4100 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZL075030 |
| Application Name :- MQM |
| Component :- zlaReuseConnection |
| Build Date :- May 28 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- c:\Program Files\MQSeries\bin\amqzlaa0.exe |
| Process :- 00003820 |
| Thread :- 00002028 |
| QueueManager :- MQPWST0667 |
| Major Errorcode :- STOP |
| Minor Errorcode :- OK |
| Probe Type :- HALT6109 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
|
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Jun 07, 2008 7:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Let's have a look at this.
a) MQ V5.xx is out of support 
b) MQ V6.0.2.4 has a lot better .NET libraries.
You really should not be moving to CSD11 (IIRC CSD14 is the latest ... still out of support ) but upgrading to V6 or even V7! I hear it is out...
In any case the client installation and the .NET MQ component are a matched pair. You should never have them at a different level/CSD
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| julianm |
| Posted: Sun Jun 08, 2008 2:31 am Post subject: |
|
|
Newbie
Joined: 05 Jun 2008
Posts: 3
|
Hi.
Thanks for your reply.
Yes I know that MQ V5.xx is out of support. I'm also aware that CSD14 is the latest patch but unfortunatly I have to work within the constraints that I have currently. Its scheduled but not imminent.
I noted that problems seemed more frequent in the test system when I combined the CSD11 amqmdnet.dll with the remaining infrastructure being CSD07 but the problem was actually the same as detailed above in the post. Might just have been a concidence.
I'm really looking for what might be casusing this problem so I can attack the possible program issues.
Any idea's on that one? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Jun 08, 2008 4:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The problem is exactly and specifically that you are using CSD7 of MQ v5.3.
The only way to solve this is to move to a later CSD, or a supported version of MQ, imminently.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| julianm |
| Posted: Sun Jun 08, 2008 5:19 am Post subject: |
|
|
Newbie
Joined: 05 Jun 2008
Posts: 3
|
Hi,
It seems a bit strange that this is purely linked to the patch version of MQ because we have several other applications that are not creating this problem with CSD07. It only appears to be this one application and we have around 800 servers nationally messaging in both directions with message counts in the several millions per day.
I would like to understand what the FDC dump is telling me and if its able to be addressed programatically as any patch is not an option at this stage. |
|
| Back to top |
|
|
|
|
