[
https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251714#comment-13251714
]
Jim Gomes edited comment on AMQNET-377 at 4/11/12 4:36 PM:
-----------------------------------------------------------
I don't think there is a bug currently filed against this issue, so this one
will do. I actually spent some time yesterday working on this unit test before
I saw your bug entry. I tried refactoring the test to see if it would fail
even if different Sessions were used, and it still does. Once it fails, all of
the consumers on that Connection are closed, regardless of Session.
was (Author: jgomes):
I don't think there is a bug currently filed against this issue, so this
one will do. I actually spent some time yesterday working on this unit test
before I saw your bug entry. I tried refactoring the test to see if it would
fail even if different Sessions were used, and it still does. Once it fails,
all of the consumers on that Connection, regardless of Session, are closed.
> Sending to non-existent temp queue causes consumer to shutdown
> --------------------------------------------------------------
>
> Key: AMQNET-377
> URL: https://issues.apache.org/jira/browse/AMQNET-377
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: ActiveMQ
> Affects Versions: 1.5.3, 1.5.4
> Environment: .NET client on Windows Server 2008 R2
> Reporter: Chris Robison
> Assignee: Jim Gomes
> Priority: Blocker
> Attachments: 2012-04-09.log, AMQ-NMS.zip, activemq.xml, putty.log
>
>
> It appears as though attempting to send a message to a non-existent temp
> queue is causing the consumer to shutdown. The behavior manifests itself by
> either the consumer ceasing to consume messages or, if a request timeout is
> set, a RequestTimedOutException being thrown. I have an NUnit project
> attached that I was able to reproduce the issue with. I've also attached logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
