最近在學習Java AIO操作時，出現如下異常

比較奇怪的是，該異常僅僅在兩個操作間隔非常短的時候，才會出現。根據調式與排查，發現問題出現在AsynchronousSocketChannel的connect方法調用上。

/*** Connects this channel.** <p> This method initiates an operation to connect this channel. This* method behaves in exactly the same manner as the {@link* #connect(SocketAddress, Object, CompletionHandler)} method except that* instead of specifying a completion handler, this method returns a {@code* Future} representing the pending result. The {@code Future}'s {@link* Future#get() get} method returns {@code null} on successful completion.** @param remote* The remote address to which this channel is to be connected** @return A {@code Future} object representing the pending result** @throws UnresolvedAddressException* If the given remote address is not fully resolved* @throws UnsupportedAddressTypeException* If the type of the given remote address is not supported* @throws AlreadyConnectedException* If this channel is already connected* @throws ConnectionPendingException* If a connection operation is already in progress on this channel* @throws SecurityException* If a security manager has been installed* and it does not permit access to the given remote endpoint*/public abstract Future<Void> connect(SocketAddress remote);

此處connect為異步方法，調用connect時，可能并沒有成功建立連接，從而導致出現上述異常。
解決措施：
1、顯示調用get，通過阻塞的方式，獲取連接。

2、通過如下connect方法，通過第三個參數，在完成連接連接時，進行后續操作。

public abstract <A> void connect(SocketAddress remote,A attachment,CompletionHandler<Void,? super A> handler);

總結

以上是生活随笔為你收集整理的java.nio.channels.NotYetConnectedException: null的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。