【Java.NIO】API —— Channel接口

本文介绍了Java NIO中的通道概念及其与流的区别,详细解释了通道的基本特性、使用方式及其实现接口如ByteChannel、SelectableChannel等。还探讨了分散读取和集中写入的概念及其实现。

Java NIO的通道类似流stream,但又有些不同:

  • 既可以从通道中读取数据,又可以写数据到通道。但流的读写通常是单向的
  • 通道可以异步地读写
  • 通道中的数据总是先读到一个Buffer,或者总是要从一个Buffer中写入
  • Channel用于在字节缓冲区和位于Channel另一侧的实体(通常是一个文件或套接字)之间有效的传输数据




java.nio.channels.Channel接口只声明了两个方法:

java.nio.channels
public interface Channel extends Closeable

  • close() - 关闭通道
  • isOpen() - 判断通道是否打开

通道在创建时被打开,一旦关闭通道,就不能重新打开了。


一些子接口/子类

ReadableByteChannel和WritableByteChannel, 以及ByteChannel

两个重要的子接口。

  • ReadabelByteChannel接口声明了read(ByteBuffer dst)方法,把数据源的数据读入参数指定的ByteBuffer缓冲区中
  • WritableByteBuffer接口声明了write(ByteBuffer src)方法,该方法把参数指定的ByteBuffer缓冲区中的数据写到数据汇中


ByteChannel接口扩展了这两个接口,因而同时支持读写操作。



分散和聚集 —— GatheringByteChannel和ScatteringByteChannel

  • ScatteringByteChannel接口扩展了ReadableByteChannel接口,允许分散地读取数据。分散读取数据是指单个读取操作能填充多个缓冲区。ScatteringByteChannel接口声明了read(ByteBuffer[] dsts)方法,该方法把从数据源读取的数据依次填充到参数指定的ByteBuffer数值中
  • GatheringByteChannel接口扩展了WritableByteChannel接口,允许集中地写入数据。集中写入数据是指单个写操作能把多个缓冲区的数据写到数据汇。GatheringByteChannel接口声明了write(ByteBuffer[] srcs)方法,该方法依次把参数指定的ByteBuffer数组的每个ByteBuffer中的数据写入数据汇。
  • 分散读取和集中写数据能够进一步提高输入和输出操作的速度。

Scattering Reads:


ByteBuffer header = ByteBuffer.allocate(128);
ByteBuffer body = ByteBuffer.allocate(1024);

ByteBuffer[] bufferArray = {header, body};

channel.read(bufferArray);

注意buffer首先被插入到数组,然后再将数组作为channel.read()的输入参数。read()方法按照buffer在数组中的顺序将从channel中读取的数据写到buffer中,当一个buffer被写满后,channel紧接着向另一个buffer中写。

Scattering Reads在移动一下buffer前,必须填满当前的buffer。这意味着它不适用于动态消息。

Gathering Writes


ByteBuffer header = ByteBuffer.allocate(128);
ByteBuffer body = ByteBuffer.allocate(1024);

ByteBuffer[] bufferArray = {header, body};

channel.write(bufferArray);

buffer数组是write()方法的入参,write()方法会按照buffer在数组中的顺序,将数据写入到channel,注意只有position和limit之间的数据才会被写入。与scattering reads相反,gathering writes能较好地处理动态消息。


FileChannel类

FileChannel类代表与文件相连的通道。该类实现了ByteChannel, ScatteringByteChannel和GatheringByteChannel接口,支持读写操作,分散读操作和集中写操作。

FileChannel类没有提供公开的构造方法,因此用户不能使用new构造;不过,在FIleInputStream, FileOutputStream和RandomAccessFile类中提供了getChannel(0方法,该方法返回相应的FileChannel对象。

例如:

RandomAccessFile aFile = new RandomAccessFile("data/nio-data.txt", "rw");
FileChannel inChannel = aFile.getChannel();

ByteBuffer buf = ByteBuffer.allocate(48);

int byteRead = inChannel.read(buf);
while (byteRead != -1){
    System.out.println("Read" + bytesRead);
    buf.flip();

    while(buf.hasRemaining()){
        System.out.println((char)buf.get());
    }

    buf.clear();
    bytesRead = inChannel.read(buf);
}

aFile.close();


SelectableChannel类

java.nio.channels
public abstract class SelectableChannel extends AbstractInterruptibleChannel implements Channel


SelectableChannel是一种支持阻塞I/O和非阻塞I/O的通道

在非阻塞模式下,读写数据不会阻塞,并且SelectableChannel可以向Selector注册读就绪和写就绪等事件。

Selector负责监控这些事件,等到事件发生时,比如发生了读就绪事件,SelectableChannel就可以执行读操作了。



SelectableChannel的主要方法如下:

  • confugureBlocking(boolean block) —— 当参数block为true时,表示设为阻塞模式;如果为false,表示设为非阻塞模式。默认情况下,采用阻塞模式,该方法返回对象本身的引用
  • isBlocking —— 判断是否处于阻塞模式
  • register(Selector sel, int ops) —— 向Selector注册事件
  • register(Selector sel, int ops, Object attachment) —— 向Selector注册事件
  • 上两个方法返回一个SelectionKey对象,用来跟踪被注册的事件。register()方法(第二个)还有一个Object类型的参数attachment,用于为SelectionKey关联一个附件,当被注册事件发生后,需要处理该事件时,可以从SelectionKey中获得这个附件,该附件可用来包含与处理这个事件相关的信息

SelectionKey key = socketChannel.register(selector, SelectionKey.OP_READ | SelectionKey.OP_WRITE);
或者
MyHandler handler = new MyHandler();
SelectionKey key = socketChannel.register(selector, SelectionKey.OP_READ | SelectionKey.OP_WRITE, handler);
或者
SelectionKey key = socketChannel.register(selector, SelectionKey.OP_READ | SelectionKey.OP_WRITE);
MyHandler handler = new MyHandler();
key.attach(handler);






[root@yfw ~]# cd /opt/openfire [root@yfw openfire]# ls -l /opt/openfire/plugins/restapi/ ls: cannot access '/opt/openfire/plugins/restapi/': No such file or directory [root@yfw openfire]# tail -f /opt/openfire/logs/openfire.log at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.108.Final.jar:4.1.108.Final] at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.108.Final.jar:4.1.108.Final] at java.lang.Thread.run(Thread.java:829) [?:?] 2025.10.03 00:48:37.616 ERROR [socket_c2s-thread-4]: org.jivesoftware.openfire.nio.NettyConnection - Problem during connection close or cleanup io.netty.channel.StacklessClosedChannelException: null at io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object, ChannelPromise)(Unknown Source) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] 2025.10.03 00:48:51.280 WARN [socket_c2s-thread-5]: org.jivesoftware.openfire.net.StanzaHandler - TLS requested by initiator when TLS was never offered by server. Closing connection: NettyConnection{peer: /64.62.197.2:37526, state: CLOSED, session: LocalClientSession{address=localhost/fd019775-0604-48c3-890b-927d4a9329f2, streamID=a1slsqrfla, status=CLOSED, isEncrypted=false, isDetached=false, serverName='localhost', isInitialized=false, hasAuthToken=false, peer address='64.62.197.2', presence=' <presence type="unavailable"/>'}, Netty channel handler context name: NettyClientConnectionHandler#0} 2025.10.03 01:25:57.988 WARN [PluginMonitorExec-2]: org.jivesoftware.openfire.container.PluginManager - Ignoring plugin 'restapi-openfire-plugin-assembly': requires server version 5.0.0. Current server version is 4.9.2. 2025.10.03 01:29:11.523 WARN [socket_c2s-thread-7]: org.jivesoftware.openfire.nio.NettyXMPPDecoder - Error occurred while decoding XMPP stanza, closing connection: NettyConnection{peer: /35.203.210.191:59128, state: OPEN, session: LocalClientSession{address=localhost/33ef000c-a3c3-4c31-ae17-74d84ffa0605, streamID=597g80vfvc, status=CONNECTED, isEncrypted=false, isDetached=false, serverName='localhost', isInitialized=false, hasAuthToken=false, peer address='35.203.210.191', presence=' <presence type="unavailable"/>'}, Netty channel handler context name: NettyClientConnectionHandler#0} java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[?:?] at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[?:?] at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:276) ~[?:?] at sun.nio.ch.IOUtil.read(IOUtil.java:233) ~[?:?] at sun.nio.ch.IOUtil.read(IOUtil.java:223) ~[?:?] at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:356) ~[?:?] at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:255) ~[netty-buffer-4.1.108.Final.jar:4.1.108.Final] at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-buffer-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.108.Final.jar:4.1.108.Final] at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.108.Final.jar:4.1.108.Final] at java.lang.Thread.run(Thread.java:829) [?:?] 2025.10.03 01:29:11.525 ERROR [socket_c2s-thread-7]: org.jivesoftware.openfire.nio.NettyConnection - Problem during connection close or cleanup java.io.IOException: Broken pipe at sun.nio.ch.FileDispatcherImpl.write0(Native Method) ~[?:?] at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) ~[?:?] at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:113) ~[?:?] at sun.nio.ch.IOUtil.write(IOUtil.java:58) ~[?:?] at sun.nio.ch.IOUtil.write(IOUtil.java:50) ~[?:?] at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:462) ~[?:?] at io.netty.channel.socket.nio.NioSocketChannel.doWrite(NioSocketChannel.java:415) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannel$AbstractUnsafe.flush0(AbstractChannel.java:931) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.flush0(AbstractNioChannel.java:359) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannel$AbstractUnsafe.flush(AbstractChannel.java:895) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.DefaultChannelPipeline$HeadContext.flush(DefaultChannelPipeline.java:1372) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(AbstractChannelHandlerContext.java:935) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeFlush(AbstractChannelHandlerContext.java:921) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.flush(AbstractChannelHandlerContext.java:907) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.ChannelOutboundHandlerAdapter.flush(ChannelOutboundHandlerAdapter.java:125) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(AbstractChannelHandlerContext.java:939) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeWriteAndFlush(AbstractChannelHandlerContext.java:957) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:982) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:950) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:1000) ~[netty-transport-4.1.108.Final.jar:4.1.108.Final] at org.jivesoftware.openfire.nio.NettyConnection.close(NettyConnection.java:215) [xmppserver-4.9.2.jar:4.9.2] at org.jivesoftware.openfire.nio.NettyXMPPDecoder.exceptionCaught(NettyXMPPDecoder.java:71) [xmppserver-4.9.2.jar:4.9.2] at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:346) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:325) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.fireExceptionCaught(AbstractChannelHandlerContext.java:317) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.DefaultChannelPipeline$HeadContext.exceptionCaught(DefaultChannelPipeline.java:1377) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:346) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.AbstractChannelHandlerContext.invokeExceptionCaught(AbstractChannelHandlerContext.java:325) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.DefaultChannelPipeline.fireExceptionCaught(DefaultChannelPipeline.java:907) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.handleReadException(AbstractNioByteChannel.java:125) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:177) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) [netty-transport-4.1.108.Final.jar:4.1.108.Final] at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.108.Final.jar:4.1.108.Final] at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.108.Final.jar:4.1.108.Final] at java.lang.Thread.run(Thread.java:829) [?:?]
最新发布
10-04
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值