11 Replies Latest reply on May 31, 2006 5:15 PM by Chris Baxter

    JBossWS not thread safe

    Chris Baxter Newbie

      From what I am seeing with JBoss 4.0.4.CR2, JBossWS does not appear to be thread safe. I retrieve a Service object from JNDI and then procede to make concurrent requests on it from seperate threads. I pretty much always get exceptions and they vary from test to test. The most common ones are:

      org.xml.sax.SAXException: FWK005 parse may not be called while parsing

      Cannot obtain NamespaceRegistry, because there is no SOAPMessage associated with this context

      Can someone please help me out with this? Is this a known issue? Concurrent access worked just fine when using Axis (JBoss 4.0.3 SP1), but Axis is too slow for me to use. I'm trying to upgrade to JBoss 4.0.4.CR2 and this is a major blocker.