[
https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252826#comment-13252826
]
Timothy Bish commented on AMQNET-377:
-------------------------------------
Yes, I think there's still an issue here with that, but for now a simple
workaround is to use the AlwaysSyncSend option. When I have some spare time I
will look into this a bit more. If anyone wants to construct a simpler test
for this to add to the TempDestinationTest test set feel free, should be easy
enough to reproduce by creating a temp dest and deleting it and then trying to
send to it ensuring that AlwaysSyncSend is true, and WatchTopicAdvisories is
false.
> 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,
> 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
