I suggest trying with the latest version of CXF, in case it's an issue that's been fixed, and if you can still reproduce it then create a JIRA including the stacktrace.
Colm. On Fri, Sep 27, 2019 at 12:19 PM Mantas Gridinas <[email protected]> wrote: > Hi! > > I've recently started using Apache CXF to consume SOAP based HTTP > interfaces. The documentation suggests that there are two modes of > operation for Apache CXF: per thread HttpURLConnection based client, > which blocks the thread until response is processed and asynchronous > mode, which permits multiple requests per thread. While using the > latter mode, I seem to come into an issue where responses that are not > malformed (as seen by BURP HTTP proxy and CXF's logging interceptors) > are treated as malformed by the parser for what ever reason. Question > stands: Does the Async mode ensure that the underlying parser (ex. > FasterXML/Woodstox) can be used safely while running in > AutomaticWorkQueue? > > The entire setup is as follows: > > Apache camel 2.23 with Apache CXF 3.2.7 using direct component routes > that pass data straight into CXFEndpoints provided via Apache Camel > CXF integration. >
