You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hongchao Deng (JIRA)" <ji...@apache.org> on 2014/10/28 23:30:33 UTC

[jira] [Updated] (ZOOKEEPER-2072) Netty Server Should Configure Child Channel Pipeline By Specifying ChannelPipelineFactory

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

Hongchao Deng updated ZOOKEEPER-2072:
-------------------------------------
    Attachment: test-jenkins.patch

QA run this

> Netty Server Should Configure Child Channel Pipeline By Specifying ChannelPipelineFactory
> -----------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2072
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2072
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>            Reporter: Hongchao Deng
>            Assignee: Hongchao Deng
>         Attachments: test-jenkins.patch
>
>
> Currently, netty server is setting up child channel in this way:
> {code}
>  bootstrap.getPipeline().addLast("servercnxnfactory", channelHandler);
> {code}
> According to the [netty doc|http://netty.io/3.9/api/org/jboss/netty/bootstrap/ServerBootstrap.html],
> bq. you cannot use this approach if you are going to open more than one Channels or run a server that accepts incoming connections to create its child channels.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)