I have now registered this as a Jira issue along with a JUnit test case:
http://issues.apache.org/activemq/browse/AMQ-2571
I added another observation.
"When the TempQueue is auto(re)created it is not removed when the server
closes its connection as one (or at least I) would expect. Also, the ser
on second thoughts, the network of brokers support, which bridges temp
destinations by default, that needs (or builds on) auto create of temp
destinations. So the option to turn off auto creation for temp destinations
could be exposed as a configuration option on the broker but it can't be the
defa
Great that you have a solution that works.
I think you have a good point here. I cannot think of a reason to have auto
create for temp queues save that it negates the need to call
session.createTempX which is not well behaved w.r.t JMS semantics. Can you
open a jira issue to track this?
As to the
Thanks for the answer, Gary.
I rebuilt ActiveMQ with
setAutoCreateDestinations(false);
in the constructor of TempQueueRegion.
It seems to solve the problem. I put some logging into AbstractRegion.lookup
to verify this.
Is there any reason to have autocreating enabled by default for TempQueues?
S
this sounds like a reasonable theory.
An ActiveMQConnection by default registers interest in the advisory messages
for temp destination removal so it does try and track temp queues as you
suggest.
So if advisory support is enabled for the broker the window for recreation
of a temp queue should be s
Zemus wrote:
>
> Hi,
>
> I have a problem where TemporaryQueues are left (with 0 consumers) after
> the applications creating them have finished.
>
> This scenario occurs for both ActiveMQ 4.1.1 and 5.3.0 on my P4 2.6 GHz, 3
> GB RAM, Ubuntu 9.10, Sun JDK, default settings for ActiveMQ.
>
> I
