You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Kevin Koltzau (JIRA)" <ji...@apache.org> on 2011/03/11 16:41:59 UTC

[jira] Updated: (AMQ-1612) Publishing to a deleted destination topic does not produce any errors

     [ https://issues.apache.org/jira/browse/AMQ-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Koltzau updated AMQ-1612:
-------------------------------

    Attachment: DeleteDestTest.java

This issue occurs with both topics and queues.
What I am testing:
1. Create a topic or queue
2. Send a message
3. Via JMX, delete the destination
4. Send another message using the same MessageProducer as #2

What happens:
The second message is never delivered, and there is no indication of an error

I expect one of the following:
1. Both messages are delivered
2. The second MessageProducer.send throws an exception
3. ExceptionListener.onException for one or both of the connections is called

> Publishing to a deleted destination topic does not produce any errors
> ---------------------------------------------------------------------
>
>                 Key: AMQ-1612
>                 URL: https://issues.apache.org/jira/browse/AMQ-1612
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0
>            Reporter: Kevin Koltzau
>             Fix For: NEEDS_REVIEWED
>
>         Attachments: DeleteDestTest.java
>
>
> A topic was accidentally deleted while the our publisher was running, but the publisher never received any error.
> Calling ActiveMQConnection.isDeleted does return true for this destination.
> It appears the solution already partly exists, ActiveMQConnection.send contains the following lines
>         if (destination.isTemporary() && isDeleted(destination)) {
>             throw new JMSException("Cannot publish to a deleted Destination: " + destination);
>         }
> Removing destination.isTemporary() from that check appears to solve the problem, at least while topic advisories are being watched.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira