Well, that clinches it. The *exact* same code with the threading pulled out (so now the xml files are processed sequentially, not parallel) and the memory problems disappear (the crude method of watching the memory allocation in windows task manager shows a slight uptick, but no where near to hitting the wall of the java heap size). On a whim I also pulled out the extra check for the xmlChildren size. Guess what? The unexplainable indexing error is gone now too.
Of course, processing things will take longer - one file has to wait for the other to finish. But considering I've wasted a day chasing unexplainable ghost problems caused by threading, I'll have to figure out some other processing method to speed things up. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:327536 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
