[ 
https://issues.apache.org/jira/browse/QPIDJMS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348161#comment-15348161
 ] 

zjiali commented on QPIDJMS-186:
--------------------------------

Hi Robbie, Much appreciated for your solution. it is a good solution.  on 
client side code, after I set  "amqp.idleTimeout =0" into connection. this 
problem can be fixed.   Thanks in advance. :)

> [Borken-0.32,qpid-jms-client0.9.0] When recieve message, after about 100s, 
> throw error" The MessageConsumer was closed due to an unrecoverable error"
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-186
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-186
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>            Reporter: zjiali
>            Priority: Blocker
>
> I using "MessageConsumer.receive ()" to receive message. 
> case 1:  when I using (Borken-0.32,qpid-jms-client0.9.0), after about 100 
> seconds, throw error" The MessageConsumer was closed due to an unrecoverable 
> error". 
> case 2:  Based on case 1,  I changed to connect Borken-6.0.3 server, it works 
> without any error. 
> case 3:  Based on case 1,  I changed "qpid-jms-client0.9.0" jars as 
> "qpid-amqp-1-0-client-jms-0.32" jars, and connect with Borken-0.32, it works 
> without any error. 
> qpid-amqp-1-0-client-jms-0.32" jars download from: 
> https://qpid.apache.org/releases/qpid-0.32/index.html
> so my question is why qpid-jms-client0.9.0 +  Borken-0.32 can not work? 
> I searched out a similar issue of ActiveMQ. 
> http://qpid.2158936.n2.nabble.com/Qpid-JMS-0-9-0-receive-hanging-issue-relates-to-Artemis-works-on-ActiveMQ-td7642585.html
> Regards 
> -Gary 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to