On Sat, Nov 19, 2005 at 01:08:02AM -0000, Kevin Walsh wrote: > Mod_interchange will remain connected to Interchange until Interchange > closes the socket at its end. Or until the apache hard timeout is reached, IIRC. Although mod_ic might not be the culprit on this issue, it could mitigate the issue. It's clearly "stuck" somewhere waiting for something to happen. Maybe at connect? Would it make sense to set up a hard timeout at the beginning of mod_ic's code path and kill it at the end? The current code only sets timeouts during RX, TX, and select but not during connect. In the end, it seems like mod_ic's entire exchange with IC should not exceed apache's hard timeout value and I don't believe that the current code ensures this. Jeff _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.