On 31/12/2011 13:38, Janne Jalkanen wrote: >> Which Connector are you using? > > <Connector port="8080" protocol="HTTP/1.1" > connectionTimeout="20000" > redirectPort="8443" > URIEncoding="UTF-8" > compression="on" > > compressableMimeType="text/html,text/plain,text/css,text/javascript,application/json,application/javascript" > noCompressionUserAgents=".*MSIE 6.*"/> > > >> What is the minimum that is required to reproduce the issue? > > Wish I knew. This is from our production cluster, so I'm a bit hesitant to > start experimenting with it. However, there was no configuration change > between 7.0.20 and 7.0.23, I just shut down tomcat, unpacked the 7.0.23 > tar.gz, changed symlink to point at the new binaries, and restarted. > >> >> >>> lsof says >> >> Did you supply any options to lsof? > > lsof -nP -u ubuntu|grep 21299|grep "identify protocol" > >> Are you using RMI for anything in your application or is this a >> reference to the JMX connection? > > I am using RMI only for JMX monitoring. The socket exception times *do* > roughly correspond to Munin contacting my application every five minutes for > getting monitoring data, which is logical because they would be requiring a > set of new file handles.
When did the problem start occurring and what else has changed? Can you stop monitoring with Munin and see if the problem goes away? If it does, I would consider that Munin may not be properly closing the connections it makes. p > Ah yes, I also have Terracotta session clustering configured using their > Valve. That might be using RMI, but I would be expecting to see a lot more > errors in that case. > > /Janne > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
