You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hans Bausewein (JIRA)" <ji...@apache.org> on 2008/07/10 12:44:00 UTC
[jira] Commented: (AMQ-1849) Slave threads increasing when sending
to temporary queue
[ https://issues.apache.org/activemq/browse/AMQ-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44162#action_44162 ]
Hans Bausewein commented on AMQ-1849:
-------------------------------------
Everytime it happens, I get a ClassCastException in "data/activemq.log" on the slave host:
2008-07-10 11:48:33,907 [t: vm://slavehost#1] ERROR Queue - Failed to page in more queue messages
java.lang.ClassCastException: org.apache.activemq.command.ActiveMQTextMessage cannot be cast to org.apache.activemq.broker.region.QueueMessageReference
at org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:1045)
at org.apache.activemq.broker.region.Queue.messageExpired(Queue.java:1037)
at org.apache.activemq.broker.region.Queue.doPageIn(Queue.java:1117)
at org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:1196)
at org.apache.activemq.broker.region.Queue.iterate(Queue.java:951)
at org.apache.activemq.broker.region.Queue.wakeup(Queue.java:1077)
at org.apache.activemq.broker.region.Queue.sendMessage(Queue.java:1072)
at org.apache.activemq.broker.region.Queue.doMessageSend(Queue.java:470)
at org.apache.activemq.broker.region.Queue.send(Queue.java:413)
at org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:350)
at org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:437)
at org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:224)
at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
at org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:95)
at org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:133)
at org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:437)
at org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:624)
at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:292)
at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:180)
at org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:104)
at org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
at org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:205)
at org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98)
at org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:36)
> Slave threads increasing when sending to temporary queue
> --------------------------------------------------------
>
> Key: AMQ-1849
> URL: https://issues.apache.org/activemq/browse/AMQ-1849
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.2.0
> Environment: Pure master/slave
> JBoss 4.0.5 GA (on Java 1.5.0_14)
> few days old ActiveMQ 5.2.0-SNAPSHOT (on Java "1.6.0_06")
> Reporter: Hans Bausewein
> Attachments: activemqjee-0.0.1-src.tar.gz, activemqjee-0.0.2-src.tar.gz, jboss.log
>
>
> Deployed the attached TextMDB (modified JBoss example) to our JBoss 4.0.5 GA server (cluster).
> - send a message to "queue.A" with Reply To set to "queue.REPLY_A"
> The TextMDB bean:
> - creates a temporary queue with NON_PERSISTENT delivery mode
> - forwards message body to "queue.B" and sets the reply queue to this temporary queue
> - another (or the same) instance of TextMDB replies and adds some text, replies to the temporary queue
> - the first TextMDB replies to "queue.REPLY_A"
> Works fine, except that every time a temporary queue message is sent, the number of threads on the slave increases by 3.
> On the master the threads are destroyed after a while, but on the slave they persist, growing to "OutOfMemoryError: unable to create new native thread"
> Temporary queue Thread Name example: TempQueue: ID:{HOSTNAME}-59619-1215591084487-0:16:5
> + 2 topic threads
> That thread ID can be found ActiveMQ messages in the attached JBoss log.
> Have I created a bug im my code or have I found a bug in the ActiveMQ server?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.