| Author |
Message
|
| blovell |
 Posted: Mon Oct 18, 2010 6:22 am Post subject: AMQ9504 |
 |
|
Acolyte
Joined: 08 Feb 2006
Posts: 63
Location: Alpharetta, GA
|
We have a JAVA Application that is pushing files to our main QMGR. On rare occasions we get a AMQ9504.
Starting today I am now getting this event every second. Below is the FDC contents of the problem.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon October 18 2010 10:06:15 EDT |
| UTC Time :- 1287410775.617373 |
| UTC Time Offset :- -240 (EST) |
| Host Name :- MQPROD |
| Operating System :- Linux 2.6.9-67.ELsmp |
| PIDS :- 5724H7224 |
| LVLS :- 7.0.0.1 |
| Product Long Name :- WebSphere MQ for Linux (x86 platform) |
| Vendor :- IBM |
| Probe Id :- RM680003 |
| Application Name :- MQM |
| Component :- rriBadDataReceived |
| SCCS Info :- base/src/cmqxrmcv.c, 1.82 |
| Line Number :- 1991 |
| Build Date :- Dec 19 2008 |
| CMVC level :- p700-001-081219 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000500 (mqm) |
| Program Name :- amqrmppa |
| Addressing mode :- 32-bit |
| Process :- 7857 |
| Process(Thread) :- 20168 |
| Thread :- 118444 |
| ThreadingModel :- PosixThreads |
| QueueManager :- ELSFTS01 |
| ConnId(1) IPCC :- 7031334 |
| ConnId(3) QM-P :- 119340 |
| Last HQC :- 3.0.0-42312 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- rrcE_PROTOCOL_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9504 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9504: A protocol error was detected for channel |
| 'SVRCONN.MFT.ADMIN'. |
| FDCSequenceNumber :- 4592 |
| Arith1 :- 32244 7df4 |
| Arith2 :- 32218 7dda |
| Comment1 :- SVRCONN.MFT.ADMIN |
| |
+-----------------------------------------------------------------------------+
_________________
Bradley M. Lovell |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Oct 18, 2010 6:28 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Mr. Google found THIS...
...especially as you are way back-level.
_________________
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.
Last edited by exerk on Mon Oct 18, 2010 7:42 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Oct 18, 2010 7:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If it is occurring every second on the second, exactly, and your application itself is not throwing an error or reporting any issues, then it is likely that some well-meaning but misinformed person has put in a process to try and ensure the MQ server is running by telnetting to the Listener port or ICMP pinging the channel.
Perhaps BigIP is trying this. |
|
| Back to top |
|
|
| blovell |
| Posted: Mon Oct 18, 2010 8:51 am Post subject: Particular File |
|
|
Acolyte
Joined: 08 Feb 2006
Posts: 63
Location: Alpharetta, GA
|
It appears this error is tied to a paritcular file. This file is somewhat larger than the others. After removing this file from our application Put queue, the smaller ones were able to drain.
After reading the above post, I am going to try and deploy refresh pack 7.0.1.3, hopefully this helps.
_________________
Bradley M. Lovell |
|
| Back to top |
|
|
| blovell |
| Posted: Mon Oct 18, 2010 10:12 am Post subject: Still experiencing 9504 event |
|
|
Acolyte
Joined: 08 Feb 2006
Posts: 63
Location: Alpharetta, GA
|
The sending JMS application is receiving a 2019, and the server is reporting the 9504. Upgrade to 7.0.1.3 doesn't appear to have done anything.
The problem appears to be something with the socket timeout value. TCPDUMPs aren't showing anything out of the ordinary. I manipulated the HBINT to 600, to no avail.
Is it possible the Java code on the client simply isn't closing the queue properly after teh put
_________________
Bradley M. Lovell |
|
| Back to top |
|
|
| blovell |
| Posted: Mon Oct 18, 2010 10:26 am Post subject: Latest FDC content |
|
|
Acolyte
Joined: 08 Feb 2006
Posts: 63
Location: Alpharetta, GA
|
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon October 18 2010 13:25:10 EST |
| UTC Time :- 1287426310.704542 |
| UTC Time Offset :- -300 (EST) |
| Host Name :- MQPREPRO |
| Operating System :- Linux 2.6.9-67.ELsmp |
| PIDS :- 5724H7224 |
| LVLS :- 7.0.1.3 |
| Product Long Name :- WebSphere MQ for Linux (x86 platform) |
| Vendor :- IBM |
| Probe Id :- RM680003 |
| Application Name :- MQM |
| Component :- rriBadDataReceived |
| SCCS Info :- base/src/cmqxrmcv.c, 1.79.3.3 |
| Line Number :- 2081 |
| Build Date :- Aug 12 2010 |
| CMVC level :- p701-103-100813 |
| Build Type :- IKAP - (Production) |
| Effective UserID :- 500 (mqm) |
| Real UserID :- 500 (mqm) |
| Program Name :- amqrmppa |
| Addressing mode :- 32-bit |
| Process :- 4464 |
| Process(Thread) :- 13541 |
| Thread :- 139 |
| ThreadingModel :- PosixThreads |
| QueueManager :- ELSTEST01 |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 1034 |
| ConnId(3) QM-P :- 191 |
| Last HQC :- 3.0.0-46888 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- rrcE_PROTOCOL_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9504 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9504: A protocol error was detected for channel |
| 'SVRCONN.MFT.ADMIN'. |
| FDCSequenceNumber :- 119 |
| Arith1 :- 32244 (0x7df4) |
| Arith2 :- 32218 (0x7dda) |
| Comment1 :- SVRCONN.MFT.ADMIN |
| |
+-----------------------------------------------------------------------------+
_________________
Bradley M. Lovell |
|
| Back to top |
|
|
| blovell |
| Posted: Thu Oct 28, 2010 10:05 am Post subject: CLNTCONN .JAR Update |
|
|
Acolyte
Joined: 08 Feb 2006
Posts: 63
Location: Alpharetta, GA
|
The .JAR files being used on the client were 6.0.x.x. The problem was resolved by updating all .jar classes on the client machine.
_________________
Bradley M. Lovell |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Oct 28, 2010 1:22 pm Post subject: Re: CLNTCONN .JAR Update |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| blovell wrote: |
The .JAR files being used on the client were 6.0.x.x. The problem was resolved by updating all .jar classes on the client machine.
|
If ever there was a good example of why a 'proper' install should be done, rather than just ship the .jar files, this is a prime example...
_________________
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 |
|
|
|
|
