XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 5.2.0
    • 5.2.0
    • None
    • None
    • 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")

    Description

      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?

      Attachments

        1. ASF.LICENSE.NOT.GRANTED--jboss.log
          4 kB
          Hans Bausewein
        2. activemqjee-0.0.2-src.tar.gz
          5 kB
          Hans Bausewein

        Activity

          People

            gtully Gary Tully
            hansb Hans Bausewein
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: