Recovery bug: prepared transaction belongs to another database

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Recovery bug: prepared transaction belongs to another database

Andrew Frolov
This post has NOT been accepted by the mailing list yet.
Hi guys!

I think I found bug in Bitronix. If I have pending transactions, bitronix is trying to repair it and execute rollback or commit commands.  But in PostgreSQL you have to execute "commit prepared" command only in database where it belongs.

- I work with several databases from single JVM.
- I have 16 pending transactions in database (it's ok.)
- bitronix.tm.currentNodeOnlyRecovery=true  
- bitronix chooses one for recovery
- and executes commit prepared in wrong database.


This is my log.
http://pastebin.com/ECx4d1Nw

p.s. I use bitronix-hp fork.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Recovery bug: prepared transaction belongs to another database

Andrew Frolov
This post has NOT been accepted by the mailing list yet.
This bug is probably not yours.

PostgreSQL JDBC driver in PGXAConnection.recover() returns all xa transactions in the whole cluster.  I should probably be replaced by  transactions only in current database.

Same problem but, unfortunately, without an answer .
http://www.postgresql.org/message-id/CAPSK6ngYLaRAy_FGGQqknTPE9FUDCRn32UShxuncWEyD+swD=w@mail.gmail.com
Loading...