You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Rob Davies (JIRA)" <ji...@apache.org> on 2008/06/06 16:00:00 UTC
[jira] Created: (AMQ-1778) Request/Reply across a Queue stalls
Request/Reply across a Queue stalls
------------------------------------
Key: AMQ-1778
URL: https://issues.apache.org/activemq/browse/AMQ-1778
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.1.0, 5.0.0
Reporter: Rob Davies
Assignee: Rob Davies
Fix For: 5.2.0
see http://www.nabble.com/ActiveMQ-5.1-broken---repro-test-included-td17681102s2354.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-1778) Request/Reply across a Queue stalls
Posted by "Hans Bausewein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans Bausewein updated AMQ-1778:
--------------------------------
Attachment: output.tar
JmsTest.tar
Modified the sources to:
- close receivers and senders
- log more exceptions
- create a QueueBrowser to look for the missing messages
I hope I still test the same issue, but it still seems to happen.
What I've found:
1. Apparently the MessageConsumer does not find the messages, but they are still on the queue.
2. If the sender threads are interrupted after the timeout and after the receiver closed, I get some InterruptedIOException in the ActiveMQSession.close() method:
Caused by: javax.jms.JMSException: java.io.InterruptedIOException
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)
at org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1178)
at org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1170)
at org.apache.activemq.ActiveMQSession.close(ActiveMQSession.java:548)
at org.apache.activemq.ActiveMQQueueSession.close(ActiveMQQueueSession.java:65)
at test.JmsSenderTest.facilityRequest(JmsSenderTest.java:253)
See "output-interrupted.log"
So closing the session takes quite long.
NOTE: purge (empty) the "testResponses" queue before a test. When there are a lot of messages on it, the results are worse.
I guess it may be some resource issue. (sockets, memory,...?)
No time to check more, now.
hope it helps. Interesting case.
> Request/Reply across a Queue stalls
> ------------------------------------
>
> Key: AMQ-1778
> URL: https://issues.apache.org/activemq/browse/AMQ-1778
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0, 5.1.0
> Reporter: Rob Davies
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: JmsTest.tar, output.tar
>
>
> see http://www.nabble.com/ActiveMQ-5.1-broken---repro-test-included-td17681102s2354.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1778) Request/Reply across a Queue stalls
Posted by "Sharon Barker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43483#action_43483 ]
Sharon Barker commented on AMQ-1778:
------------------------------------
I was able to consistently reproduce the loss of a message with NateS' sample code.
When I reduced the thread pool size to 1 there was no loss of messages in several runs that I tried.
Because my application does not use the correlation ids at all, I adjusted the samples slightly to use separate queues for the responses. Under that circumstance, I did not see any message losses.
These results make me suspect that the loss of messages is related to using correlation ids across many threads.
> Request/Reply across a Queue stalls
> ------------------------------------
>
> Key: AMQ-1778
> URL: https://issues.apache.org/activemq/browse/AMQ-1778
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0, 5.1.0
> Reporter: Rob Davies
> Assignee: Rob Davies
> Fix For: 5.2.0
>
>
> see http://www.nabble.com/ActiveMQ-5.1-broken---repro-test-included-td17681102s2354.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1778) Request/Reply across a Queue stalls
Posted by "Hans Bausewein (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43897#action_43897 ]
Hans Bausewein commented on AMQ-1778:
-------------------------------------
BTW: for me it's (of course) okay to include the code anywhere, but I was not the author of most of it, so I did not specify that.
> Request/Reply across a Queue stalls
> ------------------------------------
>
> Key: AMQ-1778
> URL: https://issues.apache.org/activemq/browse/AMQ-1778
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0, 5.1.0
> Reporter: Rob Davies
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: JmsTest.tar, output.tar
>
>
> see http://www.nabble.com/ActiveMQ-5.1-broken---repro-test-included-td17681102s2354.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1778) Request/Reply across a Queue stalls
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1778.
-----------------------------
Resolution: Fixed
This is resolved for 5.2
> Request/Reply across a Queue stalls
> ------------------------------------
>
> Key: AMQ-1778
> URL: https://issues.apache.org/activemq/browse/AMQ-1778
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.0.0, 5.1.0
> Reporter: Rob Davies
> Assignee: Rob Davies
> Fix For: 5.2.0
>
> Attachments: JmsTest.tar, output.tar
>
>
> see http://www.nabble.com/ActiveMQ-5.1-broken---repro-test-included-td17681102s2354.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.