2011/6/29 Igor Podolskiy <[email protected]>: > like with all Java applications: it is _always_ the class path :D Judging > from the stack trace and the classes involved, you have two Xerces jars > somewhere. I can think at least of two possible constellations:
At first I thought that the problem in two Xerces jars. But in this case, the same command in my environment should give same result, because the set of loaded plugins depend only on command. In my case, the same command succeeds with the second attempt. This is very similar to the bugs arising from incorrect thread synchronization. Perhaps the two threads simultaneously attempt to load Xerces.. It seems to me there is some dependence on the current system load. At load average = 5 chance encounter with this error greater than at load average = 0.5 _______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
