activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] Commented: (AMQ-1979) Temporary queue on slave not removed in Pure Master/Slave setup
Date Wed, 15 Oct 2008 14:23:52 GMT


Gary Tully commented on AMQ-1979:

exception from your test case:
2008-10-15 15:16:10,551 [MQ Session Task] ERROR JmsMessageHandler              - Failed to
delete reply queue ID:gtullyd810-51430-1224080169714-3:2:1
javax.jms.JMSException: A consumer is consuming from the temporary destination
	at org.apache.activemq.ActiveMQConnection.deleteTempDestination(
	at org.apache.activemq.command.ActiveMQTempDestination.delete(
	at org.activemq.jms.JmsMessageHandler.forwardToNext(
	at org.activemq.jms.JmsMessageHandler.onMessage(
	at org.apache.activemq.ActiveMQMessageConsumer.dispatch(
	at org.apache.activemq.ActiveMQSessionExecutor.dispatch(
	at org.apache.activemq.ActiveMQSessionExecutor.iterate(
	at org.apache.activemq.thread.PooledTaskRunner.runTask(
	at org.apache.activemq.thread.PooledTaskRunner$
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$

> Temporary queue on slave not removed in Pure Master/Slave setup
> ---------------------------------------------------------------
>                 Key: AMQ-1979
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: Hans Bausewein
>            Assignee: Gary Tully
>         Attachments: activemqjee-0.0.6-src.tar.gz
> Maybe not the most logical client code, but it happened here and I guess it will happen
somewhere again:
>   TemporaryQueue reply = session.createTemporaryQueue();      	
>   MessageConsumer consumer = session.createConsumer(reply);
>   Message received = consumer.receive(timeout);
>   ...
>   reply.delete();
>   consumer.close();
> I've removed try/finally blocks to keep it simple.
> See the attached source code.
> It works fine, but set 
>   JmsMessageHandler.REVERSE_ORDER=true
> and the slave will not be cleaned up properly.
> It means that the number of threads is increasing and at some time it will get an OutOfMemoryError
(see AMQ-1849) and the slave dies.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message