| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ9504 - protocol error on iSeries |
« View previous topic :: View next topic » |
| Author |
Message
|
| mjaman75 |
 Posted: Thu Feb 05, 2009 11:31 am Post subject: AMQ9504 - protocol error on iSeries |
 |
|
Newbie
Joined: 06 Mar 2008
Posts: 5
|
I'm on an iSeries. We are receiving the error below when a message gets put on a local queue by a MQ Client. The queue depth increases for a very brief moment and then decreases. There are no applications that are on the queue performing a get. So something inside MQ is removing the message. To my knowledge, the client isn't receiving an error but we are checking on it. This only occurs sporadically as most messages go thru. But we have captured one of the msgs on the client side so we can resend it at will.
The channel is a server connection channel. The client uses MQI in a Java program for the MQ functions.
The iSeries system is at fix pack 6.0.2.5. The client has at least fix pack 6.0.2.3 at the very least. We are verifying that.
Any ideas on what is going on? If more information is needed, please let me know.
Thanks in advance
Mark
Job Name: AMQRMPPA QMQM 286030
-------------------------------------------------------------------------------
Message . . . . : A protocol error was detected for channel 'MDMTOPOWER_CN'.
Cause . . . . . : During communications with the remote queue manager, the channel program detected a protocol error. The failure type was 10 with associated data of 134. Recovery . . . : Contact the systems administrator who should examine the error logs to determine the cause of the failure.
------------------------------------------------------------------------------- |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Feb 05, 2009 12:03 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
and you examined the error logs to determine the cause of the failure?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mjaman75 |
| Posted: Thu Feb 05, 2009 12:41 pm Post subject: |
|
|
Newbie
Joined: 06 Mar 2008
Posts: 5
|
Bruce,
I am going thru the logs to the best of my ability. Below is another error I see in the .JOB stream file. I see these errors repeat as we send the problem msg(s) in.
Unfortunately, I do not have formal training in MQ admin. I had used MQ in a past life(I coded the MQ calls to pass data between systems and I didn't have to deal with admin), so I was the one that had the honor of setting up MQ in my current position. We play the hand we are dealt. Anyhow, I'm giving it my best shot.
Thanks,
Mark
Message ID: AMQ6184
Job Name: AMQRMPPA QMQM 286030
-------------------------------------------------------------------------------
Message . . . . : An internal WebSphere MQ error has occurred.
Cause . . . . . : An internal MQ error has occurred on queue manager
QM_MDMTOPOWER and the MQ error recording routine has been called. The
failing process is process 779. Recovery . . . : 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. Technical
Description . . . . . . . . : None. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 06, 2009 2:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If a message is appearing briefly and then disappearing, and no application has the queue open for output, then the message is in a transaction that is being rolled back. |
|
| Back to top |
|
|
| mjaman75 |
| Posted: Fri Feb 06, 2009 6:36 am Post subject: RE: AMQ9504 - protocol error on iSeries |
|
|
Newbie
Joined: 06 Mar 2008
Posts: 5
|
mqjeff, Thanks for the idea. I will look into that.
If it's being rolled back, why would it throw the error AMQ9504? We have been able to recreate the issue on a test server with the specific message that is being sent. The only MQ traffic is the one msg. So from that aspect we can narrow it down. Could bad data in the MQ header or the msg data cause this error?
The sending app is controlled by a different team. So it's taking me some time to get more info on their process. Making sure they handle errors correctly.
Thanks,
Mark |
|
| 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
|
|
|
|
