Hi Paul,
I made the same mistake here, I sent it to the wrong list, sorry for that,
I will send it to the correct one.
Christian
On Tue, Jun 19, 2012 at 9:13 PM, Paul Parkinson
<paul.parkinson_at_oracle.com>wrote:
> Hi Christian,
>
> Yes, the lack of certain recovery specification is a long standing known
> omission and has come up many times in the past. I expect this may take
> some time to negotiate in the community as most application servers do this
> in different ways if only subtly in some cases. Could I ask you to post
> this on users_at_jta-spec.java.net for comment from the community there as
> it relateds to JTA?
>
> Thanks,
> Paul
>
> On Jun 19, 2012, at 3:49 AM, Christian Romberg wrote:
>
> Hi Paul, all,
>
> JTA 1.1 does not mandate, how an XAResource is restored after a system
> failure for the purpose of
> transaction recovery conducted by the transaction manager.
>
> Common suggestions and implementations (e.g. JBoss) use the following
> strategies:
>
> 1. If the XAResource was acquired by a JNDI-named pool, the JNDI name can
> be stored in the
> transaction log file of the transaction manager
>
> 2. If the XAResource is Serializable, then the XAResource can be
> serialized into the transaction log
> file of the transaction manager.
>
> Nothing of this is mandated by the JTA spec.
>
> Any transaction manager implementation needs a portable way to restore
> XAResources.
>
> If 1. alone would be mandatory, this would not work for us, because we
> don't use a JNDI-based pool
> but register our XAResource instances directly with the Transaction.
>
> I suggest to mandate the following behavior for the transaction manager
> when writing it's log file:
>
> "If the XAResource was acquired via a JNDI named pool or the XAResource is
> serializable, the
> transaction manager might store the JNDI name, or the serialized
> XAResource in it's transaction
> log file. If the XAResource was not acquired via a JNDI named pool and is
> not serializable, an
> exception will be thrown".
>
> Thank you!
>
> Regards,
>
> Christian
>
> --
> Christian Romberg
> Chief Engineer | Versant GmbH
> (T) +49 40 60990-0
> (F) +49 40 60990-113
> (E) cromberg_at_versant.com
> www.versant.com<http://www.google.com/url?q=http%3A%2F%2Fwww.versant.com%2F&sa=D&sntz=1&usg=AFrqEzeeEBc_gN_8mxtt8xDB0tjXDXQVlw>|
> www.db4o.com<http://www.google.com/url?q=http%3A%2F%2Fwww.db4o.com%2F&sa=D&sntz=1&usg=AFrqEzdo3Q40RwKQPBtnPIuBYQd1diFxJQ>
>
> --
> Versant
> GmbH is incorporated in Germany. Company registration number: HRB
> 54723, Amtsgericht Hamburg. Registered Office: Halenreie 42, 22359
> Hamburg, Germany. Geschäftsführer: Bernhard Wöbker, Volker John
>
> CONFIDENTIALITY
> NOTICE: This e-mail message, including any attachments, is for the sole
> use of the intended recipient(s) and may contain confidential or
> proprietary information. Any unauthorized review, use, disclosure or
> distribution is prohibited. If you are not the intended recipient,
> immediately contact the sender by reply e-mail and destroy all copies of
> the original message.
>
>
>
>
>
--
Christian Romberg
Chief Engineer | Versant GmbH
(T) +49 40 60990-0
(F) +49 40 60990-113
(E) cromberg_at_versant.com
www.versant.com<http://www.google.com/url?q=http%3A%2F%2Fwww.versant.com%2F&sa=D&sntz=1&usg=AFrqEzeeEBc_gN_8mxtt8xDB0tjXDXQVlw>|
www.db4o.com<http://www.google.com/url?q=http%3A%2F%2Fwww.db4o.com%2F&sa=D&sntz=1&usg=AFrqEzdo3Q40RwKQPBtnPIuBYQd1diFxJQ>
--
Versant
GmbH is incorporated in Germany. Company registration number: HRB
54723, Amtsgericht Hamburg. Registered Office: Halenreie 42, 22359
Hamburg, Germany. Geschäftsführer: Bernhard Wöbker, Volker John
CONFIDENTIALITY
NOTICE: This e-mail message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential or
proprietary information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
immediately contact the sender by reply e-mail and destroy all copies of
the original message.