It is because of how my implementation is, instead of locking on a RPC call I call out for replicated data in a async manner. You have a very valid point, and it is a valid problem.
I will fix when time permits :) - the fix is to implement RPC instead of async request-reply between nodes. This has been tricky because of how flaky the NIO implementations are in the current available VMs. I might even switch back to java.io instead of java.nio, because so far, I have not seen a good NIO implementation out there. And yes, if you want to look at source, take a look at T5, since the backport for T4 is not pretty and will get you pretty confused :) Filip ----- Original Message ----- From: "David Rees" <[EMAIL PROTECTED]> To: "Filip Hanik" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, September 11, 2003 1:49 PM Subject: Re: Tomcat 4 Replication problems Hi Filip, Filip Hanik said: > > The replication in T4 is a back port, hence it doesn't have the > capabilities to delay the startup of tomcat in any other way than putting > a sleep on the start thread. Is this because of of the way TC4 is designed or because of the nature of the backport? Just trying to get an idea of where to start looking if I get the itch to see if it's fixable the proper way for TC4. Am I right in assuming that TC5 handles this issue properly? Maybe it's time to start testing TC5 instead... -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
