How does Log4j's database appender deal with Container Managed Transactions?
Specifically, how does the database appender prevent the container from rolling back logging entries as part of the business transaction that might be rolling back due to a SQL failure? Mike _______________________________________________ Siemens Medical Solutions Health Services Michael Lutz Software Engineer, Soarian Common Components 51 Valley Stream Parkway, Malvern, PA 19355 Office / Voice Mail +01 610-219-8613 Cell +01 610-952-2289 Home Office +01 610-989-3623 Fax +01 610-219-4004 E-mail <mailto:[EMAIL PROTECTED]> _______________________________________________ ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
