According to jdbc javadoc Statement.close simply releases resources without waiting for them to be closed automatically.
And good behaving libs in java look for their external resources allocated. The application may have problems. Last leak I've seen was something like this.getClass().getResourceAsStream(...) != null. But this was traceable because one could find unclosed streams in heap dump.
What is proposed here is server side leak that will be invisible while analyzing application. I can't afford using such a lib in my projects.
23 жовт. 2013 04:04, користувач "Dave Cramer" <
pg@fastcrypt.com> написав:
That's rather harsh. How do you see this as introducing a server side leak ? Statements are supposed to be closed by applications as are connections.
