write attempt timed out; force-closing the connection.

[john meyer]

i am facing an weird issue though it is a common issue but i am little bit 
confused how can we handle it 

Line 202571: x3 Mar 2017 17:16:23,384 SslHandler.java|1419 : [id: 
0xc11db208, L:/181.5xx.19x.x0:1443  - R:/x
02.x6.5.x49:x6862 ] Last write attempt timed 
out; force-closing the connection.
Line 202572: x3 Mar 2017 17:16:23,384 PromiseNotifier.java|57 : Failed to 
mark a promise as success because it is done already: 
DefaultChannelPromise@731ec0a0(success)

  
My concern is, if that write request got timeout, then will it be 
failed to send that packet or it will retry on next attempt? How can 
resolve the scenario?


-- 
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 netty+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/netty/4ae40175-82f7-44cb-ab10-afe91a8d9df0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Last write attempt timed out; force-closing the connection.

[john meyer]

*Last write attempt timed out; force-closing the connection.*


*why it is thrown by sslhandler?*

-- 
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 netty+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/netty/68e8f963-b2cf-420f-8d92-297dc42daa10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ChannelInitializer.initChannel called multiple times

[john meyer]

@Norman

Here is the log. when i am making a socket connection, it is trying to 
create channel from two different port.

Firefox: 48.0.2


[id: 0xa64b3a8b, L:/162.222.190.204:5080 - R:/119.30.38.248:41086]
[id: 0xaf7922c3, L:/162.222.190.204:5080 - R:/119.30.38.248:41087]




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 <nursi...@gmail.com > 
> 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 netty+un...@googlegroups.com .
> 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_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 netty+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/netty/841ac8ae-fde3-45b6-b3c8-8bd31aba309a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ChannelInitializer.initChannel called multiple times

[john meyer]

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 <nursi...@gmail.com > 
> 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 netty+un...@googlegroups.com .
> 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_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 netty+unsubscr...@googlegroups.com.
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.