New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oracle JDBC issue on Linux - IO Error: Connection reset #1077
Comments
I ran into problems with Connection Reset towards Oracle, and this option actually makes a big difference... My builds actually runs in less than 5 seconds where it would often fail after the first call to flyway. Ie. if I did a flyway:info this would run OK once, but then the following flyway runs will fail with connection reset... Connecting to Oracle with ie. SQLDeveloper works fine, so it is not a DB issue. Apparently it is an issue in Java: http://stackoverflow.com/questions/137212/how-to-solve-performance-problem-with-java-securerandom |
Yes. The entropy problem exists on Linux. Which os are you running on?
|
I'm running on Ubuntu 14.04 LTS running on VMWare. I found a nice explanation here: http://www.usn-it.de/index.php/2009/02/20/oracle-11g-jdbc-driver-hangs-blocked-by-devrandom-entropy-pool-empty/ It would be nice to have this option inside flyway property file or something instead ;-) |
There you go. I recommend installing the package haveged which fills dev
|
Fixed. |
when I use more than 2 connections to get Oracle data by Flink JDBCInputFormatBuilder, it will throw Connection reset exception. I add |
The Oracle JDBC driver has a known issue on some linux systems. When using flyway, it manifests itself as an intermittent failure with the message:
The problem can be fixed by starting Java with the following JVM param:
To fix it on my system, I replaced this line in the flyway script:
With this one:
Do you think it would be worth adding a feature to flyway to allow JVM params to be passed in as a setting, without having to modify the original flyway file?
The text was updated successfully, but these errors were encountered: