Hello, I found few related threads on this topic in archives that are ~ 1 year old, but didn't find the answer to my question.
We are using Xerces 1.5.1 on Solaris 8. DOM Tree is constructed when the process is initialised. After the tree is constructed, multiple threads access it only for read. No writes/updates to DOM tree during the life time of our process. Is DOM tree thread safe for reads? I do get cores in DOM parser code, if I let multiple threads access it. It doesn't core if just one thread is accessing it. I came across a thread on xerces' 'lazy evaluation' of the tree. Is there any option to turn it off? Is DOM tree thread safe with 'lazy evaluation' option turned off? I've also tested with xerces 1.6.0 without any luck. Having multiple instances of DOM tree or synchronising the access to DOM tree will have a huge impact on the performance of the system. I would prefer to avoid these options. Thanks in advance regards Raju --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
