I'm wondering if this is the great
FileUrlConnection.getLastModified()
leak?
Or in fact any of the FileUrlConnection related leaks
-Stephen
2008/11/5 <glassfish_at_javadesktop.org>
> I can't say anything about the Sockets used in the app server code itself.
> Which is the main reason for my post.
>
> Our code does use some non-blocking sockets (java.nio.channels package).
> We do detect when the remote ends just disconnects and we do clean up after
> ourselves.
>
> We've watched the file descriptor directory as our sockets are created and
> then destroyed and have been able to prove to ourselves that its not our
> application sockets causing the leak.
>
> We think the app server is the culprit somewhere down in the "bowels" of
> the CORBA protocol stack. We're getting ready to try our app on Apache
> Geronimo to see if its any different.
> [Message sent by forum member 'snewbold' (snewbold)]
>
> http://forums.java.net/jive/thread.jspa?messageID=315101
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>