×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Dan Kimmel wrote:
You could have a race condition on a multiprocessor machine. The
dataqueue monitorThread is doing something in processEntry() when the
interrupting thread hits the join.
That's not something I specifically thought of ... but I don't think it's the case.
This seems to happen (at least on this customers box) very consistently ... even when the application that's listening to the data queue is doing nothing. The only time the processEntry() method would be invoked is if there were an entry received from the data queue.
If the application were more active, I would say it's a possibility.
We had the customer move the application to a PC, instead of running it on the iSeries, as a workaround ... and it seems to be working OK.
I've also sent them a patch that will change the data queue timeout from -1 (forever) to 15 seconds. Also, instead of looping forever and hoping for a InterruptedException, I'm controlling the loop based on the thread's isInterrupted() method.
david
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
