Re: Threads problem in Java on i5

I got to the bottom of this. I took a look at the JTOpen source code for the native implementation of DataQueue and although the Read method says that it throws thread interupted exception, it never actually throws it nor does it check for interruption.

Anyway I got round this by setting setMustUseSockets(true), not ideal but it solves the problem.

---- Original message ----

Date: Fri, 14 Nov 2008 00:42:22 +0100
From: java400-l-bounces@xxxxxxxxxxxx (on behalf of Thorbjørn Ravn Andersen <ravn@xxxxxxxxxx>)
Subject: Re: Threads problem in Java on i5
To: Java Programming on and around the iSeries / AS400 <java400-l@xxxxxxxxxxxx>

Neill.Harper@xxxxxxxx skrev:

Your right the exception is ignored, but I'm not even getting the chance to ignore it on the i5. In WDSC the exception is ignored and the next iteration of the loop checks a close down flag and shuts the server down.

Some googling has suggested that certain JVM's also don't throw InterruptionExceptions in certain circumstances (when they should), Reading from standard input etc...

I think I am going to have to forget interruption and do something a bit more drastic to get the servers attention.... :)

Which JVM are you using? The Classic and non-Classic JVM's may show
different behaviours in this area...
--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.