Bugzilla – Bug 3828
RLSClient crashes when a null parameter is passed to a method
Last modified: 2008-01-29 22:23:40
You need to
before you can comment on or make changes to this bug.
The RLSClient accepts null parameters and passes them to the RLS JNI calls.
The JNI calls invoke JDK JNI library routines without checking for null
parameters. It appears that the JNI lib routines crash when passed null
We need to check for null parameters, preferably in the Java portion of the
RLSClient, and throw exceptions rather than passing through to the JNI portion
of the code.
This bug is fixed by the new RLS Client Java API in trunk (to be released in GT