Re: Suppressing call stacks when RPG call to Java throws Java exception

On 8/21/2013 2:08 AM, Scott Klement wrote:

James,

Assuming this is occurring in JDBCR4, you can eliminate the stack trace
and the 10 second pause by commenting-out these two lines of code in the
jni_checkError() subprocedure of JDBCR4:

ExceptionDescribe(JNIENV_P);
sleep(10);

-snip-

But, by all means, remove them if you don't like them.

Hard-won personal experience speaking here: Don't delete these lines.
Condition them on a debug data area or an external indicator or a
parameter or something that you can have the client change in order to
surface the debug information.

Even better would be to keep a log in a stream file which your app can
email to you when the user authorises sending debug information back to
you. I don't know how to redirect the Java stack trace yet, but I
intend to learn.
--buck

On 8/20/2013 12:52 PM, Barbara Morris wrote:

On 8/19/2013 8:27 PM, James H. H. Lampert wrote:

Is there a way to suppress the call stack entirely, and avoid the long
pause?

Are you using the QIBM_RPG_JAVA_EXCP_TRACE environment variable to
enable the stack trace? Unlike other Java-related environment variables
that are only checked at JVM startup, the RPG runtime checks that one
for every Java method call that gets an exception.