我创建了一个小型Netty服务器来计算BigInteger的阶乘并发送结果。代码如下。
Factorial.java
public class Factorial {
private int port;
public Factorial(int port) {
this.port = port;
}
public void run(int threadcount) throws Exception {
EventLoopGroup bossGroup = new NioEventLoopGroup();
EventLoopGroup workerGroup = new NioEventLoopGroup(threadcount);
try {
ServerBootstrap b = new ServerBootstrap();
b.group(bossGroup, workerGroup)
.channel(NioServerSocketChannel.class)
.childHandler(new ChannelInitializer<SocketChannel>() {
@Override
public void initChannel(SocketChannel ch) throws Exception {
ch.pipeline().addLast(new FactorialHandler());
}
})
.option(ChannelOption.SO_BACKLOG, 128)
.childOption(ChannelOption.SO_KEEPALIVE, true);
ChannelFuture f = b.bind(port).sync();
f.channel().closeFuture().sync();
} finally {
workerGroup.shutdownGracefully();
bossGroup.shutdownGracefully();
}
}
public static void main(String[] args) throws Exception {
int port = 15000;
new Factorial(port).run(Integer.parseInt(args[0]));
}
}
FactorialHandler.java
public class FactorialHandler extends ChannelInboundHandlerAdapter {
@Override
public void channelRead(ChannelHandlerContext ctx, Object msg) {
BigInteger result = BigInteger.ONE;
String resultString;
for (int i=2000; i>0; i--)
result = result.multiply(BigInteger.valueOf(i));
resultString = result.toString().substring(0, 3)+"\n";
ByteBuf buf = Unpooled.copiedBuffer(resultString.getBytes());
ctx.write(buf);
ctx.flush();
}
@Override
public void exceptionCaught(ChannelHandlerContext ctx, Throwable cause) {
cause.printStackTrace();
ctx.close();
}
}
当我跑步时,我收到以下错误
Jun 08, 2018 5:28:09 PM io.netty.util.ResourceLeakDetector reportTracedLeak
SEVERE: LEAK: ByteBuf.release() was not called before it's garbage-collected. See http://netty.io/wiki/reference-counted-objects.html for more information.
Recent access records:
正如在给定链接中所解释的那样,我在buf.release()
之后调用了channelRead方法中的ctx.flush()
来发布ByteBuffer。
但是当我这样做时,服务器开始抛出以下异常
io.netty.util.IllegalReferenceCountException: refCnt: 0, increment: 1
有人可以告诉我如何解决这个问题吗?
答案 0 :(得分:3)
问题不在于出站ByteBuf。 Outbound ByteBufs总是为您服务(参见OutboundMessages)。问题是入站ByteBuf。我在看着你,FactorialHandler。它延伸ChannelInboundHandlerAdapter。请注意JavaDoc:
请注意,之后不会发布消息 channelRead(ChannelHandlerContext,Object)方法返回 自动。如果您正在寻找ChannelInboundHandler 实现自动释放收到的消息, 请参阅SimpleChannelInboundHandler。
你的处理程序有这样的签名:
public void channelRead(ChannelHandlerContext ctx, Object msg)
那个msg,(顺便说一下,你不使用它)实际上是一个ByteBuf,这正是上面JavaDoc注意到的警告你的内容。 (在没有任何其他ChannelHandler的情况下,消息将始终是ByteBuf的实例。)
所以你的选择是:
答案 1 :(得分:1)
因为你不调用msg.release()
(msg是ByteBuf的一个实例)。