[
http://jira.jboss.com/jira/browse/JBAS-2156?page=all ]
Andrig Miller updated JBAS-2156:
--------------------------------
Fix Version/s: No Release
(was: JBossAS-5.0.0.Beta)
JBoss MQ will not be a part of JBoss AS 5, and is being replaced by JBoss Messaging. This
work should be placed into JBoss Messaging, and I believe there is an existing JIRA issue
in the JBoss Messaging project that deals with this.
Patch to add expiry queue support to JBossMQ
--------------------------------------------
Key: JBAS-2156
URL:
http://jira.jboss.com/jira/browse/JBAS-2156
Project: JBoss Application Server
Issue Type: Patch
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.3RC2
Reporter: Elias Ross
Assigned To: Elias Ross
Fix For: No Release
Attachments: expiry.diff, expiry.diff, expiry.txt,
ExpiryDestinationTestCase.java
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira