activemq-dev mailing list archives

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

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

Jim Gomes edited comment on AMQNET-377 at 4/12/12 6:11 PM:
-----------------------------------------------------------

-It's the *TestConsumeAfterPublishFailsForDestroyedTempDestination* test.  On the second pass,
it will usually fail randomly between the 15th and 25th loop of the test.-

Scratch that.  Looks like I may have had a merge error with some of my local changes.  I've
reverted out my local changes, and the test seems to succeed consistently now.
                
      was (Author: jgomes):
    It's the *TestConsumeAfterPublishFailsForDestroyedTempDestination* test.  On the second
pass, it will usually fail randomly between the 15th and 25th loop of the test.
                  
> 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