cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seumas Soltysik (JIRA)" <>
Subject [jira] Updated: (CXF-2145) Proxy in JCA connector throws exception due to concurrency issues
Date Fri, 03 Apr 2009 14:20:13 GMT


Seumas Soltysik updated CXF-2145:

    Attachment: patch2.txt

This second patch simplifies the process of retreiving a new endpoint for each invocation.
Instead of maintaining a pool of endpoint, the patch relies on the pooling of endpoint by
the app server according to spec. After each invocation the endpoint is released and recycled
by the application server.

> Proxy in JCA connector throws exception due to concurrency issues
> -----------------------------------------------------------------
>                 Key: CXF-2145
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Integration
>    Affects Versions: 2.1, 2.0.6, 2.2
>            Reporter: Seumas Soltysik
>         Attachments: patch.txt, patch2.txt
> A customer is having a problem with concurrent access to a JCA endpoint that is deployed
in WebSphere. The stacktrace is below.
> They are running a 2.0.x version of CXF with WebSphere, HP/UX version B.11.23,
Java .
> The problem is that the JCA connector uses a single MDB/EJB proxy for all threads which
is causing the exception to be thrown. The solution is to create a pool of proxies which can
be accessed so that the proxy is used by no more than 1 thread at a time.
> [3/10/09 15:55:19:685 EDT] 0000042f DispatchMDBIn E Failed to obtain service object java:comp/env/GreeterWithWsdlLocalHome

>                                  java.lang.IllegalStateException: Multiple threads can
not use same MessageEndpoint proxy instance concurrently 
>             at

>             at

>             at

>             at

>             at $Proxy50.lookupTargetObject(Unknown Source) 
>             at org.apache.cxf.jca.inbound.DispatchMDBInvoker.getServiceObject(

>             at org.apache.cxf.service.invoker.AbstractInvoker.invoke(

>             at org.apache.cxf.interceptor.ServiceInvokerInterceptor$

>             at org.apache.cxf.workqueue.SynchronousExecutor.execute(

>             at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(

>             at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(

>             at org.apache.cxf.transport.ChainInitiationObserver.onMessage(

>             at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(

>             at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(

>             at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(

>             at org.mortbay.jetty.handler.ContextHandler.handle(

>             at org.mortbay.jetty.handler.ContextHandlerCollection.handle(

>             at org.mortbay.jetty.handler.HandlerWrapper.handle(

>             at org.mortbay.jetty.Server.handle( 
>             at org.mortbay.jetty.HttpConnection.handleRequest(

>             at org.mortbay.jetty.HttpConnection$RequestHandler.content(

>             at org.mortbay.jetty.HttpParser.parseNext( 
>             at org.mortbay.jetty.HttpParser.parseAvailable( 
>             at org.mortbay.jetty.HttpConnection.handle( 
>             at

>             at org.mortbay.thread.BoundedThreadPool$

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message