[
https://issues.apache.org/jira/browse/AMQ-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005043#comment-13005043
]
Kevin Koltzau commented on AMQ-1612:
------------------------------------
I think I wasn't clear. Destinations are created when a publisher or subscriber
is created.
1. Create a publisher, which auto creates the destination.
2. Delete the created destination.
3. Send a message on the publisher.
The message sent in #3 will never be delivered, the destination will NOT be
recreated and there is no indication of a problem.
If #3 failed, it would give an opportunity to re-create the publisher and
re-create the destination.
> 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
>
>
> 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
