summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGurmeen Bindra <gurmeen.bindra@isode.com>2012-08-16 09:53:11 (GMT)
committerKevin Smith <git@kismith.co.uk>2012-08-16 10:07:01 (GMT)
commita22d6c1c23f06bb4dbc8b5c72177ebf27b239482 (patch)
tree30818f83b43b7b66f877c65b88939d3a60aa3fd9 /Makefile
parent8568b7b74fe962bf6d3252e9967aa3123968615c (diff)
downloadstroke-a22d6c1c23f06bb4dbc8b5c72177ebf27b239482.zip
stroke-a22d6c1c23f06bb4dbc8b5c72177ebf27b239482.tar.bz2
Close DirectoryContext after receiving results
If I leave an Application using Stroke running for a few hours(making periodic connection attempts), the JVM would throw an Exception saying "Too Many Open Files". On doing an "lsof -p <pid_of_jvm>", I noticed that there were number of open sockets in CLOSE_WAIT state and these went up after every attempt to do a connect on CoreClient object. Closing of DirContext object fixes this bug and the number of open sockets does not increase. Test-information: Ran MLC and kept on monitoring the result of "lsof -p <pid>". It would not increase after this patch.
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions