It should be useful to add this kind of information as JMX operation (like list sessions).
On 20 fév, 10:59, Noel Grandin <[email protected]> wrote: > Hi > > In order to monitor for bad transactions, how about we add a > TRANSACTION_START column to the SESSIONS meta-table? > > Regards, Noel Grandin > > On 2012-02-18 09:27, Thomas Mueller wrote: > > > > > > > > > Hi, > > >> Can I add some debug settings on customer side? > > There are two options: > > > - Use the trace options to analyze the JDBC method calls (append > > ;TRACE_LEVEL_FILE=3 to the database URL) > > > - Use the Recover tool to find out if there are uncommitted > > transactions in the (large) database file (or a copy of the file; in > > this case you could even copy the database file while it's in use, > > because you don't need a 'save' copy of the database just to analyze > > the transaction log). > > >> Perhaps we need to implement some kind of default timeout on how long a > >> transaction can stay open? > > Thats a very good idea. I wonder if other databases support something > > like this? > > > At the very least there should be a warning in the .trace.db file. I > > will have a look at that. > > > Regards, > > Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
