Hi Ray, It seems your problem is from a synchronized block for a DocumentBuilderFactory. Axis is pooling parser instances, however the current is using only one dbf instance at least.
But, I think also this bottle-neck might be caused by your testing scenarios.I mean the neck might make it hard to find out if you use a real implementation of your business-logics as an end-point. Anyway, if you hope to clear the matter and also you help us to fix it, we may provide a snapshot patch for testing. -- Toshi <[EMAIL PROTECTED]> On Fri, 3 Oct 2003, Sutton, Ray wrote: > > To answer Toshi's comment, the configuration I was testing loop a response > back in the method proxy, the test payload is an echo request so I was able > to simply instantiate our response object and move the payload without > entering our application framework. The only non-Axis/infrastructure > processing is instantiate, move object reference, return. I'll double check > the instantiate doesn't involve a synchronize though. > > The thread dump as requested, I've trimmed it to the lock holder and one on > the waiters, the other two were at the same location in code. > > "Thread-23" daemon prio=5 tid=0x03650408 nid=0xfd8 runnable > [43df000..43dfd94] > at > org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown > Source) > at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:318) > - locked <0x10ac8688> (a > org.apache.xerces.jaxp.DocumentBuilderFactoryImpl) > at
