On Sat, Jun 30, 2001 at 10:21:35AM -0400, David Green wrote:
> Sounds like more of a database-specific question than a JBoss question.
> For instance, with Progress, I think it's possible to halt updates to the
> actual database files, all updates are temporarily stored in .ai (after
> image files), which can be applied after the backup is complete.
I'm not sure how transactions are implemented in Java. I'm paranoid
enough, however, to think that it is possible that a Java transaction
implementation uses several DB-native transactions per one of its own
transactions. If so, then attacking this only at the database level
could result in a logically invalid backup database.
> Even if JBoss stops talking to the database, other processes might
> continue to talk to the database. Does it really make sense to tell JBoss
> to stop, then go around to each of your other applications and tell them
> to stop, so that you can make your backup real quick? This might be a
> better question for the Hypersonic or InstantDB? folks, or plug in your
> own Database.
I would certainly have to keep track of other processes with write
access to the database. I intend to keep this number very low,
preferrably at zero. What can't be done through JBoss isn't worth
doing <g>
I am not burdened with legacy software and I am doing a design from
scratch so I can pretty much make all the decisions. I want to make
sure I do it properly from the start :-)
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
