Quick question on AREmail Java process
We are seeing a problem where the arserverd appears to be exerting the proper level of control over the tcp keepalive setting for the connections between itself and the AREmail preprocessor, as well as the DB connections. The AREmail java preprocessor, on the other hand, does not appear to be applying any kind of tcp keepalive to the front-side connections - IE those coming in to it from the web tier servers or directly from user clients. Because the front-end process is failing to apply a tcp keepalive to the incoming connections, it has no way of knowing if the client is still there or not. Thus the 3900 sockets open to the AREmail processes, which then replicates those connections back to the arserverd for another 3900 sockets. There are a total of more than 7800 sockets open between those two functions. Any ideas? [Description: Description: Description: cid:image001.png@01CB1CFE.724B27B0] IT Accounts & ITSM Applications Manager University of New Hampshire Client Services Primary: (603) 862-2377 Alternate: (603) 862-4242 paul.hodg...@unh.edu<mailto:paul.hodg...@unh.edu> http://accounts.unh.edu<http://accounts.unh.edu/> _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
