cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-4024) Update to Jetty 7.5.4 or implement workraound from JETTY-1444
Date Fri, 13 Jan 2012 19:48:39 GMT

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

Daniel Kulp resolved CXF-4024.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5.2
         Assignee: Daniel Kulp
    
> Update to Jetty 7.5.4 or implement workraound from JETTY-1444
> -------------------------------------------------------------
>
>                 Key: CXF-4024
>                 URL: https://issues.apache.org/jira/browse/CXF-4024
>             Project: CXF
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 2.5.1
>         Environment: Windows XP
> java version "1.6.0_26"
> Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing)
>            Reporter: Michael Heß
>            Assignee: Daniel Kulp
>            Priority: Trivial
>             Fix For: 2.5.2
>
>
> After upgrading my application from CXF 2.4.2 to 2.5.1 the embedded jetty stopped working.
> Currently CXF comes bundles with Jetty 7.5.3, which has a rather nasty bug causing the
NIO Connectors to hang in accept().
> After some research I have found JETTY-1444 to document the issue.
> This bug was fixed in Jetty 7.5.4 onwards.
> I have manually exchanged Jetty 7.5.3 with 7.5.4 in my local copy of CXF and can confirm
that it fixes the issue.
> If upgrading to Jetty 7.5.4 is not an option for CXF right now, maybe you can consider
the workaround described in JETTY-1444? I don't understand the specifics, but seems like it
is pretty simple to implement (changing the sequence of ThreadPool init and Server start).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message