| Author |
Message
|
| shashi |
 Posted: Sun Oct 18, 2015 7:48 pm Post subject: Issue in MQ Version 6 |
 |
|
Newbie
Joined: 16 Oct 2015
Posts: 4
|
Hi Everyone..
I am new to this forum..And I am facing one issue, need help on this.
I have MQ Server which is running on version 6.0.2.11 , and one application is connecting through Web Methods as client.
Now when the application is trying to put msgs in to one of the queue,it getting 2009 error randomly for any one msg for first time, and when it is trying to put the same msg second time it is taking fine.
In error logs it is written as protocal error.
AMQ9504: A protocol error was detected for channel 'SYSTEM.DEF.SVRCONN'.
For the same error one FDC got generated and the PROBEID is:RM046007.
Can anyone explain the cause of this error please. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sun Oct 18, 2015 9:31 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
1) MQ Version 6 has been out of support for several years. You really do need upgrade.
2) No user application should be using the SYSTEM.DEF.SVRCONN channel. This is not good practice
3) 2009 errors are often attributed to communication/network problems.
You chould check your network routing and firewalls.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| shashi |
| Posted: Sun Oct 18, 2015 10:35 pm Post subject: |
|
|
Newbie
Joined: 16 Oct 2015
Posts: 4
|
Thank you..Jedi.
1) We have suggested to upgrade but there is no plan from customer to upgrade in near future.And for default SVR.CONN channel also..
2)We had thoroughly checked with n/w and firewall and we found there is no issue with them.
| Quote: |
Error description
A JAVA.IO.EOFEXCEPTION accompanied by an unexpected error (2195)
and a connection broken error(2009) occurs when receiving
message with the WebSphere MQ Java client. The queue manager
(server) side will see the rrcE_PROTOCOL_ERROR from component
rriMQIServer and probe id RM046007.
PROBLEM SUMMARY:
There was a difference in the number of bytes anticipated by
the WMQ Java client and those received from the server. This
occurred due to a miscalculation in the number of bytes
requested by the WMQ Java client. When the WMQ client was in the
process of receiving messages, this miscalculation resulted in
an unexpected end of stream being received from the WMQ
server. |
This is the info I found by using Probeid:RM046007.
I just need an confirmation like whether this issue had anything to do with application..or it is purely MQ issue..? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 19, 2015 4:17 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Time to Upgrade... You should be at V 7.1, 7.5, or 8.0 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 19, 2015 4:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashi wrote: |
| it is purely MQ issue..? |
Is this a new application, or an application that used to work and suddenly stopped?
It's unlikely to be an application problem. It's most likely that someone updated something in the stack (maybe a new Java level or patched the OS) and this has caused this problem within the MQ layer.
Because the MQ layer is way, way out of date and won't understand anything invented in the last decade or so.
Tell your customer the business risk they took not bothering to upgrade MQ just blew up in their faces.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashi |
| Posted: Mon Oct 19, 2015 5:10 am Post subject: |
|
|
Newbie
Joined: 16 Oct 2015
Posts: 4
|
Hi Vitor..
This is old application only, and it is worked fine before 2 months..
From last two months we are getting this issue..
And we observed one thing like..,this error is coming for a random msg for first time only,when we try to put the same msg second time it is coming to queue without any problem.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 19, 2015 5:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shashi wrote: |
This is old application only, and it is worked fine before 2 months..
From last two months we are getting this issue.. |
Then 2 months ago someone updated something in the stack, and your old version of MQ doesn't like it.
| shashi wrote: |
| And we observed one thing like..,this error is coming for a random msg for first time only,when we try to put the same msg second time it is coming to queue without any problem |
Consider this a taste of things to come. After a future upgrade of something you can't detect, it will start happening the first time for every message. Or stop working at all.
Enjoy.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Oct 20, 2015 3:06 pm Post subject: |
|
|
Jedi
Joined: 25 Mar 2003
Posts: 2494
Location: Melbourne, Australia
|
Does WebMethods implement its own MQ Client, or does it use the MQ libraries / classes ? If it has its own client code, there could be a bug in the protocol that it implements.
_________________
Glenn |
|
| Back to top |
|
|
|
|
