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/09/08 13:30:09 UTC

[jira] Closed: (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:all-tabpanel ]

Hans Bausewein closed AMQ-1849.
-------------------------------


The test with the attached "activemqjee-0.0.2" worked fine.

> 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
>            Assignee: Gary Tully
>             Fix For: 5.2.0
>
>         Attachments: 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.