You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Dmitri Zavrid (Created) (JIRA)" <ji...@apache.org> on 2012/01/31 10:16:10 UTC
[jira] [Created] (CAMEL-4960) NettyProducer with user defined
client pipeline factory
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
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
[jira] [Resolved] (CAMEL-4960) NettyProducer with user defined
client pipeline factory
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4960.
--------------------------------
Resolution: Not A Problem
Fix Version/s: 2.10.0
Assignee: Claus Ibsen
This works as designed. When you use a custom factory then it's shared. Because a custom factory could be configured and whatnot. I will improved the docs a bit on this.
> 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
>
>
> 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
[jira] [Reopened] (CAMEL-4960) NettyProducer with user defined
client pipeline factory
Posted by "Claus Ibsen (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reopened CAMEL-4960:
--------------------------------
I decided to make the factories stateless, then it works much better.
> 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
>
>
> 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
[jira] [Resolved] (CAMEL-4960) NettyProducer with user defined
client pipeline factory
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ 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