activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (Commented) (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Commented] (AMQNET-377) Sending to non-existent temp queue causes consumer to shutdown
Date Thu, 12 Apr 2012 18:25:17 GMT

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

Jim Gomes commented on AMQNET-377:
----------------------------------

The queue purge was a good addition to the test.  As I play around with it a bit, I can get
it to fail if I comment out only the Thread.Sleep() call.  It failed on about the 20th loop.
 I'm still trying to understand all of the interactions here.  Specifically, why is the AlwaysSyncSend
option necessary, and why is the sleep delay necessary?  I've never used the AlwaysSyncSend
option before, and I don't think we can count on a delay in a real production scenario that
is trying to run at top speed.  Thoughts?
                
> 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

        

Mime
View raw message