[jira] [Resolved] (CXF-3627) high load may cause deadlocks

["Freeman Fang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CXF-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang resolved CXF-3627.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5
                   2.4.2
                   2.3.6

commit fix
http://svn.apache.org/viewvc?rev=1141787&view=rev for trunk
http://svn.apache.org/viewvc?rev=1141788&view=rev for 2.4.x branch
http://svn.apache.org/viewvc?rev=1141789&view=rev for 2.3.x branch

> high load may cause deadlocks
> -----------------------------
>
>                 Key: CXF-3627
>                 URL: https://issues.apache.org/jira/browse/CXF-3627
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.4.1
>            Reporter: Peter Repp
>            Assignee: Freeman Fang
>             Fix For: 2.3.6, 2.4.2, 2.5
>
>
> we tried to implement bi directional ws communication (both sides are client and servers)
> methods were annotated with @oneway to make sure that on the other side request is processed in separate thread and to make sure requesting thread do not wait for the server processing (because server can issue another request back).
> Unfortunately there is confusing part of the code in org/apache/cxf/interceptor/OneWayProcessorInterceptor.java 
> } catch (RejectedExecutionException e) {
>       //the executor queue is full, so run the task in the caller thread
>       chain.resume();
> that ignores @oneway and continues with the current thread, which means requesting thread (acting as client) will wait... in some cases forever (or till some network timeout)
> What is even worse, there is no single log line indicating that (and suggesting to increase thread pool size), so it was really hard to debug it

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira