Bug ID: JDK-6519688 DNS provider does not cleanup resources properly

Type: Bug
Component: core-libs
Sub-Component: javax.naming
Affected Version: 5.0u4

Priority: P2
Status: Closed
Resolution: Duplicate
OS: solaris_10
CPU: sparc

Submitted: 2007-01-31
Updated: 2010-04-03
Resolved: 2007-03-26

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

Other
5.0u4Resolved

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).