tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46384] Due to missing synchronization, a member may disappear permanent.
Date Fri, 17 Apr 2009 03:58:20 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46384





--- Comment #3 from Filip Hanik <fhanik@apache.org>  2009-04-16 20:58:18 PST ---
(In reply to comment #1)
> Created an attachment (id=23501)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23501) [details]
> Patch to fix this issue
> 
> The attached patch should fix this although I haven't tested it.

I don't think that patch will fix it. The key problem here is that if the
sender thread gets locked up, it will stop broadcast the member itself, and
other nodes will deem it gone.

The only solution here is to not lock up the sender thread ever. The same goes
for the receiver thread. 

The code is a bit of a sync spaghetti mess, but Tomcat 6.0 has the fix for
this, that will prevent it from locking up these two threads.

TC 6 also has secondary verification mechanism, that are unrelated to this.

You'd be better off backporting the fix from Tomcat 6 to Tomcat 5

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message