Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-2156

Patch to add expiry queue support to JBossMQ

XMLWordPrintable

    • Icon: Patch Patch
    • Resolution: Obsolete
    • Icon: Major Major
    • No Release
    • JBossAS-4.0.3RC2
    • JMS (JBossMQ)
    • None

      Added attributes "ExpiryDestination" to DestinationMBean and DestinationManagerMBean to indicate an ObjectName of queue to receive expired messages. This destination queue must be bound into JNDI when this queue starts.

      The messages are copied over to this queue when expiry time is reached and the original expiration and destination is kept in the vendor parameters "JBOSS_ORIG_EXPIRATION" and "JBOSS_ORIG_DESTINATION". The same JMSMessageID is kept in the copied message.

      The limitation of this is that the queue must be located on the same local JBoss server.

      Another limitation is that the expired message is only removed after its copy has been added to the new destination. Ideally, the "move" would happen within a single transaction.

        1. expiry.diff
          109 kB
        2. expiry.diff
          20 kB
        3. expiry.txt
          2 kB
        4. ExpiryDestinationTestCase.java
          5 kB

            genman_jira Elias Ross (Inactive)
            genman_jira Elias Ross (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days
                2d