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

On 8/20/13 11:08 PM, Scott Klement wrote:

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);

Or, you could put in an IF statement to have it only run these under
certain circumstances, or whatever works best for you.

Fascinating. Thanks.

I think I'll probably just get rid of the sleep(10), and redirect the output the way I'd been doing. The sleep(10) doesn't really help much when the call stack is too big to fit on one screen in its entirety, and the stack trace doesn't really help much when the exception is from, say, the user trying to sign on to a server with a bad password.

Definitely nice to know why it sits there without doing anything for as long as it does. Didn't know it was doing so by design, with something I could easily get rid of.

--
JHHL