[Logo] JCVSForum - Community Support For JCVS Users and Developers
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Deadlock on Update Bug in jCVS 5.4.2  XML
Forum Index » JCVS Users
Author Message
Anonymous



I am constantly seeing deadlocks when trying to "update all files" on
SPARC/Solaris or Linux. It seems to be sensitive to the number of files that are
out-of-date -- the more files, the more likely I am to see a deadlock. My take,
just from looking at the stack trace, is that having the "update" thread lock
the ProjectFrame (probably a JFrame, and therefore a Component) is asking for
such trouble. Code within ProjectFrame that must be synchronized should use a
private, internal lock object instead.

The other developers here seem to have it working fine on Windows, but they
might be running an older release of jCVS. I'm using Java 1.4.2_04 and jCVS
5.4.2. I've also seen it in 5.4.1. The Solaris system is running Solaris 9, the
Linux box is on Java Desktop System release 2. The SPARC is a dual-processor
box, but the Intel box is a single. Any suggestions for a work-around, or a
recommendation for an older version of jCVS that doesn't have this bug?

The stack trace of the deadlock is:


Anonymous



Wow! Thanks for reporting this bug. I never really thought about that
synchronized method, but it makes sense that it is not a good lock to acquire,
even if it is only for a very short time. I will fix this in the next release. I
wonder if this might explain other "inexplicable" bugs that have been reported
over the years?!
time


[Avatar]

Joined: 05/06/2004 18:09:23
Messages: 367
Location: Bangkok
Offline

I hope to post a new release to fix this soon.
[Email] [WWW]
 
Forum Index » JCVS Users
Go to:   
Powered by JForum 2.1.9 © JForum Team