You know JMS is asynchronous and although you can
guarantee message delivery, you cannot guarantee when?
I suspect you would want some replication that is more
closely tied to the transaction commits.
The replication doesn't need to be immediate -- as long as it happens. A certain amount of lag time is acceptable in this application -- and the amount that we're allowing for would be (I would think) well within the delay time I presumed I might see with JMS...maybe not, though -- what kind of delay can I expect?
I don't want to tie up the local user waiting on synchronous replication to several remote locations. Once the commit happens locally, they can continue on. The remote sites can be updated afterwards.
There will be periodic database auditing to ensure that all is well.