interesting,
there isn't a way to stop the incoming flux of transactional threads.
You can shutdown the container applications but that is different.
One of the things I wanted to do for jboss3.0 is an interceptor that
"freezes" threads (wait()) and notifies you when all the threads are gone so
that you know that you don't have worker threads in your engine. you can do
maintenance work on the container (even replace an interceptor) but your
database example is a good real life example. Then there is a notifyAll that
opens the valves again... there might be another way...
Now I am thinking we can do it at the JMX layer, since I am planning on
building a router, will see how it is implemented.
regards
marcf
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|[EMAIL PROTECTED]
|Sent: Saturday, June 30, 2001 8:19 AM
|To: jboss
|Subject: [JBoss-user] Taking backups
|
|
|What is a workable way of taking regular backups of the database in a
|JBoss application? I am assuming I can't just merrily copy the
|database while it is working. Is it possible to put JBoss into some
|kind of "idle" mode so that it temporarily halts all transactions (and
|flushes any unwritten data to the database) until I tell it to go
|again?
|
|I would prefer to do this without terminating JBoss first.
|
|Cheers
| Bent D
|--
|Bent Dalager - [EMAIL PROTECTED] - http://www.pvv.org/~bcd
| powered by emacs
|
|_______________________________________________
|JBoss-user mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
