-
Bug
-
Resolution: Duplicate
-
P2
-
5.0u4
-
None
-
sparc
-
solaris_10
Short description: com.sun.jndi.dns.DnsContext.close() doesn't work
After starting the program(find the program attached as SocketLeak1.java), run "truss -t so_socket,close -p <pid>" on the Java process that is just started.
Please find the attached results in the file called "truss_new". As you can see, there are a lot of sockets opened, and then closed. But they are closed by the garbage
collector, not by the calls to "close()" in the code. A correct
behavior would show up in the truss log as open/close/open/close/open/close, maybe something like the "truss2" file (the expected behaviour from the customer).
After starting the program(find the program attached as SocketLeak1.java), run "truss -t so_socket,close -p <pid>" on the Java process that is just started.
Please find the attached results in the file called "truss_new". As you can see, there are a lot of sockets opened, and then closed. But they are closed by the garbage
collector, not by the calls to "close()" in the code. A correct
behavior would show up in the truss log as open/close/open/close/open/close, maybe something like the "truss2" file (the expected behaviour from the customer).
- duplicates
-
JDK-5053708 DNS provider does not cleanup resources properly
- Resolved