cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Salt (JIRA)" <>
Subject [jira] [Updated] (CXF-7135) ConcurrentModificationException in MessageImpl.calcContextCache() when using JMS Transport and JAXRS Client
Date Wed, 16 Nov 2016 14:21:58 GMT


Dan Salt updated CXF-7135:
    Summary: ConcurrentModificationException in MessageImpl.calcContextCache() when using
JMS Transport and JAXRS Client  (was: ConcurrentModificationException in MessageImpl.calcContextCache()
when using JMS Transport)

> ConcurrentModificationException in MessageImpl.calcContextCache() when using JMS Transport
and JAXRS Client
> -----------------------------------------------------------------------------------------------------------
>                 Key: CXF-7135
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 3.0.11
>         Environment: Mac OSX 10.11.6. 
> Java JDK 1.8.0_71 (64 bit Server)
>            Reporter: Dan Salt
>         Attachments:
> Our platform allows the user to switch transports for a particular proxy based on configuration.
We currently allow HTTP and JMS as possible options.
> During recent performance testing, we've hit a bug which causes JAXRS Clients over JMS
to fail with a ConcurrentModificationException:
> A test case is attached that reproduces our problem.
> Our test executes requests across multiple concurrent threads, switching between JMS
and HTTP for both JAXWS and JAXRS Client Proxies. In the test case, executing JAXWS over JMS
works fine, both in single and multi-threaded tests. JAXRS works fine across single and multi-threaded
tests over HTTP with the 'ThreadSafe' flag set on the Client Factory. But when the transport
is switched to JMS two problems occur:
> 1) The ConnectionFactoryFeature fails to properly set the JMS Connection Factory on the
Conduit and results in an error at send-time because no Connection Factory is set. This is
because in JAXRS Clients, the InterceptorProvider is neither a Client or Server, it is a ClientConfiguration,
so the JMS ConnectionFactoryFeature does not fire either of it's methods:
> public void initialize(Client client, Bus bus) 
> public void initialize(Server server, Bus bus)
> We have worked around this in our code by sub-classing and overriding the method:
> public void initialize(InterceptorProvider interceptorProvider, Bus bus)
> .. and adding code similar to that in the ConnectionFactory feature. This resolves the
missing ConnectionFactory problem.
> 2) Under multi-threaded conditions, the JAXRS Clients fail with the following exception:
> Problem with reading the data, class
java.lang.String, ContentType: text/plain.
> 	at org.apache.cxf.jaxrs.impl.ResponseImpl.reportMessageHandlerProblem(
> 	at org.apache.cxf.jaxrs.impl.ResponseImpl.doReadEntity(
> 	at org.apache.cxf.jaxrs.client.AbstractClient.readBody(
> 	at org.apache.cxf.jaxrs.client.ClientProxyImpl.handleResponse(
> 	at org.apache.cxf.jaxrs.client.ClientProxyImpl.doChainedInvocation(
> 	at org.apache.cxf.jaxrs.client.ClientProxyImpl.invoke(
> 	at com.sun.proxy.$Proxy24.doSimpleMethod(Unknown Source)
> 	at$
> 	at
> Caused by: java.util.ConcurrentModificationException
> 	at java.util.HashMap$HashIterator.nextNode(
> 	at java.util.HashMap$
> 	at java.util.HashMap$
> 	at java.util.HashMap.putMapEntries(
> 	at java.util.HashMap.putAll(
> 	at org.apache.cxf.message.MessageImpl$1.putAll(
> 	at org.apache.cxf.message.MessageImpl.calcContextCache(
> 	at org.apache.cxf.message.MessageImpl.getContextualProperty(
> 	at org.apache.cxf.jaxrs.impl.HttpHeadersImpl.getRequestHeaders(
> 	at org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBodyReader(
> 	at org.apache.cxf.jaxrs.impl.ResponseImpl.doReadEntity(
> 	... 7 more
> This occurs even though the 'ThreadSafe' property is set via:
> rsClientFactory.setThreadSafe(true);
> I've done quite a large amount of digging through the code to try and narrow down the
scope of the problem, and the results above is as far as I could get, unfortunately.
> Finally, one important factor is that this error only happens on the latest 3.0.x release
(3.0.11). When I switch my test case to 3.1.8, it does NOT occur. Not sure if this equates
to a fix not being back-ported, or a fundamental difference in functionality. Sadly, we're
not able to yet move to 3.1.x, because of running inside the Karaf container, and our dependencies
on Camel and Spring 3.x.
> Thanks. Please let me know if you need any other information.

This message was sent by Atlassian JIRA

View raw message