Thanks norman

Here is my pipeline

@Override
public void initChannel(SocketChannel ch) throws Exception 
{
logger.info("=================initChannel===================="+this);
ChannelPipeline pipeline = ch.pipeline();

pipeline.addLast("codec-http", new HttpServerCodec());
pipeline.addLast("deflater", new HttpContentCompressor(1));
pipeline.addLast("aggregator", new HttpObjectAggregator(65536));
pipeline.addLast(CommonExecutors, "websocket-handler", new 
WebSocketTransport());
}


On Tuesday, September 20, 2016 at 11:09:17 PM UTC+6, Norman Maurer wrote:
>
> Ensure its actually the same connection. I suspect firefox is opening two 
> connections.
>
> On 20 Sep 2016, at 09:30, john meyer <[email protected] <javascript:>> 
> wrote:
>
> I am getting a weird behavior in channel pipeline initializer. when a new 
> connection registered, initChannel() called two times. This is happening 
> only when i am testing client socket connection from firefox browser.
>
>
> Urgent help needed. what is the reason actually.
>
> Netty version: 4.1.5
>
>
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Netty discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/netty/ab87503f-7383-4c0a-b64d-1b5792307089%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/netty/ab87503f-7383-4c0a-b64d-1b5792307089%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Netty discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/netty/7e9259bf-7b7c-4a19-9f70-cf0c7d94056c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to