David Lloyd [https://community.jboss.org/people/dmlloyd] created the discussion "Re: Transactional MSC" To view the discussion, visit: https://community.jboss.org/message/828664#828664 -------------------------------------------------------------- OK I will attempt to answer as many questions as I can. Starting off with the tough ones I see. :) Currently our audit requirements are met by using syslog-style remote logging, which is done in a very ad-hoc manner (i.e. without sensitivity to crashes).  It will be difficult, regardless of the answer to this question, to both meet the remote log requirement as well as dealing with the possibility of crashing.  AFAIK there is no way to log to syslog transactionally. Ignoring that problem though, my feeling is that we are only required to Audit (with a capital A) changes that were successfully made, but we do want to at least locally log (in a human-readable fashion) failures as well. I think not.  I think we will want to isolate the administration actions from the user's transactions as completely as possible. Only insofar as the previous requirement can be met. Just application transactions.  The MSC/management transactions should be separately recoverable, as the management system cannot be initialized without its database. No. Yes (see above). Yes. Yes.  The object store should be separate as mentioned above.  The recovery system should probably not be (directly) network-enabled for MSC.  Looking over the environment beans, I'm going to say "yes these need to be considered".  I see many parameters that seem likely to be able to cause trouble for the management system. -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/828664#828664] Start a new discussion in JBoss Transactions Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]