pageStore: Transaction log could not be truncated - anything to worry about?

[Sanjeev Gour]

Hello-

I see in my application that this message is sometime printed in the trace file. I see a related post to this message but I am unsure if it is really a problem or an informational message. Is there any important info that I lose when this message is printed?

This is the related post-

https://groups.google.com/forum/#!topic/h2-database/-d1IBmUt3Zw

Thanks.

[Noel Grandin]

No, it's more of a performance issue.
We improved our code in later versions to hit this less often, but you can also just up the size of the transaction log.

> --
> You received this message because you are subscribed to the Google Groups "H2 Database" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
> h2-database...@googlegroups.com <mailto:h2-database...@googlegroups.com>.
> To post to this group, send email to h2-da...@googlegroups.com <mailto:h2-da...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/h2-database.
> For more options, visit https://groups.google.com/d/optout.

[Thomas Mueller]

Hi,

This message is just to inform that there is probably a long running transaction that was not committed. I'm not quite sure currently whether this message is sometimes logged even if there is no such transaction (meaning that the message is sometimes logged in error).

What you should check is if you do have a long running transaction, as in general this should be avoided. But no data is lost.

Regards,

Thomas

--
You received this message because you are subscribed to the Google Groups "H2 Database" group.

To unsubscribe from this group and stop receiving emails from it, send an email to h2-database...@googlegroups.com.
To post to this group, send email to h2-da...@googlegroups.com.

[Sanjeev Gour]

Is there a way to enable additional logging in H2 to understand which transaction is long running? I am trying to map with timestamp in our logs with the timestamp in the trace file but that doesn't seem to pinpoint the location as there are several operations going on at the same time.

Thanks.

On Monday, 11 August 2014 23:34:51 UTC+5:30, Thomas Mueller wrote:

Hi,

This message is just to inform that there is probably a long running transaction that was not committed. I'm not quite sure currently whether this message is sometimes logged even if there is no such transaction (meaning that the message is sometimes logged in error).

What you should check is if you do have a long running transaction, as in general this should be avoided. But no data is lost.

Regards,

Thomas

On Mon, Aug 11, 2014 at 11:26 AM, Sanjeev Gour <sanjee...@gmail.com> wrote:

Hello-

I see in my application that this message is sometime printed in the trace file. I see a related post to this message but I am unsure if it is really a problem or an informational message. Is there any important info that I lose when this message is printed?

This is the related post-

https://groups.google.com/forum/#!topic/h2-database/-d1IBmUt3Zw

Thanks.

--
You received this message because you are subscribed to the Google Groups "H2 Database" group.

To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscribe@googlegroups.com.

[Thomas Mueller]

Hi,

Is there a way to enable additional logging in H2 to understand which transaction is long running?

You can run the following query to get data about open sessions: SELECT * FROM INFORMATION_SCHEMA.SESSIONS 

When appending ";trace_level_system_out=3;trace_level_file=3" to the database URL, you should get more detailed information about which connection did what operation (see the documentation).

Regards,

Thomas

 

To unsubscribe from this group and stop receiving emails from it, send an email to h2-database...@googlegroups.com.