Terracotta Discussion Forums

Hi,

I keep seeing a deadlock when I use terracotta.

I have attached the relevant bit of the stack trace and my terracotta config file.

Ive still not been able to determine the exact conditions under which the deadlock occurs, but i think it only occurs when the app has been restarted but the terracotta server remained up and running.

Any help or ideas to what might cause it would be helpful.

Thanks,

Richard

Hi Richard,

What version of Terracotta are you using? From your log it looks like v 2.6?

Fyi, In TC 2.6 you can use the Admin console to get a single cluster-wide thread dump.

Scott

This is definitely a Terracotta bug, I've created a JIRA issue for it here:
http://jira.terracotta.org/jira//browse/CDV-771

Hi,

Yes we are using 2.6, but I also saw this bug in 2.5.4.

Thanks

Hi again,

Fyi, we have fixed this in trunk, revision 8706.

That was quick :)

Presumably the trunk build is safe for me to use in production?

Thanks,

Richard

No, I wouldn't recommend using the trunk build in production, unless you really really want to :) The nightly build isn't as rigorously tested as the release builds. If I were you I would just get the change for revision 8706 (which is confined to a single class) and either rebuild 2.6 or just build a patch from the changed class (the class API didn't change so you can safely do that in this case). That patch would need to go in the classpath in front of tc.jar.

We are discussing rolling this and other changes into a 2.6.x patch release, but unfortunately I don't know yet when that will happen. As soon as I know I'll post something here.

Let me know if you run into trouble and I'll see what we can do on my end.

Here's a couple links that may be helpful:
Terracotta source repository
building and kitting Terracotta from source

Hi again Richard,

We have merged the fix into the 2.6 branch, which means if you want you can use the nightly build from that branch, starting tonight. Tonight's nightly build should contain the fix you need, and is nearly identical to the 2.6.1 release build (which is just about to be released but doesn't contain your fix). So it's a much safer bet than using the trunk nightly build.

Check out our download page. Links and RSS feed for 2.6 nightly builds should be available sometime within the next day.

what minimum revision # for the 2.6 nightly builds will contain this fix?

revision # 8726

The nightly does indeed fix the problem, and also seems to have fixed the problem I was having in this thread http://forums.terracotta.org/forums/posts/list/0/1112.page#6739

When do you think the 2.6.2 final will be released?

Thanks alot for the quick replies and fixes,.

Richard

Hi Richard,

Glad to hear it!

Our project manager estimates approx 4 weeks to 2.6.2.

Scott