Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Error handling for sync invocations in Java
01-12-2011, 01:03 PM
Post: #14
RE: Error handling for sync invocations in Java
(01-12-2011 11:53 AM)simoncn Wrote:  I'd be very surprised if this failure were in my main app thread, as this thread is just sitting idle when my application has completed its startup. I'll install Visual Studio on the test server to find out which thread is running at the time of the abort.

Sorry, you're right, this is happening in a thread that is created by the OS abstraction layer and is used to monitor changes in available network adapters. It'll be much simpler to get the call stack printed now.

(01-12-2011 11:53 AM)simoncn Wrote:  When you say that I would need to catch exceptions in my app thread(s), are you referring to Java exceptions or C++ exceptions? There's no problem if it's Java exceptions. If it's C++ exceptions, the ohNet JNI code would need to catch these and rethrow them as Java exceptions so that I could catch them in my app.

Good point. I can probably catch and deal with any unexpected exceptions in the C bindings, saving the need to do anything in managed code.
Find all posts by this user

Messages In This Thread
RE: Error handling for sync invocations in Java - simonc - 01-12-2011 01:03 PM

Forum Jump: