错误分析：OutConnectionProcessor:289] Error when read data from SocketChannel

最新推荐文章于 2025-01-03 20:11:25 发布
最新推荐文章于 2025-01-03 20:11:25 发布 · 196 阅读 · 0
文章标签：

#java

本文讨论了在使用Socket通道进行数据读取时遇到的异常情况，包括`CancelledKeyException`和`NullPointerException`，并分析了在XMPP会话中加载VCard信息时遇到的超时问题。
2012-08-06 05:06:22 Out Connection Reader (18) ERROR [com.pica.gateway.connmng.OutConnectionProcessor:289] Error when read data from SocketChannel
java.nio.channels.CancelledKeyException
at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:55)
at sun.nio.ch.SelectionKeyImpl.readyOps(SelectionKeyImpl.java:69)
at java.nio.channels.SelectionKey.isConnectable(SelectionKey.java:318)
at com.pica.gateway.connmng.OutConnectionProcessor.readMessage(OutConnectionProcessor.java:261)
at com.pica.gateway.connmng.OutConnectionProcessor.access$2(OutConnectionProcessor.java:236)
at com.pica.gateway.connmng.OutConnectionProcessor$1.run(OutConnectionProcessor.java:95)
2012-08-06 05:06:22 Out Connection Reader (18) ERROR [com.pica.gateway.connmng.OutConnectionProcessor:298] Selector exception
java.lang.NullPointerException
at com.pica.gateway.connmng.OutConnectionProcessor.readMessage(OutConnectionProcessor.java:290)
at com.pica.gateway.connmng.OutConnectionProcessor.access$2(OutConnectionProcessor.java:236)
at com.pica.gateway.connmng.OutConnectionProcessor$1.run(OutConnectionProcessor.java:95)
2012-08-06 05:08:26 google transport (64) ERROR [com.pica.gateway.protocols.nxmpp.NioXMPPSession:771] Load vcard error!
Timeout getting VCard information,packet id is 9tibf-4083650: request-timeout(408) Timeout getting VCard information,packet id is 9tibf-4083650
at org.jivesoftware.smackx.packet.VCard.doLoad(VCard.java:553)
at org.jivesoftware.smackx.packet.VCard.load(VCard.java:539)
at com.pica.gateway.protocols.nxmpp.NioXMPPSession.getBuddyVCard(NioXMPPSession.java:766)
at com.pica.gateway.protocols.nxmpp.NioXMPPTransport.getUserVCard(NioXMPPTransport.java:89)
at com.pica.gateway.BaseTransport.handleRcsVcard(BaseTransport.java:1000)
at com.pica.gateway.BaseTransport.processPacket(BaseTransport.java:726)
at com.pica.gateway.BaseTransport.processPacketInThread(BaseTransport.java:278)
at com.pica.gateway.BaseTransport.access$0(BaseTransport.java:242)
at com.pica.gateway.BaseTransport$2.run(BaseTransport.java:234)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
iteye_11790
关注
Java必知必会系列：缓存技术与Memcached
AI天才研究院
09-24 1821
Apache Memcached是一个开源高性能的内存对象缓存系统，用于动态WEB应用以减轻数据库负载。它通过在内存中缓存数据对象来减少数据库调用，从而提高网站响应速度。Memcached最初是用C语言编写的，但后来又有移植到其他语言（如Java、Python等）的实现版本。Memcached提供了多种方式来存储和管理数据，包括内存缓存和磁盘缓存。本文将介绍Java编程语言中的缓存技术及其重要性，并讨论Memcached这种基于内存的缓存系统。
HTTP2:netty http2 StreamChannel多流实现与Http2StreamFrame解码器的源码分析
Mr_rain的专栏
02-08 1378
netty http2 server侧的核心逻辑个人认为，主要在编解码处理器和Stream Transform Channel这块，分别处理Http2 消息帧的编解码，以及连接的多流处理机制。
【Django-meeting系统】Django报错Timeout reading from socket--还没有解
Season 优快云博客
10-17 601
Django报错Timeout reading from socket--还没有解
从socket中读取数据时使用超时
黑客攻防 | .net 源代码下载 | ASP.NET开发 | ORACLE数据库开发 | JAVASCRIPT脚本下载 | java源码下载
03-25 979
导读： 　　Java 1.4在Java API加入了非阻塞I/O（non-blocking I/O），不过Java 1.3和更早的版本都不支持这样的特性。然而，你可以用java.net.Socket类的超时属性来获得一些类似于非阻塞I/O的功能。 　　 　　要使用超时属性，首先你要创建一个socket，然后设置你期望的超时时间。setSoTimeout方法有一个参数，这个int型参数指定了
报错：fdfs while reading from socket: (timed out))
墨痕诉清风的博客
10-13 1272
实际测试 recv_size有可能大于 buffer_size，那么就会存在 文件实际已经下载完成，但是 remain_bytes大于0，导致因为一直等待而超时。具体路径是：[Python安装路径]/site-packages/fdfs_client/异常代码处：remain_bytes -= buffer_size。2. 替换 storage_client.py 代码文件，替换的 storage_client.py 代码。1. 可以直接从 GitHub下载源码进行安装。
Socket笔记之Read timed out深入分析
热门推荐
jannal专栏
09-10 11万+
ReadTimedOut深入分析 PlainSocketImpl.c Java_java_net_PlainSocketImpl_socketSetOption read()时 Java_java_net_SocketInputStream_socketRead0 solaris/native/java/net/bsd_close.c 总结 ReadTimedOut...
谨慎使用SocketChannel的read方法
wei
01-13 1061
下面的代码是一个实例化SocketChannel的过程： SocketChannel channel = SocketChannel.open(); //要设置连接超时 channel.socket().connect(addr,connectionTimeOut_ms); //设置读超时 channel.socket().setSoTimeout(timeou...
hbase 踩坑：hbase大面积读写卡死问题定位分析
sikoutang的博客
05-31 872
setAttribute0(env, fd, RECEIVE_TIMEOUT, DEFAULT_RECEIVE_TIMEOUT)，设置读数据超时 DEFAULT_RECEIVE_TIMEOUT = 120000 毫秒。1、优先从datanode的数据目录删除有问题的磁盘，执行 hdfs dfsadmin -reconfig datanode datanode1:50020 start。生成环境中hbase和hdfs部署在一起，开启了短路读提高性能。hbase 踩坑：hbase大面积读写卡死问题定位分析，
2025-06-22 02:14:04,462 ERROR cluster.YarnClientSchedulerBackend: YARN application has exited unexpectedly with state FAILED! Check the YARN application logs for more details. 2025-06-22 02:14:04,463 ERROR cluster.YarnClientSchedulerBackend: Diagnostics message: Application application_1750558147603_0001 failed 2 times due to AM Container for appattempt_1750558147603_0001_000002 exited with exitCode: -103 Failing this attempt.Diagnostics: [2025-06-22 02:14:04.276]Container [pid=2268,containerID=container_1750558147603_0001_02_000001] is running 77679104B beyond the 'VIRTUAL' memory limit. Current usage: 265.6 MB of 1 GB physical memory used; 2.2 GB of 2.1 GB virtual memory used. Killing container. Dump of the process-tree for container_1750558147603_0001_02_000001 : |- PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE |- 2268 2267 2268 2268 (bash) 0 0 15486976 366 /bin/bash -c /opt/module/jdk1.8.0_212/bin/java -server -Xmx512m -Djava.io.tmpdir=/opt/module/hadoop-3.1.3/data/dfs/nm-local-dir/usercache/root/appcache/application_1750558147603_0001/container_1750558147603_0001_02_000001/tmp -Dspark.yarn.app.container.log.dir=/opt/module/hadoop-3.1.3/logs/userlogs/application_1750558147603_0001/container_1750558147603_0001_02_000001 org.apache.spark.deploy.yarn.ExecutorLauncher --arg 'master:37846' --properties-file /opt/module/hadoop-3.1.3/data/dfs/nm-local-dir/usercache/root/appcache/application_1750558147603_0001/container_1750558147603_0001_02_000001/__spark_conf__/__spark_conf__.properties --dist-cache-conf /opt/module/hadoop-3.1.3/data/dfs/nm-local-dir/usercache/root/appcache/application_1750558147603_0001/container_1750558147603_0001_02_000001/__spark_conf__/__spark_dist_cache__.properties 1> /opt/module/hadoop-3.1.3/logs/userlogs/application_1750558147603_0001/container_1750558147603_0001_02_000001/stdout 2> /opt/module/hadoop-3.1.3/logs/userlogs/application_1750558147603_0001/container_1750558147603_0001_02_000001/stderr |- 2278 2268 2268 2268 (java) 473 29 2317049856 67628 /opt/module/jdk1.8.0_212/bin/java -server -Xmx512m -Djava.io.tmpdir=/opt/module/hadoop-3.1.3/data/dfs/nm-local-dir/usercache/root/appcache/application_1750558147603_0001/container_1750558147603_0001_02_000001/tmp -Dspark.yarn.app.container.log.dir=/opt/module/hadoop-3.1.3/logs/userlogs/application_1750558147603_0001/container_1750558147603_0001_02_000001 org.apache.spark.deploy.yarn.ExecutorLauncher --arg master:37846 --properties-file /opt/module/hadoop-3.1.3/data/dfs/nm-local-dir/usercache/root/appcache/application_1750558147603_0001/container_1750558147603_0001_02_000001/__spark_conf__/__spark_conf__.properties --dist-cache-conf /opt/module/hadoop-3.1.3/data/dfs/nm-local-dir/usercache/root/appcache/application_1750558147603_0001/container_1750558147603_0001_02_000001/__spark_conf__/__spark_dist_cache__.properties [2025-06-22 02:14:04.301]Container killed on request. Exit code is 143 [2025-06-22 02:14:04.302]Container exited with a non-zero exit code 143. For more detailed output, check the application tracking page: http://master:8088/cluster/app/application_1750558147603_0001 Then click on links to logs of each attempt. . Failing the application. 2025-06-22 02:14:04,483 INFO server.AbstractConnector: Stopped Spark@7728643a{HTTP/1.1, (http/1.1)}{0.0.0.0:4040} 2025-06-22 02:14:04,486 ERROR spark.SparkContext: Error initializing SparkContext. java.lang.IllegalStateException: Spark context stopped while waiting for backend at org.apache.spark.scheduler.TaskSchedulerImpl.waitBackendReady(TaskSchedulerImpl.scala:1096) at org.apache.spark.scheduler.TaskSchedulerImpl.postStartHook(TaskSchedulerImpl.scala:231) at org.apache.spark.SparkContext.<init>(SparkContext.scala:640) at org.apache.spark.SparkContext$.getOrCreate(SparkContext.scala:2678) at org.apache.spark.sql.SparkSession$Builder.$anonfun$getOrCreate$2(SparkSession.scala:942) at scala.Option.getOrElse(Option.scala:189) at org.apache.spark.sql.SparkSession$Builder.getOrCreate(SparkSession.scala:936) at org.apache.spark.examples.SparkPi$.main(SparkPi.scala:30) at org.apache.spark.examples.SparkPi.main(SparkPi.scala) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.spark.deploy.JavaMainApplication.start(SparkApplication.scala:52) at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:951) at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:180) at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:203) at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:90) at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:1030) at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:1039) at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala) 2025-06-22 02:14:04,494 INFO spark.SparkContext: SparkContext already stopped. Exception in thread "main" java.lang.IllegalStateException: Spark context stopped while waiting for backend at org.apache.spark.scheduler.TaskSchedulerImpl.waitBackendReady(TaskSchedulerImpl.scala:1096) at org.apache.spark.scheduler.TaskSchedulerImpl.postStartHook(TaskSchedulerImpl.scala:231) at org.apache.spark.SparkContext.<init>(SparkContext.scala:640) at org.apache.spark.SparkContext$.getOrCreate(SparkContext.scala:2678) at org.apache.spark.sql.SparkSession$Builder.$anonfun$getOrCreate$2(SparkSession.scala:942) at scala.Option.getOrElse(Option.scala:189) at org.apache.spark.sql.SparkSession$Builder.getOrCreate(SparkSession.scala:936) at org.apache.spark.examples.SparkPi$.main(SparkPi.scala:30) at org.apache.spark.examples.SparkPi.main(SparkPi.scala) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.spark.deploy.JavaMainApplication.start(SparkApplication.scala:52) at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:951) at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:180) at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:203) at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:90) at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:1030) at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:1039) at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala) 2025-06-22 02:14:04,489 INFO ui.SparkUI: Stopped Spark web UI at http://master:4040 2025-06-22 02:14:04,514 INFO storage.DiskBlockManager: Shutdown hook called 2025-06-22 02:14:04,534 INFO util.ShutdownHookManager: Shutdown hook called 2025-06-22 02:14:04,536 INFO util.ShutdownHookManager: Deleting directory /tmp/spark-aa1d5e4b-40b9-4395-a25e-db587133f3c8 2025-06-22 02:14:04,566 INFO util.ShutdownHookManager: Deleting directory /tmp/spark-d2e97756-5102-456f-9640-7a3a245981a9 2025-06-22 02:14:04,576 INFO util.ShutdownHookManager: Deleting directory /tmp/spark-d2e97756-5102-456f-9640-7a3a245981a9/userFiles-38c65405-58f6-4600-ac43-a94d608c822a 2025-06-22 02:14:04,595 WARN server.TransportChannelHandler: Exception in connection from /172.18.0.2:60198 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:223) at sun.nio.ch.IOUtil.read(IOUtil.java:192) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253) at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133) at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748) 2025-06-22 02:14:04,599 ERROR client.TransportResponseHandler: Still have 1 requests outstanding when connection from /172.18.0.2:60198 is closed 2025-06-22 02:14:04,602 ERROR cluster.YarnSchedulerBackend$YarnSchedulerEndpoint: Sending RequestExecutors(Map(),Map(),Map(),Set()) to AM was unsuccessful 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:223) at sun.nio.ch.IOUtil.read(IOUtil.java:192) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253) at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133) at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748) 2025-06-22 02:14:04,608 ERROR util.Utils: Uncaught exception in thread YARN application state monitor org.apache.spark.SparkException: Exception thrown in awaitResult: at org.apache.spark.util.ThreadUtils$.awaitResult(ThreadUtils.scala:301) at org.apache.spark.rpc.RpcTimeout.awaitResult(RpcTimeout.scala:75) at org.apache.spark.scheduler.cluster.CoarseGrainedSchedulerBackend.requestTotalExecutors(CoarseGrainedSchedulerBackend.scala:742) at org.apache.spark.scheduler.cluster.YarnSchedulerBackend.stop(YarnSchedulerBackend.scala:114) at org.apache.spark.scheduler.cluster.YarnClientSchedulerBackend.stop(YarnClientSchedulerBackend.scala:168) at org.apache.spark.scheduler.TaskSchedulerImpl.stop(TaskSchedulerImpl.scala:881) at org.apache.spark.scheduler.DAGScheduler.stop(DAGScheduler.scala:2365) at org.apache.spark.SparkContext.$anonfun$stop$12(SparkContext.scala:2075) at org.apache.spark.util.Utils$.tryLogNonFatalError(Utils.scala:1419) at org.apache.spark.SparkContext.stop(SparkContext.scala:2075) at org.apache.spark.scheduler.cluster.YarnClientSchedulerBackend$MonitorThread.run(YarnClientSchedulerBackend.scala:124) Caused by: 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:223) at sun.nio.ch.IOUtil.read(IOUtil.java:192) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253) at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133) at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748)
最新发布
06-23
### Spark YARN 容器虚拟内存超出限制被杀死的解决方案 当 Spark 在 YARN 上运行时，如果容器因虚拟内存超出限制而被杀死，通常是由于 YARN 的内存管理机制限制了容器的虚拟内存使用。以下是一些具体的解决方法： ...
深入理解Java I_O流：《Java开发实战经典》文件与网络操作全面分析
!... # 摘要 本文系统地探讨了Java I/O流的原理、实践和进阶应用，旨在为Java编程人员提供文件操作、网络通信等方面的深入理解及解决方案。首先，概述了Java I/O流的基本概念和文件操作的实践应用，详细介绍了字节流与...
学技术学英文：java socket connect timeout & read timeout
zfj321的博客
01-03 1101
如果你没有显式设置连接超时，系统将依赖操作系统或网络设备的默认超时设置。 操作系统默认不会为读取操作设置超时时间，也就是说，读取操作（如读取网络套接字的数据）在没有显式设置超时时间的情况下，可能会无限期地阻塞，直到有数据可读或发生错误。
客户端数据被动刷新 QWebSocket
zhanghw的博客
03-15 2492
一、简述 WebSocket 是一个基于 Web 的协议，旨在使 client 应用程序和远程主机之间进行双向通信。如果最初的握手成功，则两个实体可以来回发送数据。WebSocket 是通过用更少的网络延迟和最小数据交换来努力获取实时数据的应用程序解决方案。 二、代码 #ifndef WEBSOCKET_H #define WEBSOCKET_H #include <QObject>...
Http超时时间之SocketTimeout
weixin_33753845的博客
08-21 1374
/** * Sets the read timeout to a specified timeout, in * milliseconds. A non-zero value specifies the timeout when * reading from Input stream when a connection is established to a...
记录解决java.net.SocketTimeoutException: Read timed out的过程
Melo_FengZhi的博客
02-13 10万+
  上周产品那边反馈说拉取不到2022-01-30的美团第三方账单，于是果断查了下数据库，果然发现数据库中并没有2022-01-30的美团账单记录,分别查了下29号和31号后发现都是有的，就唯独30号的没有。当时我就纳闷了，不就是一个简单的拉取第三方账单的逻辑吗？怎么就会拉取不到呢？为了能够彻底解决我的疑惑，于是我马上去阿里云查了相关拉取日志，不查不知道，一查吓一跳，没想到拉取时还果真出问题了，见下图：   从上图中大家不难发现日志中明显报了java.net.SocketTimeoutException.
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值