[jira] [Resolved] (MARMOTTA-498) Database Connections remain in "Idle in Transaction"

["Sebastian Schaffert (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MARMOTTA-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian Schaffert resolved MARMOTTA-498.
------------------------------------------

    Resolution: Fixed

The reason was that the Tomcat JDBC pool automatically starts a new transaction for its validation query when the connection has previously been set to autoCommit=false. The solution for PostgreSQL is to change the validation query to "SELECT 1; COMMIT;"

> Database Connections remain in "Idle in Transaction"
> ----------------------------------------------------
>
>                 Key: MARMOTTA-498
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-498
>             Project: Marmotta
>          Issue Type: Bug
>          Components: KiWi Triple Store
>    Affects Versions: 3.2.0
>            Reporter: Sebastian Schaffert
>            Assignee: Sebastian Schaffert
>
> After running for some time,  some of the database connections remain in the state "idle in transaction" instead of "idle". This indicates they are not properly closed for some reason (or not committed/rolled back).
> The bug can be observed by starting up Marmotta, connecting to Postgres and then running a SPARQL query (without any data). The connection state can be monitored in Postgres (e.g. using pgadmin)



--
This message was sent by Atlassian JIRA
(v6.2#6252)