【Java.NIO】API —— Channel接口 —— SocketChannel类

本文详细介绍了SocketChannel类,它是Java NIO中的重要组件之一,用于替代传统的Socket编程,并提供了更多的功能和灵活性。文章覆盖了SocketChannel的基本概念、创建方法、主要API使用及非阻塞模式下的读写操作。
java.nio.channels
public abstract class SocketChannel extends AbstractSelectableChannel implements ByteChannel, ScatteringByteChannel, GatheringByteChannel, NetworkChannel


SocketChannel可看作是Socket的替代类,但它比Scoket具有更多的功能。

SocketChannel不仅从SelectableChannel父类中继承了configureBlocking()和register()方法,而且实现了ByteChannel接口,因此具有读写数据的read(Buffer dst)和write(Buffer src)方法

SocketChannel没有public类型的构造方法,必须通过它的静态方法open()来创建SocketChannel对象。



SocketChannel是一个连接到TCP网络套接字的通道。可以通过以下两种方式创建SocketChannel:

  • 打开一个SocketChannel并连接到互联网上的某台服务器
  • 一个新连接到达ServerSocketChannel时,会创建一个SocketChannel



SocketChannel的主要方法如下:

  • open(), open(SocketAddress remote) —— 静态工厂方法负责创建SocketChannel对象,

SocketChannel socketChannel = SocketChannel.open();
channel.connect(remote);
等价于:
SocketChannel socketChannel = SocketChannel.open(remote);

  • close() —— 关闭SocketChannel
  • validOps() —— 返回SocketChannel所能产生的事件,这个方法总是返回以下值: SelectionKey.OP_CONNECT | Selection.OP_READ | SelectionKey.OP_WRITE
  • socket() —— 返回与这个SocketChannel关联的Socket对象,每个SocketChannel对象都与一个Socket对象关联
  • isConnected() —— 判断底层Socket()是否已经建立了远程连接
  • isConnectionPending() —— 判断是否正在进行远程连接,当远程连接已经开始,但还没有完成时,返回true,否则返回false
  • connect(SocketAddress remote) —— 使底层Socket建立远程连接。当SocketChannel处于非阻塞模式时,如果立即连接成功,该方法返回true,如果不能立即成功连接,返回false,程序过会必须通过调用finishConnect()方法来完成连接。当SocketChannel处于阻塞模式,如果立即连接成功,该方法返回true,如果不能立即连接成功,将进入阻塞状态,直到连接成功,或者出现I/O异常
  • finishConnect() —— 试图完成连接远程服务器的操作。在非阻塞模式下,建立连接从调用SocketChannel的connect()方法开始,到调用finishConnect()结束。如果finishConnect()方法顺利完成连接,或者在调用此方法之前连接已经建立,则finishConnect()方法立即返回true。如果连接操作还没完成,则立即返回false;如果连接操作中遇到异常而失败,则抛出相应的I/O异常。在阻塞模式下,如果连接操作没有完成,则会进入阻塞状态,直到连接完成,或者出现I/O异常
  • read(ByteBuffer dst) —— 从Channel中读入若干字节,把它们存放到参数指定的ByteBuffer中。假定执行read()方法前,ByteBuffer的位置为p,剩余容量为r,r等于dst,remaining()方法的返回值。假定read()方法实际上读入了n个字节,read()方法返回后,参数dst引用的ByteBuffer的位置变为p+n,极限保持不变。
    • 在阻塞模式下,read()方法会争取读取到r个字节,如果输入流中不足r个字节,就进入阻塞状态,直到读入r个字节,或者读到了输入流末尾,或者出现了I/O异常
    • 在非阻塞模式下,read()方法奉行能读到多少数据就读多少数据的元素。read()方法读取当前通道中的可读数据,有可能不足r个字节,或者为0个直接,read()方法总是立即返回,而不会等到读取了r个字节再返回。
    • read()方法返回实际上读入的字节数,有可能为0.如果返回-1,就表示读到了输入流的末尾
  • write(ByteBuffer src) —— 把参数src指定的ByteBuffer中的字节写到Channel中。假定执行write()方法前,ByteBuffer的位置为p,剩余容量为r,r等于src.remaining()方法的返回值。假定write()方法实际上相通道中写入了n个字节,write()方法返回后,参数src引用的ByteBuffer的位置变为p+n,极限保持不变。
    • 在阻塞模式下,wirte()方法会争取输出r个字节,如果底层网络的输出缓冲区不能容纳r个字节,就进入阻塞状态,直到输出了r个字节,或者出现了I/O异常
    • 在非阻塞模式下,write()方法奉行能输出多少数据就输出多少数据的原则,有可能不足r个字节,或者为0个字节,write()方法总是立即返回,而不会等到输出r个字节后在返回
    • write(0方法返回实际上输出的字节数,有可能为0


从SocketChannel读取数据

ByteBuffer buf = ByteBuffer.allocate(48);
int bytesRead = socketChannel.read(buf);


read()方法返回的int值表示读了多少字节进Buffer里。如果返回的是-1.表示已经读到了流的末尾(连接关闭了)。

非阻塞模式下,read()方法在尚未读取到任何数据时可能就返回了。所以需要关注它的int返回值,它会告诉你读取了多少字节。



写入SocketChannel —— 非阻塞模式 ***

String newData = ... ...

ByteBuffer buf = ByteBuffer.allocate(48);
buf.clear();
buf.put(newData.getBytes());

buf.flip();

while(buf.hasRemaining()){
    chaneel.write(buf);
}

SocketChannel.write()方法的调用是在一个while循环中的。write()方法无法保证能写多少字节到SocketChannel中,所以,需要重复调用write()直到Buffer没有要写的字节为止。



建立连接 —— 非阻塞模式

如果SocketChannel在非阻塞模式下,此时掉哟过connect(),该方法可能在建立连接之前就返回了,为了确定连接是否建立,可以调用finishConnect()方法,

socketChannel.configureBlocking(false);
socketChannel.connect(new InetSocketAddress("http://...", 80));

while (!socketChannel.finishConnect()){
    // wait, or do something else...
}




[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、付费专栏及课程。

余额充值