-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
java.lang.NumberFormatException Invalid long: "�" #30
Comments
Hi Farzad, can you provide a test case that reproduces this? Thanks! |
Hi Larry, It just happened once on a Samsung S5, Android 5.0 and this stack trace is the only thing I have got about it. |
We still receiving this issue. last night from Android 5.1, Galaxy J1 Ace (j1acevelte) java.lang.NumberFormatException: Invalid long: "�" |
this issue is going to be a big problem for us on Android devices. do you have any plan to fix it out in a short term?
|
Can you provide the version/snapshot of the API are you using? |
it's 0.3.1. Because of incompatibility with Android devices I can not use newer version of jnats. |
…om killing the client. On parse exceptions, the client will disconnect, and reconnect if reconnect is possible. Resolves #30
thank you.
|
@remotegun This does not create a jar file. It installs the NATS parent pom.xml in your local M2 repo. |
Also make sure you do:
|
@aricart The repo that @remotegun was executing |
Please note my revised comment. |
@mcqueary is correct. |
@remotegun I am taking @aricart |
that would be great @mcqueary! |
This has been fixed in release 0.3.2. Need to verify whether it's still an issue in 0.5.1. |
great! thank you |
I'm going to go ahead and close this. Please reopen if 0.3.2 doesn't solve the problem. |
…om killing the client. On parse exceptions, the client will disconnect, and reconnect if reconnect is possible. Resolves #30
This seems to have occurred in jnats 1.0 on android. Reopening this issue. |
Can you try 2.0 and see if you can reproduce. The only place the new library parses numbers is for ids and lengths in the protocol strings. if these are invalid then there was a data problem coming on the socket. However, it is possible that the issue had to do with buffering, so it may be fixed in the new code. |
Closing for now, please reopen if you see this again. |
Today I got this error:
The text was updated successfully, but these errors were encountered: