There is a new version for the Postgresql JDBC 3 driver.
I inluded a workaround bugfix (see:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5092063 for details), which
occurs only in the 1.5 JDK. _But_ the change eliminates the useage of Proxyes.
So if you apply this patch than you cant be able to connect via a SOCKS (or
another type) proxy!!
Steps to Reproduce:
Created attachment 68132 [details]
jdbc3-postgresql-8.0_p312.ebuild -- the ebuild file for the 8.0_p312 version
Created attachment 68133 [details, diff]
jdk1.5_socket_workaround.patch -- the patch file
version bumped too 312, will not include the workaround
I added a ned USE flag for the patch, so it dont hurt anybody.
The new USE flag name is jdk1.5_socket_workaround.
In servers this is a very big problem, on my machine it takes 20 more seconds
to establish the connection from the tomcat machine to the postgresql server
machine. And my patch (you can see) does the same thing as the original code,
just eliminates the proxy connection.
Please, think it again, please!
(In reply to comment #6)
> Please, think it again, please!
> thank you!
We don't want to maintain patches if at all possible. Please submit this
upstream. When they release a new version it will be included in our packages.
this is a bug just in the 1.5 version of JDK.
hmm, may you add a comment for the package?
"if you are experiencing unexpected slowdown
building up connections with Java 1.5, see
infos and a workaround patch here:
1.5 is not officially supported yet, but axxo can add the warning to the 1.5
overlay I think so it will hit the official tree after 1.5 is unmasked. Please,
do not add devs to CC because we already recieve mail sent to email@example.com.
Applied here. See http://bugs.gentoo.org/show_bug.cgi?id=65937#c30 for more info.