jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luis Muniz <neur0ma...@gmail.com>
Subject Re: Deadlock in my JCR repository
Date Thu, 07 Oct 2010 13:07:55 GMT
Hi Jukka,

Of course, I do appreciate the time you put in to help out, and possibly
state the obvious from your perspective. We don't update every component of
our architecture if it is stable. Our repository was fairly stable until
lately. We have a 20GB+ repository so the migration, jumping minor versions
and a major version, is not going to be trivial. I guess the first thing
will have to be to create a migration script. I read in the wiki that from
1.6 on there is a migration program, but that does not solve my issue.

The thread dump we forgot to generate it and we will generate one when the
issue gets reproduced.

I know that identifying the deadlock with the information I provided is not
possible unless some of the elements taht appear in my log remind someone of
a similar case, which was what I was hoping for. it was a long shot, but it
was all I could currently do to diagnose the issue without a thread dump.

Anyway, I'll post an update in this thread in case another lost soul is
looking for this information.

Thanks again for your time,


On Thu, Oct 7, 2010 at 2:42 PM, Jukka Zitting <jukka.zitting@gmail.com>wrote:

> Hi,
> On Thu, Oct 7, 2010 at 1:19 PM, Luis Muniz <neur0maner@gmail.com> wrote:
> > On Thu, Oct 7, 2010 at 11:47 AM, Jukka Zitting <jukka.zitting@gmail.com
> >wrote:
> >> On Thu, Oct 7, 2010 at 11:44 AM, Luis Muniz <neur0maner@gmail.com>
> wrote:
> >> > We are using jackrabbit-1.5.6, should we think about upgrading?
> >> Yes.
> > Why?
> You're one major and two minor releases behind the latest Jackrabbit
> version, which means that the likelihood of any issues you encounter
> being already fixed in a more recent release is pretty high.
> I'd love to help you track down and fix the problem if it still occurs
> after an upgrade, as doing so will help prevent me or the customers of
> my employer from encountering the same issue in the future. But
> chasing down an old problem that's most likely already fixed in a more
> recent version would probably just be a waste of time from my
> perspective.
> There may be other people on this list who may want to help you even
> with 1.5.6 and you can always turn to paid support, but upgrading to a
> more recent version is a cheap way to either get rid of the problem
> automatically or at least notably increase the motivation of other
> people to help you.
> That said, you may want to check the Jackrabbit issue tracker for the
> list of known and resolved deadlock issues [1]. Also, without a thread
> dump it's usually quite hard to determine the cause of a deadlock.
> [1]
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&query=deadlock&summary=true&description=true&body=true&pid=10591
> BR,
> Jukka Zitting

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message