-
Patch
-
Resolution: Obsolete
-
Major
-
JBossAS-4.0.3RC2
-
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.
- is duplicated by
-
JBAS-1445 Support for redirect upon message expiration
- Closed
1.
|
Remove the use isOutdated from clientside JMS | Closed | Unassigned | ||||||||||
2.
|
TimeoutFactory should expose thread pool | Closed | Dimitrios Andreadis |
|
|||||||||
3.
|
JBossMQ should use a TimeoutFactory configured through JMX | Closed | Elias Ross (Inactive) | ||||||||||
4.
|
Extend DLQ Config | Closed | Elias Ross (Inactive) | ||||||||||
5.
|
Add expiry processing plugin | Closed | Elias Ross (Inactive) | ||||||||||
6.
|
Test new expiry processing | Closed | Elias Ross (Inactive) | ||||||||||
7.
|
Document new expiry processing | Closed | Elias Ross (Inactive) | ||||||||||
8.
|
Remove public interface changes from HEAD | Closed | Adrian Brock (Inactive) |