You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/19 00:36:39 UTC
[jira] [Resolved] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-377.
---------------------------------
Resolution: Fixed
Fixed on trunk and in the 1.5.x branch. On the older 1.5 branch the exception will arrive via onException event as an NMSConnectionException.
> 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: Timothy Bish
> Priority: Blocker
> Fix For: 1.5.5, 1.6.0
>
> Attachments: 2012-04-09.log, AMQ-NMS.zip, NonExistentTempQueueSendTest.cs, 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