Search results for query: *

Maybe. I have been running my same code on Windows and have not come across this problem (doesn't mean it's not there as well, I am not pushing it as hard, mostly using it for unit testing and debugging). Glad to hear yours has been running flawlessly, there is hope for me ;) Thanks for your...

>>>> The MQ pooling and multi-threaded message handling was >>>> in place before I came across the problem. >>Then i would consider that highly suspect. If you isolate >>your use of Xerces and execute that isolated code in an >>automated fashion without reproducing the problem then >>the...

idarke, I'll try synchronizing with Xerces and see what turns up--unfortunately I don't have a predictable way to reproduce the problem yet, so it will be tough to tell if it's a cure or not :) pete, I only meant that the code starting another process w/ Runtime.exec() was new. The MQ...

Pete, The application is multithreaded. There is MQ Connection Pooling (so a thread for each MQ connection) and also a thread is started to handle each message on the queue. Each of the message handler threads creates its own instance of the XML parsing logic. In some cases, this thread...

Hi all, I tried this post in the XML forum, but it was suggested I try the java forum instead...so here goes... I have an application which is using Xerces parser for XML parsing. Most of the time, I have no problems. However, occasionally, at the point I am creating the new DocumentBuilder...

Hi all, I'm not sure if this a place for java XML questions, but hopefully it is. I have an application which is using Xerces parser for XML parsing. Most of the time, I have no problems. However, occasionally, at the point I am creating the new DocumentBuilder .. ... DocumentBuilderFactory...