Re: If a Java function seems to never return, how do I test?

Any chance the thing being thrown was not an Exception, but still a Throwable? e.g. AssertionError would behave in the way you've described here, unless I'm missing some detail - https://docs.oracle.com/javase/7/docs/api/java/lang/AssertionError.html -- You received this message because you

Re: If a Java function seems to never return, how do I test?

> flush twice, oracle is far far away? Are you saying this is so obvious I should be able to easily look it up? It might be obvious to you, but it is not obvious to me. That's why I'm asking. On Monday, November 2, 2015 at 3:25:36 PM UTC-5, raould wrote: > > flush twice, oracle is far

Re: If a Java function seems to never return, how do I test?

Possible. I have not dug into the Java app, but I will look for that. On Monday, November 2, 2015 at 4:48:38 PM UTC-5, Rob Lally wrote: > > Is it possible that the exception is being thrown in a different thread? > If that’s the case, you can use: > > >

Re: If a Java function seems to never return, how do I test?

> It is possible to rebind System.out to something else inside Java, so the > library could be redirecting it from your view. Not saying that's > happening, but it's possible. Thanks for this. Now that you mention it, I recall some conversation about this over the summer. I will investigate

Re: If a Java function seems to never return, how do I test?

It is possible to rebind System.out to something else inside Java, so the library could be redirecting it from your view. Not saying that's happening, but it's possible. If you you can connect with a debugger, you can set breakpoints based on any thrown exception. On Monday, November 2, 2015

Re: If a Java function seems to never return, how do I test?

flush twice, oracle is far far away? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To

Re: If a Java function seems to never return, how do I test?

Now there is a new error. Somehow, when the exception happens in our Java library, even though we, in theory, write to System.out.println(), I never see the Exception in the logs. All I can think is that somewhere in the Java library there is an exception that we catch but we forget to do

Re: If a Java function seems to never return, how do I test?

Is it possible that the exception is being thrown in a different thread? If that’s the case, you can use: https://docs.oracle.com/javase/7/docs/api/java/lang/Thread.UncaughtExceptionHandler.html to

Re: If a Java function seems to never return, how do I test?

So, we eventually fixed this. There were 2 bugs that worked together to make this a mystery. I had to guess at what the problems were, and fix them blind, since I could not see the Exceptions. I am curious about why I was not able to see the Exceptions. About this: > Exceptions are ALWAYS

Re: If a Java function seems to never return, how do I test?

> > > What could we do to make the Exception visible, assuming there is one? > > Exceptions are ALWAYS visible, the only way they get lost is the try/catch blocks you added in your code which effectively swallow and ignore them. The JVM will not randomly lose an Exception, it is always code

If a Java function seems to never return, how do I test?

I am trying to figure out where this code might die, and why we don't se the Exception, if there is an Exception. Inside of a try/catch block, we have this, when calls a library written in Java: (timbre/log :trace " in parse-sentence fields-and-labels is: " fields-and-labels) (let [