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
Driver throws NumberFormatException when used with 9.4 beta1 #90
Comments
Hi Andreas, This is a known limitation. I have to extract this commit (in fact, this code has changed but it's just a one liner to fix): I have a couple of things to do so I'll see about extracting this one from the original pull request and submit another one. |
Thanks! |
BTW; The real error was kind of hard to spot as the NFE is masked and the real NFE.message never gets out in the log. Maybe changin so that becomes: ? Then the NFE won't get masked. As it stands e.getCause() returns null so the NFE never propagates. |
IIRC, there's something to fix that in the original PR and it should be See my post here: #85 On Thu, Jul 3, 2014 at 11:13 AM, Andreas Joseph Krogh <
|
Right, it's there. |
Nothing. There's just some work to merge it due to the recent changes. I'll prepare a clean PR for Kevin or Brett to merge it directly. Hopefully On Thu, Jul 3, 2014 at 11:35 AM, Andreas Joseph Krogh <
|
Done: #91 |
Get this exception:
java.lang.NumberFormatException: For input string: "4beta1"
But the exception is masked in IOException:
ProtocolFactoryImpl:288
io = new IOException(e.getCause());
The real NFE-stack-trace is:
But the Exception in the logs is:
The text was updated successfully, but these errors were encountered: