[
http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ]
Jeff Mesnil updated JBMESSAGING-381:
------------------------------------
Attachment: patch-JBMESSAGING-381.txt
tentative patch.
corresponding test case is:
export TARGET_CLASS=org.jboss.test.messaging.jms.PersistenceTest
export TARGET_TEST=testQueueWithDisabledPersistence
test case is:
* deploy a queue with disabled persistence
* send a few messages with DeliveryMode.PERSISTENT
* restart the server
* redeploy the same queue
* check that the queue is empty
(the opposing test is PersistenceTest.testQueuePersistence() which checks
that the messages are still in the queue after restart)
- Persistent is true by default for destinations.
- It can be set only before the destination is started (at deployment time)
- a "not persistent" destination corresponds to a MessagingQueue w/o a
PersistenceManager and flagged as non recoverable
I did not check passing null as a PersistenceManager in ChannelSupport is acceptable... it
may generate unexpected NPE...
Add param on destination to disable persistence
-----------------------------------------------
Key: JBMESSAGING-381
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-381
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta 1
Attachments: patch-JBMESSAGING-381.txt
Original Estimate: 1 day
Remaining Estimate: 1 day
We should add a configuration param on destinations which id true prevents messages being
persisted even if they are persistent.
This should give equivalent functionality to the JBossMQ NullPersistenceManager.
in some circumstances uses want to override persistence for messages but have no access
to change the delivery mode at the sender.
--
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