|
From: David K. <dav...@al...> - 2003-11-04 19:26:22
|
Hi Bruce! McDonald, Bruce wrote: > Another data point... Great! (Well, I am happy to see that the problem wasn't only occuring in my own setup, since I would then be even *more* stumped than I am currently. :-) Now that the problem has been confirmed elsewhere I feel much better about the whole thing. Then again, I feel sorry for causing a delay in the 1.2 release. Oh, well, the things is pretty serious...) > If I synchronize the getConfig methods on the ConfigService class (as opposed to the internal synchronization) then I can run the scanner > with only the first and second group (each group has 4 files) of data files causing an exception. All subsequent runs are perfect. Hmm. How many threads are doing work in the subsequent runs? > go figure... Indeed... As an added data point (not exactly new, but anyway), I can have the problem occur in a multi-pipeline setup as well, in which I have two pipelines doing initial processing for two separate incoming data-sources, and when done they both call a third pipeline for common processing. I have had the crash occur in the third, common, pipeline. So, the problem travels across Call-stages as well. FWIW. I am available (during Swedish working hours, at least) for running more or less whatever tests anybody can come up with that are worth running, if it helps. I can do and test code changes as well, as long as I can grasp what they intend to do. :-) Right now, I feel that I have put in synchronization both here and there to no avail, so I am *obviously* missing the target. Hints to get me on the right track are welcome! > Bruce. /David |