NumberFormatException constantly generated by LS Client library

[rsouissi]

Dear all,

Something I noticed a while ago but only now I am writing about it.
I seems that the j2me client library is internally testing a string being a number by using Integer.parseInt(). This generates a lot of NumberFormatException logging in J2ME emulator when exception tracing is enabled.
This does not cause the code to fail as I believe this is as designed, but performance wise, I don't think this is the best way to test if a string is a number.
Exceptions are known to be performance killers in Java and usually should not be used to handle normal cases. In J2ME, I have a feeling it is causing some pauses in the application.

Regards,
A

[Mone]

Hi,
You're right about exceptions but we don't feel this as a big issue since cases of non-number parsed with parseInt appear only few times per each connection (create_session.txt and bind_session.txt).
In any case we're going to change that piece of code in a future release.

About the pause, is it possible that pauses are caused after onBufferFull calls?

[rsouissi]

Actually in my case, it happens much more frequently. Between once every 2 sec to several times every sec.
I capture onBufferFull events and log them but it does not happen.
I used the very latest MIDP 2.0 client.

Regards,
A

[Mone]

Hi rsouissi,

sorry for the long delay, we've ready a build of the J2ME client that fixes the problem.
That build will be available on the next release (that should be at the end of august) but if you want to preview it just send an email to support@lightstreamer.com .