You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Chris Robison (Created) (JIRA)" <ji...@apache.org> on 2012/04/10 02:49:18 UTC
[jira] [Created] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
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
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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Chris Robison (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252142#comment-13252142 ]
Chris Robison commented on AMQNET-377:
--------------------------------------
So, upon further investigation, I found that I had WatchTopicAdvisory=false because of an apparent bug and getting the exception "Channel open for too long" or something like that. Once I took that away, everything worked like the test did with AlwaysSyncSend=true.
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253604#comment-13253604 ]
Timothy Bish commented on AMQNET-377:
-------------------------------------
Nice work on the tests Jim, thanks for cleaning those up. This should be all fixed now on trunk, not sure about merging back into 1.5.x will have to look at that when time permits.
> 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
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Chris Robison (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251630#comment-13251630 ]
Chris Robison commented on AMQNET-377:
--------------------------------------
Yeah, it's pretty much the same concept. Is there another bug already filed against it?
> 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
[jira] [Resolved] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251971#comment-13251971 ]
Timothy Bish commented on AMQNET-377:
-------------------------------------
Have you tried setting the option AlwaysSyncSend on the connection, this will let the sender wait for a response from the broker which will either indicate success or throw an exception if the send fails. With an Async send the broker will send back a BrokerError that is probably why your connection is getting shut down.
> 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
[jira] [Assigned] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQNET-377:
-----------------------------------
Assignee: Timothy Bish (was: Jim Gomes)
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252702#comment-13252702 ]
Timothy Bish commented on AMQNET-377:
-------------------------------------
You need the AlwaysSyncSend because that's the only way you get an exception response back for the send otherwise the error comes back as a broker error. The sleep is to give the broker time to deal with the removal of the connection and its associated resources, which is needed in the test because we want the next send to fail deterministically. If you didn't sleep its entirely possible that the reply producer send which is using a different connection could sneak in the send before the other connection's transport connection finishes processing the remove of the connection, this is somewhat dependent though on your brokers configuration on whether its using dedicated task runners or not.
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Chris Robison (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251978#comment-13251978 ]
Chris Robison commented on AMQNET-377:
--------------------------------------
Yes, but that isn't where the failing is happening. The consumers shutdown if I attempt to send to a non-existent temp queue.
> 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
[jira] [Updated] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQNET-377:
--------------------------------
Fix Version/s: 1.6.0
1.5.5
> 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
> 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
[jira] [Updated] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQNET-377:
--------------------------------
Attachment: NonExistentTempQueueSendTest.cs
Create a test more in line with the NMS unit tests (works with .NET v2.0 no Tasks) and added the AlwaysSyncSend option as well as catching the InvalidDestinationException that is sometimes expected. Test passes.
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Jim Gomes (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252661#comment-13252661 ]
Jim Gomes commented on AMQNET-377:
----------------------------------
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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Jim Gomes (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251714#comment-13251714 ]
Jim Gomes commented on AMQNET-377:
----------------------------------
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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252061#comment-13252061 ]
Timothy Bish commented on AMQNET-377:
-------------------------------------
You need to ensure that you set the ActiveMQHost environment var or set the IP address manually in 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252656#comment-13252656 ]
Timothy Bish commented on AMQNET-377:
-------------------------------------
Which test are you referring to? If its the TempDestinationTest one it works for me every time, I ran it several times in a row.
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Jim Gomes (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252982#comment-13252982 ]
Jim Gomes commented on AMQNET-377:
----------------------------------
I made an improvement to the test to check for the deletion of the temp queue so that it can run as fast as possible, and to be more reliable. This was only checked into the trunk version to correspond with Tim's changes.
> 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
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252926#comment-13252926 ]
Timothy Bish commented on AMQNET-377:
-------------------------------------
Added what should be a fix for this in trunk, the OnCommand handling of ConnectionError commands was over aggressive in calling OnException, should call OnAsyncException instead and allow the transport layer to deal with any forced closure of the connection by the broker.
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Jim Gomes (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Jim Gomes (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251220#comment-13251220 ]
Jim Gomes commented on AMQNET-377:
----------------------------------
I think this problem may already be exposed by the existing unit test TestConsumeAfterPublishFailsForDestroyedTempDestination in the TempDestinationTest.cs file. Can you confirm if this is the same problem or not? (Currently, this unit test fails.)
> 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
[jira] [Issue Comment Edited] (AMQNET-377) Sending to non-existent
temp queue causes consumer to shutdown
Posted by "Jim Gomes (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251220#comment-13251220 ]
Jim Gomes edited comment on AMQNET-377 at 4/11/12 1:01 AM:
-----------------------------------------------------------
I think this problem may already be exposed by the existing unit test *TestConsumeAfterPublishFailsForDestroyedTempDestination* in the *TempDestinationTest.cs* file. Can you confirm if this is the same problem or not? (Currently, this unit test fails.)
was (Author: jgomes):
I think this problem may already be exposed by the existing unit test TestConsumeAfterPublishFailsForDestroyedTempDestination in the TempDestinationTest.cs file. Can you confirm if this is the same problem or not? (Currently, this unit test fails.)
> 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
[jira] [Updated] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Chris Robison (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Robison updated AMQNET-377:
---------------------------------
Attachment: putty.log
2012-04-09.log
AMQ-NMS.zip
NUnit test case to show the problem, client and server logs.
> 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, 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252684#comment-13252684 ]
Timothy Bish commented on AMQNET-377:
-------------------------------------
I was wondering if that might be the problem, the test was failing previously because there was no purge of the queue at the start which meant that on a future run it could receive messages left over from previous runs. I have not seen it fails since my changes, I ran it several times successively.
> 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
[jira] [Issue Comment Edited] (AMQNET-377) Sending to non-existent
temp queue causes consumer to shutdown
Posted by "Jim Gomes (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Chris Robison (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252043#comment-13252043 ]
Chris Robison commented on AMQNET-377:
--------------------------------------
How long is it taking for that test case to run for you? I copied it into my environment the way that you have it and it looks like the AsyncTask method thread is crashing bring the whole thing down but reporting that it passed. For me it is showing that it is completing in 2.5 seconds, but that is impossible considering there are sleeps through the whole 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252002#comment-13252002 ]
Timothy Bish commented on AMQNET-377:
-------------------------------------
Attached is a variation of your test that seems to work fine with trunk and the 1.5.x fixes branch code. Tests included in NMS.ActiveMQ need to have license granted to Apache and build with .NET v2.0.
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Issue Comment Edited] (AMQNET-377) Sending to non-existent
temp queue causes consumer to shutdown
Posted by "Jim Gomes (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Jim Gomes (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252595#comment-13252595 ]
Jim Gomes commented on AMQNET-377:
----------------------------------
Tim, I can still get the test to fail even after the change you put in to close the replyConsumer. I usually have to run it more than once, because the first time through, it will work. Try running the test more than once, one after another. I'm still trying to narrow it down, but it would be good if you could confirm that it either works all the time for you, or whether subsequent runs will fail.
> 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
[jira] [Commented] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Chris Robison (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252776#comment-13252776 ]
Chris Robison commented on AMQNET-377:
--------------------------------------
It seems a little strange to me that a BrokerException can take the whole things down without any way for the user to handle it. Is that by design?
> 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
[jira] [Updated] (AMQNET-377) Sending to non-existent temp queue
causes consumer to shutdown
Posted by "Chris Robison (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Robison updated AMQNET-377:
---------------------------------
Attachment: activemq.xml
The basic AMQ configuration I'm using.
> 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