OK, now we are getting somewhere. Why is there is established connection hanging around even after 5-10 mins?
java 3610 root 8u IPv6 15008 TCP 192.168.2.15:webcache->18.104.22.168.kmr02-home.net.my:55006 (ESTABLISHED)
Now, three more things:
- Find out what exactly that connection stands for. AFAICT, it seems to be "socket" opened by the server as part of "accept()" but just make sure it isn't something else again by talking with your admin.
- Do the same test, but with continuous 10/20 clients. Make sure you *restart* the server before beginning the test. If after the test we have around 10-20 established connections lying around after 10 minutes, we would be damn sure it *is* a leak.
- If the above step shows a leak, close everything in your last "finally" statement. By everything, I mean the 'r', 'w' & 'socketConn1'. This isn't a very big change and is required because there isn't much correctness check we can do in this small code except close all open resources (which isn't happening now)
Edited by ~s.o.s~: n/a