Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 8 Apr 2012 13:50:18 +0000 (UTC)
From: "Claus Ibsen (Resolved) (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <506952339.897.1333893018169.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <558090714.10982.1328001370165.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CAMEL-4960) NettyProducer with user defined
 client pipeline factory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen resolved CAMEL-4960.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.9.2
    
> NettyProducer with user defined client pipeline factory 
> --------------------------------------------------------
>
>                 Key: CAMEL-4960
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4960
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-netty
>    Affects Versions: 2.8.1
>         Environment: Windows 7
>            Reporter: Dmitri Zavrid
>            Assignee: Claus Ibsen
>             Fix For: 2.10.0, 2.9.2
>
>
> If user defined client pipeline factory is configured, Netty Producer shares the same instance of ClientPipelineFactory for all created connections. See code below:
>   configuration.getClientPipelineFactory().setProducer(this);
>   configuration.getClientPipelineFactory().setExchange(exchange);
>   configuration.getClientPipelineFactory().setCallback(callback);
>   clientPipeline = configuration.getClientPipelineFactory().getPipeline();
> Which can cause an issue in multithreaded environment. Maybe it is better to create user defined client pipeline factory for each connection as it is done with DefaultClientPipelineFactory?

--
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