| Author |
Message
|
| sieijish |
 Posted: Fri May 19, 2006 4:22 am Post subject: JMS receive() error |
 |
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
At times, I get this following error from the receive(300) method of QueueReceiver object. When this happens, the receive() method freezes and get the following errors.
Server is using MQ5.3 + CSD11 on AIX.
Clinet is using
IBM JMS library is Implementation-Version: "5.306 - j5306-09-041027"
Specification-Title: "Java Message Service"
Specification-Version: "1.1"
Has anyone seen this before?
AMQERR01.log:
------------
Error:
18/05/06 14:35:43
AMQ9208: Error on receive from host 172.17.0.28.
EXPLANATION:
An error occurred receiving data from 172.17.0.28 over TCP/IP. This may be due
to a communications failure.
ACTION:
The return code from the TCP/IP (read) call was 73 (X'49'). Record these values
and tell the systems administrator.
----- amqccita.c : 2713 -------------------------------------------------------
Client freeze on receive(300) call & gets error
---------------------------------------------------
javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:553)
at com.ibm.mq.jms.MQMessageConsumer.getMessageQ(MQMessageConsumer.java:1820)
at com.ibm.mq.jms.MQMessageConsumer.getMessage(MQMessageConsumer.java:4313)
at com.ibm.mq.jms.MQMessageConsumer.receiveInternalQ(MQMessageConsumer.java:2407)
at com.ibm.mq.jms.MQMessageConsumer.receiveQ(MQMessageConsumer.java:2233)
at com.ibm.mq.jms.MQMessageConsumer.receive(MQMessageConsumer.java:4239)
at net.inspiredbroadcast.legion.dw.staging.MQSubscriber.run(MQSubscriber.java:231)
at java.lang.Thread.run(Thread.java:595) |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri May 19, 2006 6:24 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| You need to get the LinkedException. That will give an exact MQ Error code. Search for LinkedException in the forum and you will get lot of hits. |
|
| Back to top |
|
|
| 8davitt |
| Posted: Tue May 23, 2006 1:22 am Post subject: |
|
|
Apprentice
Joined: 06 Feb 2003
Posts: 37
Location: Seated in front of monitor
|
TCP/IP (read) call was 73 (X'49') = ECONNRESET
1. Get your client to the same level as server, FP11. Better yet apply FP12 to both.
2. It could be a genuine TCP/IP error. After you have verified that the problem persists after installing with a FP11 client then checkout your network to ensure there are no problems.
/s |
|
| Back to top |
|
|
| sieijish |
| Posted: Thu May 25, 2006 8:04 am Post subject: |
|
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
Venella, the linked exception i receive is
Linked Exception:
----------------
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.getMsg2(MQQueue.java:943)
at com.ibm.mq.jms.MQMessageConsumer.getMessageQ(MQMessageConsumer.java:1532)
at com.ibm.mq.jms.MQMessageConsumer.getMessage(MQMessageConsumer.java:4313)
at com.ibm.mq.jms.MQMessageConsumer.receiveInternalQ(MQMessageConsumer.java:2407)
at com.ibm.mq.jms.MQMessageConsumer.receiveQ(MQMessageConsumer.java:2233)
at com.ibm.mq.jms.MQMessageConsumer.receive(MQMessageConsumer.java:4239)
at net.inspiredbroadcast.legion.dw.staging.MQSubscriber.run(MQSubscriber.java:242)
at java.lang.Thread.run(Thread.java:595) |
|
| Back to top |
|
|
| sieijish |
| Posted: Thu May 25, 2006 8:09 am Post subject: |
|
|
Acolyte
Joined: 29 Nov 2004
Posts: 67
Location: London
|
| This error is more frequent when the subscriber is processing message at very high rates (>120 msgs/sec per subscriber) I am running 5 or them each using its own connection & jms session. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu May 25, 2006 8:20 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| 8davitt wrote: |
| TCP/IP (read) call was 73 (X'49') = ECONNRESET |
ECONNRESET is often a sign of a firewall disrupting MQ's connectivity.
| Quote: |
| Get your client to the same level as server, FP11. Better yet apply FP12 to both. |
FP12 - definitely a good idea. FP9 had problems, particularly for JMS clients. |
|
| Back to top |
|
|
|
|
