st Regards
Simon
--
View this message in context:
http://old.nabble.com/Problems-with-prefetch-and-TemporaryQueues-tp27130529p27184578.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
lient.javaTestClient.java
>> >> > http://old.nabble.com/file/p27130529/ClientShutdownHook.java
>> >> > ClientShutdownHook.java
>> >> >
>> >> > http://old.nabble.com/file/p27130529/TestServer.javaTestServer.java
>> >>
changed my mind about the nature of the
> >> problem. The prefetch limit is not involved.
> >>
> >> My new theory goes like this:
> >>
> >> 1. The temporary queue is removed correctly when the client exists and
> >> closes its connection.
> &
sn't get that exception
>> (perhaps because the broker was soo busy that it didn't have time to
>> notify
>> the activemq part of the server in time) and instead the broker creates a
>> new queue with the same name, although without any consumer, when the
>> se
ole reports MemoryPercentageUsed 100 for the broker object).
>
>
> If this sounds reasonable, my questions are instead:
>
> * How can I prevent the broker from creating a new temporary queue because
> of the server's late message?
>
> * Would listening to advisory suppo
* How can I prevent the broker from creating a new temporary queue because
of the server's late message?
* Would listening to advisory support for the temp queue at the server side
notify me in time to stop the sending of any more messages when the temp
queue is removed?
* Or is there a bette
e.com/file/p27130529/ClientShutdownHook.java
ClientShutdownHook.java
http://old.nabble.com/file/p27130529/TestServer.java TestServer.java
http://old.nabble.com/file/p27130529/ServerShutdownHook.java
ServerShutdownHook.java
--
View this message in context:
http://old.nabble.com/Problems-with-prefetch
