[jbossws-issues] [JBoss JIRA] (JBWS-3985) CXFHandlerResolverImpl not threadsafe

[Alessio Soldano (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-3985:
----------------------------------
              Project: JBoss Web Services  (was: WildFly)
                  Key: JBWS-3985  (was: WFLY-6287)
             Workflow: classic default workflow  (was: GIT Pull Request workflow )
          Component/s: jbossws-cxf
                           (was: Web Services)
    Affects Version/s: jbossws-cxf-5.0.0.Final
                           (was: 9.0.1.Final)


> CXFHandlerResolverImpl not threadsafe
> -------------------------------------
>
>                 Key: JBWS-3985
>                 URL: https://issues.jboss.org/browse/JBWS-3985
>             Project: JBoss Web Services
>          Issue Type: Bug
>          Components: jbossws-cxf
>    Affects Versions: jbossws-cxf-5.0.0.Final
>            Reporter: Bjørn Hilstad
>            Assignee: Alessio Soldano
>
> When the concurrency of handler-chain parsing increases , the following error shows up in the logs:
> Caused by: org.xml.sax.SAXException: FWK005 parse may not be called while parsing.
>         at org.apache.xerces.parsers.DOMParser.parse(DOMParser.java:260)
>         at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:298)
>         at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
>         at org.jboss.wsf.stack.cxf.client.serviceref.CXFHandlerResolverImpl.createHandlerChain(CXFHandlerResolverImpl.java:161)
>         ... 132 more
> One case where I have seen this is when an EJB/MDB uses @WebServiceRef and @HandlerChain to get a reference to a webservice.
> When multiple instances of the EJB/MDB are created at the same time to handle a lot of messages this happens.
> It is the @HandlerChain that triggers the xml parsing and gives the error.
> The Xerces DocumentBuilder is not threadsafe and thus requires code to synchronize it correctly.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)