[
https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476865#comment-13476865
]
Luca Tagliani edited comment on JCR-3440 at 10/16/12 9:08 AM:
--------------------------------------------------------------
Hi Bart,
I've tried the two patch you provide against 2.5.2 tag of jackrabbit core and
these are the results:
- with patch one I can reproduce the problem systematically
- with patch two I couldn't reproduce the problem
Attached you will find the log of Tomcat.
It can be separated in four part:
Part 1 (from start to line 3267): system initialization.
Part 2 (from line 3268 to line 8568): first run of test made using the
jackrabbit-core-2.5.2 original jar.
Part 3 (from line 8569 to line 12914): second run of test made using the jar
patched with patch one.
Part 4 (from line 12915 to EOF): third run of test made using the jar patched
with patch two.
By the way, trying to use Postgres, I faced a problem caused by the
introduction in o.a.j.c.util.db.ConnectionFactory of the ValidationQueryTimeout
that is not implemented in any of the Postgres jdbc driver available.
So I temporarily commented line 344.
Without this comment we cannot use Postgres anymore.
Should I file a new Jira issue for this problem?
BR
Luca
was (Author: luca.tagliani):
Hi Bart,
I've tried the two patch you provide against 2.5.2 tag of jacrabbit core and
these are the results:
- with patch one I can reproduce the problem systematically
- with patch two I couldn't reproduce the problem
Attached you will find the log of Tomcat.
It can be separated in tfour part:
Part 1 (from start to line 3267): system initialization.
Part 2 (from line 3268 to line 8568): first run of test made using the
jackrabbit-core-2.5.2 original jar.
Part 3 (from line 8569 to line 12914): second run of test made using the jar
patched with patch one.
Part 4 (from line 12915 to EOF): third run of test made using the jar patched
with patch two.
By the way, trying to use Postgres, I faced a problem caused by the
introduction in o.a.j.c.util.db.ConnectionFactory of the ValidationQueryTimeout
that is not implemented in any of the Postgres jdbc driver available.
So I temporarily commented line 344.
Without this comment we cannot use Postgres anymore.
Should I file a new Jira issue for this problem?
BR
Luca
> Deadlock on LOCAL_REVISION table in clustering environment
> ----------------------------------------------------------
>
> Key: JCR-3440
> URL: https://issues.apache.org/jira/browse/JCR-3440
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: clustering
> Affects Versions: 2.4.3
> Environment: Env.1: 4x Linux server CentOS 5 MSSQL 2008 database
> (production system)
> Env.2: 2x Linux Ubuntu 10.04 server tested with PostgreSQL 9.1, H2, MSSQL
> 2008 and mySQL 5.5 (lab system)
> Reporter: Luca Tagliani
> Priority: Critical
> Attachments: catalina.out, fixAlwaysBatchMode.patch,
> fixNoLockOnLocalRevisionsWIP.java, JCR-3440.patch, threadDump-JCR-3440.txt
>
>
> When inserting a lot of nodes concurrently (100/200 threads) the system hangs
> generating a deadlock on the LOCAL_REVISION table.
> There is a thread that starts a transaction but the transaction remains open,
> while another thread tries to acquire the lock on the table.
> This actually happen even if there is only a server up but configured in
> cluster mode.
> I found that in AbstractJournal, we try to write the LOCAL_REVISION even if
> we don't sync any record because they're generated by the same journal of the
> thread running.
> Removing this unnecessary (to me :-) ) write to the LOCAL_REVISION table,
> remove the deadlock.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
