cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Commented) (JIRA)" <>
Subject [jira] [Commented] (CXF-4154) AbstractConduitSelector reused cached conduit even if protocol was changed
Date Mon, 26 Mar 2012 14:48:28 GMT


Daniel Kulp commented on CXF-4154:

Committed a fix last night that pretty much removes the "selectedConduit" field and keeps
a list of conduits.  Under normal operation, that's a single conduit, but it can "grow" as
additional protocols and such require it.

Because of the field removal, not back portable to <=2.5.x.   Will need to be release noted.

Can you give it a quick spin to make sure it works OK?
> AbstractConduitSelector reused cached conduit even if protocol was changed
> --------------------------------------------------------------------------
>                 Key: CXF-4154
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>            Reporter: Andrei Shakirin
>         Attachments: AbstractConduitSelector.patch
> Hi,
> Actually AbstractConduitSelector.getSelectedConduit() creates and caches conduit in selectedConduit
variable. Cached conduit is reused by the next calls.
> I see the following problem: if user changed protocol in URI between calls, AbstractConduitSelector
still uses cached Conduit even it cannot process new URL. In my case cached HTTP consuit tries
to process UDP URL.
> Proposal for fix: check if protocol in URL was changed and if yes, close and reset selectedConduit.
> Patch is attached.
> Regards,
> Andrei.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message