Re: Has something changed that would affect connect performance ?
Posted by: Mark Matthews
Date: November 23, 2004 11:45AM

Found the issue.

We intentionally disable our use of BufferedInputStreams, because they aren't always safe to use with non fixed-packet-length protocols (MySQL being one of those), due to a 'feature' that many actually classify as a bug (see the CHANGES file for a reference to the bug parade entry).

It was actually a regression in 3.0.15 that BufferedInputStreams were enabled by default...if they work for you (and they do in most cases, but cause strange hangs for other people depending on JDK and OS versions), then just add the connection property 'useUnbufferedInput=false' to your JDBC url, and you should be back to the performance you were seeing with 3.0.15.

We're looking at implementing our own buffered input stream solution, but for now we let people decide 'fast' vs 'safe'.

Options: ReplyQuote

Written By
Re: Has something changed that would affect connect performance ?
November 23, 2004 11:45AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.