#1 is in fact the JMS default (javax.jms.DeliveryMode.PERSISTENT).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887081#3887081
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887081
-
I got a recommendation against using MySQL for blobs here.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887080#3887080
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3887080
--
Oh I forgot to say, "Legacy App."
So if I were willing to add new code, I'd consume those messages in the MDB
then store them in another queue which nobody is consuming. But the queue
doesn't finish in time only when there are other problems, so I prefer a n
administration solution over a progr
I'm using JBoss 4.0.2 with MySQL based persistence. I have a requirement that
if any messages aren't processed by a certain time, I need to move them to
another queue and reprocess the next day.
I do this by updating JMS_MESSAGE_LOG and changing the destination. However, I
need JBoss shut down
