[Simpleweb-Support] Simple Stability...
Brought to you by:
niallg
|
From: Gail R. F. <ga...@sc...> - 2005-08-09 19:12:40
|
Hi Niall and everyone, As you know, I have been testing Simple for the past few weeks, trying = to track down a TCP error that was causing my instance to eventually hang = all worker threads, even under light loads. I previously suggested a tweak to the Socket configuration (setting a SO_LINGER timeout).=20 In the end, we found spotty documentation about a Linux 2.4.x kernel bug that can cause sockets closed properly by the application to linger indefinitely in CLOSE_WAIT. Updating our Red Hat distribution via Red = Hat Network (we paid for this service) resulted in the problem completely = going away.=20 I was more than surprised to find an OS bug to be at fault! Along the way, I replaced Niall's synchronization and thread-pooling = code with the new JDK 5 constructs from the new and wonderful package java.util.concurrent. I proved that Niall's software was correct = (because we saw the same deadlocks with the JDK 5 constructs, which have already = been proven correct). But, the migration to java.util.concurrent seems to = make a faster Simple. I'm happy to contribute back the port to java.util.concurrent, it = simplifies the code... -- Gail. ------------- Gail Rahn Frederick ga...@sc... 503.260.0910 |