ActiveMQ
  1. ActiveMQ
  2. AMQ-3457

temp destinations should only be deleted once all users of a pooled connection call close

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.x
    • Fix Version/s: 5.6.0
    • Component/s: None
    • Labels:
      None
    • Environment:

      5.6-SNAPSHOT

    • Patch Info:
      Patch Available

      Description

      AMQ-2349 added some code to clean up temp destinations once close() is called on a pooled connection. This caused pretty much all the JMS request-reply tests to fail in Camel with "javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination"

      The problem is that with a pooled connection, multiple users can be using a Connection at the same time (a reference count is kept of how many there are) so if once calls close() the temp destinations of several others could be deleted while they are still using them. I think the correct behavior would be to only delete the temp destinations when all connection users call close() (i.e. when the reference count becomes zero).

      Attaching a proposed fix for this shortly for review.

      1. amqpool.diff
        3 kB
        Jonathan Anstey
      2. pooledConnCleanupOwnTemps.patch
        7 kB
        Arthur Naseef
      3. PooledSessionTempDestEventListener.java
        0.5 kB
        Arthur Naseef
      4. TestConnectionPoolLingeringTemps.java
        6 kB
        Arthur Naseef
      5. TestConnectionPoolTempCleanup.java
        8 kB
        Arthur Naseef

        Activity

          People

          • Assignee:
            Jonathan Anstey
            Reporter:
            Jonathan Anstey
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development