DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35693>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35693 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |blocker ------- Additional Comments From [EMAIL PROTECTED] 2005-07-11 22:16 ------- Yes, I have seen another problem with the read-only store enlistment changes and had to back them out of my personal build as well. In my case, which is also for DB2 and using external client-initiated transactions, it seems that all transactions including reads need to be enlisted to the same transaction or the db deadlocks. Can these "read-only" store enlistment changes be backed out or at least made configurable/optional for those of us using DB2? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
