Netty - Канал повторного использования для периодических запросов HTTP

Я хочу установить соединение с сервером HTTPS (например, google.com) и периодически получать свежий контент.Netty - Канал повторного использования для периодических запросов HTTP

Я написал простой HTTP-клиент:

public class AsyncLoader { 
    private static final String HOST = "google.com"; 
    private static final int PORT = 443; 

    public static void main(String[] args) throws InterruptedException, IOException, URISyntaxException { 
     final SslContext sslCtx = SslContextBuilder.forClient().trustManager(InsecureTrustManagerFactory.INSTANCE).build(); 

     EventLoopGroup elg = new NioEventLoopGroup(); 
     Bootstrap cb = new Bootstrap() 
       .option(ChannelOption.TCP_NODELAY, true) 
       .option(ChannelOption.SO_KEEPALIVE, true) 
       .option(ChannelOption.SO_REUSEADDR, false) 
       .option(ChannelOption.ALLOCATOR, PooledByteBufAllocator.DEFAULT) 
       .group(elg) 
       .channel(NioSocketChannel.class) 
       .remoteAddress(HOST, PORT) 
       .handler(new ChannelInitializer<SocketChannel>() { 
        @Override 
        protected void initChannel(SocketChannel ch) throws Exception { 
         ch.pipeline() 
           .addLast("ssl", new SslHandler(sslCtx.newEngine(ch.alloc()))) 
           .addLast("http", new HttpClientCodec(4096, 8192, 8192, true, true)) 
           .addLast("simple", new SimpleChannelInboundHandler<HttpObject>() { 
            @Override 
            public void channelActive(ChannelHandlerContext ctx) throws Exception { 
//          ctx.writeAndFlush(createReq()); 
            } 

            @Override 
            protected void channelRead0(ChannelHandlerContext ctx, HttpObject msg) throws Exception { 
             System.out.println(msg); 
//          ctx.writeAndFlush(createReq()); 
            } 
           }) 
           .addLast(new LoggingHandler()); 
        } 
       }); 

     Channel channel = cb.connect().sync().channel(); 

     channel.write(createReq()); 
     Thread.sleep(1000L); 
     channel.write(createReq()); 
    } 

    private static DefaultFullHttpRequest createReq() throws URISyntaxException { 
     DefaultFullHttpRequest requestCopy = new DefaultFullHttpRequest(HttpVersion.HTTP_1_1, HttpMethod.GET, 
       new URI("/").toASCIIString()); 
     HttpHeaders headersCopy = requestCopy.headers(); 
     headersCopy.set(HttpHeaderNames.HOST, HOST); 
     headersCopy.set(HttpHeaderNames.CONNECTION, HttpHeaderValues.KEEP_ALIVE); 
     return requestCopy; 
    } 
}

В конце основного метода я отправить два HTTP-запросы с 1-секундной задержкой. Сервер отвечает на первый запрос, но не на втором ...

Я позволил подробно протоколирования:

FINE: -Dio.netty.recycler.maxCapacity.maxCapacity: 262144 
Jan 28, 2016 4:32:30 PM io.netty.handler.logging.LoggingHandler write 


FINE: [id: 0x2baa7120, /172.21.222.178:32972 => google.com/173.194.220.138:443] WRITE, DefaultFullHttpRequest(decodeResult: success, version: HTTP/1.1, content: UnpooledUnsafeHeapByteBuf(ridx: 0, widx: 0, cap: 0)) 
GET/HTTP/1.1 
host: google.com 
connection: keep-alive, 0B 


Jan 28, 2016 4:32:30 PM io.netty.handler.ssl.util.InsecureTrustManagerFactory$1 checkServerTrusted 
FINE: Accepting a server certificate: CN=*.google.com, O=Google Inc, L=Mountain View, ST=California, C=US 
Jan 28, 2016 4:32:30 PM io.netty.handler.ssl.CipherSuiteConverter cacheFromOpenSsl 
FINE: Cipher suite mapping: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 => ECDHE-RSA-AES128-GCM-SHA256 
Jan 28, 2016 4:32:30 PM io.netty.handler.ssl.CipherSuiteConverter cacheFromOpenSsl 
FINE: Cipher suite mapping: SSL_ECDHE_RSA_WITH_AES_128_GCM_SHA256 => ECDHE-RSA-AES128-GCM-SHA256 
Jan 28, 2016 4:32:30 PM io.netty.handler.ssl.SslHandler setHandshakeSuccess 
FINE: [id: 0x2baa7120, /172.21.222.178:32972 => google.com/173.194.220.138:443] HANDSHAKEN: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 
Jan 28, 2016 4:32:30 PM io.netty.handler.logging.LoggingHandler userEventTriggered 
FINE: [id: 0x2baa7120, /172.21.222.178:32972 => google.com/173.194.220.138:443] USER_EVENT: SslHandshakeCompletionEvent(SUCCESS) 


DefaultHttpResponse(decodeResult: success, version: HTTP/1.1) 
HTTP/1.1 302 Found 
Location: https://ipv4.google.com/sorry/IndexRedirect?continue=https://google.com/&q=CGMSBFuXuysY7rCotQUiGQDxp4NLP1T70JLoOfxaOtbIYimcgkkrqxE 
Date: Thu, 28 Jan 2016 13:32:31 GMT 
Pragma: no-cache 
Expires: Fri, 01 Jan 1990 00:00:00 GMT 
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 
Content-Type: text/html; charset=UTF-8 
Server: HTTP server (unknown) 
Content-Length: 331 
X-XSS-Protection: 1; mode=block 
X-Frame-Options: SAMEORIGIN 
Alternate-Protocol: 443:quic,p=1 
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25" 
DefaultLastHttpContent(data: SlicedAbstractByteBuf(ridx: 0, widx: 331, cap: 331/331, unwrapped: PooledUnsafeDirectByteBuf(ridx: 913, widx: 913, cap: 942)), decoderResult: success) 


Jan 28, 2016 4:32:32 PM io.netty.handler.logging.LoggingHandler write 


FINE: [id: 0x2baa7120, /172.21.222.178:32972 => google.com/173.194.220.138:443] WRITE, DefaultFullHttpRequest(decodeResult: success, version: HTTP/1.1, content: UnpooledUnsafeHeapByteBuf(ridx: 0, widx: 0, cap: 0)) 
GET/HTTP/1.1 
host: google.com 
connection: keep-alive, 0B 

Jan 28, 2016 4:36:31 PM io.netty.handler.logging.LoggingHandler channelInactive 
FINE: [id: 0x2baa7120, /172.21.222.178:32972 :> google.com/173.194.220.138:443] INACTIVE 
Jan 28, 2016 4:36:31 PM io.netty.handler.logging.LoggingHandler exceptionCaught 
FINE: [id: 0x2baa7120, /172.21.222.178:32972 :> google.com/173.194.220.138:443] EXCEPTION: io.netty.handler.codec.PrematureChannelClosureException: channel gone inactive with 1 missing response(s) 
io.netty.handler.codec.PrematureChannelClosureException: channel gone inactive with 1 missing response(s) 
    at io.netty.handler.codec.http.HttpClientCodec$Decoder.channelInactive(HttpClientCodec.java:228) 
    at io.netty.channel.CombinedChannelDuplexHandler.channelInactive(CombinedChannelDuplexHandler.java:213) 
    at io.netty.channel.ChannelHandlerInvokerUtil.invokeChannelInactiveNow(ChannelHandlerInvokerUtil.java:56) 
    at io.netty.channel.DefaultChannelHandlerInvoker.invokeChannelInactive(DefaultChannelHandlerInvoker.java:93) 
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:133) 
    at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:332) 
    at io.netty.handler.ssl.SslHandler.channelInactive(SslHandler.java:724) 
    at io.netty.channel.ChannelHandlerInvokerUtil.invokeChannelInactiveNow(ChannelHandlerInvokerUtil.java:56) 
    at io.netty.channel.DefaultChannelHandlerInvoker.invokeChannelInactive(DefaultChannelHandlerInvoker.java:93) 
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:133) 
    at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:895) 
    at io.netty.channel.AbstractChannel$AbstractUnsafe$7.run(AbstractChannel.java:719) 
    at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:339) 
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:356) 
    at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:742) 
    at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) 
    at java.lang.Thread.run(Thread.java:745)

Как вы можете видеть, сервер ответил на первый запрос и игнорировал второй запрос.

Но если я удалю:

channel.write(createReq()); 
Thread.sleep(1000L); 
channel.write(createReq());

и раскомментировать код внутри ChannelInitializer:

.addLast("simple", new SimpleChannelInboundHandler<HttpObject>() { 
    @Override 
    public void channelActive(ChannelHandlerContext ctx) throws Exception { 
     ctx.writeAndFlush(createReq()); 
    } 

    @Override 
    protected void channelRead0(ChannelHandlerContext ctx, HttpObject msg) throws Exception { 
     System.out.println(msg); 
     ctx.writeAndFlush(createReq()); 
    } 
})

все будет работать с летающими цветами, и я получил то, что ожидал:

DefaultHttpResponse(decodeResult: success, version: HTTP/1.1) 
HTTP/1.1 302 Found 
Location: https://ipv4.google.com/sorry/IndexRedirect?continue=https://google.com/&q=CGMSBFuXuysYprSotQUiGQDxp4NLFkyG4_X9zrF5oyzQ5olUQEgR-54 
Date: Thu, 28 Jan 2016 13:39:50 GMT 
Pragma: no-cache 
Expires: Fri, 01 Jan 1990 00:00:00 GMT 
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 
Content-Type: text/html; charset=UTF-8 
Server: HTTP server (unknown) 
Content-Length: 331 
X-XSS-Protection: 1; mode=block 
X-Frame-Options: SAMEORIGIN 
Alternate-Protocol: 443:quic,p=1 
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25" 
DefaultLastHttpContent(data: SlicedAbstractByteBuf(ridx: 0, widx: 331, cap: 331/331, unwrapped: PooledUnsafeDirectByteBuf(ridx: 913, widx: 913, cap: 942)), decoderResult: success) 
DefaultHttpResponse(decodeResult: success, version: HTTP/1.1) 
HTTP/1.1 302 Found 
Location: https://ipv4.google.com/sorry/IndexRedirect?continue=https://google.com/&q=CGMSBFuXuysYprSotQUiGQDxp4NLFkyG4_X9zrF5oyzQ5olUQEgR-54 
Date: Thu, 28 Jan 2016 13:39:51 GMT 
Pragma: no-cache 
Expires: Fri, 01 Jan 1990 00:00:00 GMT 
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 
Content-Type: text/html; charset=UTF-8 
Server: HTTP server (unknown) 
Content-Length: 331 
X-XSS-Protection: 1; mode=block 
X-Frame-Options: SAMEORIGIN 
Alternate-Protocol: 443:quic,p=1 
Alt-Svc: quic=":443"; ma=604800; v="30,29,28,27,26,25" 
DefaultLastHttpContent(data: SlicedAbstractByteBuf(ridx: 0, widx: 331, cap: 331/331, unwrapped: PooledUnsafeDirectByteBuf(ridx: 913, widx: 913, cap: 942)), decoderResult: success)

В чем моя проблема? Я не могу писать на канал за пределами методов обратного вызова Netty?

источник

2016-01-28 Ivan Babanin

Вы используете 'write' на канале, но' writeAndFlush' на ctx, do writeAndFlush на канале – Ferrybig

@Ferrybig, о, мой бог, какая неосторожная ошибка, которая стоит 3 часа в моей жизни. Ура! –

При использовании netty важно убедиться, что каждый звонок write() сопровождается вызовом flush(), когда вы пишете на свой канал, вы пишете без промывки, заставляя данные оставаться в памяти программы, и не отправлять.

Изменить телефон от write() до writeAndFlush().

источник

2016-01-28 14:01:19 Ferrybig

Netty - Канал повторного использования для периодических запросов HTTP

ответ

Смежные вопросы