To answer my own question, I can redeploy my application and the
messages are persisted ok.  Cool.

On the other hand if I turn jboss off, and start it the messages are not
there.

If I change the Delivery Mode to PERSISTANT for my QueueSender, then
messages to persist accross a jboss shutdown/restart.

That's cool too.

Anyone have experience persisting messages in a cluster?  What if I fire
off a thousand messages and portions of that thousand go to different
servers in the cluster.  Then, let's say one node leaves the cluster. 
Do those messages get handled by other nodes, or do I have to restart
that node in order to handle those messages.

-Dennis
JBoss 3.0/SuSE linux

On Wed, 2002-05-08 at 16:01, Dennis Muhlestein wrote:
> Has anyone experimented around with message driven beans in the following
> sense:
> 
> What happends if I try to re-deploy my application and there is an mdb
> with a big queue not yet emptied.
> 
> Does jboss wait?  What if the beans are in a cluster.  I'll be
> experimenting around with this in the next while--just wondering if
> anyone has already tried it.
> 
> Thanks
> Dennis
> 
> 
> _______________________________________________________________
> 
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 



_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to