Re: WO bug fixes

That's it! I have retracted my bug report. I was indeed being confused by a 
long EOF fetch with prefetching that blocks other activity. Multithreading 
is certainly working very effectively in my JC app I have established. In 
this case I will look at optimising the query. Thank you.

At 21:02 02/08/2005, Chuck Hill wrote:

>On Aug 2, 2005, at 12:37 PM, John Pollard wrote:
>
>>Thanks Chuck, I expect some of the bugs I reported were fixed but the 
>>cases not marked as closed. I am hoping for concurrent processing of 
>>requests from different sessions, not within the same session. I did have 
>>it working some time ago as I got some strange effects of mixed data 
>>before I synchronized certain sections of code. Now the settings seem to 
>>be ignored by WO as a second short JC request (different session) always 
>>queues up behind the greedy long one. Come on everyone, use this great JC 
>>technology and demand concurrency!
>I'm still not quite following.  Is it getting blocked behind a greedy EOF 
>request?  EOF is single threaded so concurrency is not likely to happen 
>there.  As soon as one thread locks the EOObjectStoreCoordinator, all 
>other thread have to wait for _any_ EOF access.
>
>
>Chuck