There are comments/code in this file about getting synchonization on
page 0.  I went through the comments in the file and in the derby issue
and my understanding is that the problem is caused by the behavior on
windows where the use of a channel affects the current position of the
file that the channel is based off of.  The case in point is one thread
using non-channel code to operate on page 0 while another thread is
using channel code.

What I am missing is why the problem is limited to channel code on page
0?  What stops the case of non-channel code operating on page 0 while
channel code is operating on another page and affecting the non-channel
page 0 operation?

I considered doing the work to just get rid of the non-channel code, but
small platform environments including foundation 1.0, 1.1 and 1.1.2 don't support nio.

Reply via email to