docker 每隔15分钟就会出现此异常，请查看fillInStackTrace信息

xyhw6mcr  于 2022-12-18  发布在  Docker
关注(0)|答案(2)|浏览(137)

**问题描述：**MongoDB版本为3.4

实际上，没有做任何正常的查询，写，
因为它处于测试阶段，所以QPS较小。

**问题：**1：这种异常现象是如何产生的。

2：需要做什么配置或调整？帮帮我

02-01 15:11:47 WARN  - Got socket exception on connection [connectionId{localValue:43}] to 172.16.199.96:22001. All connections to 172.16.199.96:22001 will be closed.
02-01 15:11:47 INFO  - Closed connection [connectionId{localValue:43}] to 172.16.199.96:22001 because there was a socket exception raised by this connection.
        org.springframework.data.mongodb.UncategorizedMongoDbException: Exception receiving message; nested exception is com.mongodb.MongoSocketReadException: Exception receiving message
            at org.springframework.data.mongodb.core.MongoExceptionTranslator.translateExceptionIfPossible(MongoExceptionTranslator.java:107)
            at org.springframework.data.mongodb.core.MongoTemplate.potentiallyConvertRuntimeException(MongoTemplate.java:2135)
            at org.springframework.data.mongodb.core.MongoTemplate.executeFindMultiInternal(MongoTemplate.java:1978)
            at org.springframework.data.mongodb.core.MongoTemplate.doFind(MongoTemplate.java:1784)
            at org.springframework.data.mongodb.core.MongoTemplate.doFind(MongoTemplate.java:1767)
            at org.springframework.data.mongodb.core.MongoTemplate.find(MongoTemplate.java:641)
            at org.springframework.data.mongodb.core.MongoTemplate.findOne(MongoTemplate.java:606)
            at org.springframework.data.mongodb.core.MongoTemplate.findOne(MongoTemplate.java:598)
            at com.xxx.xxx.xxx.xxx(xxxService.java:46)
            at com.xxx.xxx.xxx.xxx(xxxService.java:157)
            at com.xxx.xxx.xxx.xxx(xxxService.java:142)
            at com.xxx.xxx.xxx.xxx(xxxService.java:87)
            at com.alibaba.dubbo.common.bytecode.Wrapper2.invokeMethod(Wrapper2.java)
            at com.alibaba.dubbo.rpc.proxy.javassist.JavassistProxyFactory$1.doInvoke(JavassistProxyFactory.java:46)
            at com.alibaba.dubbo.rpc.proxy.AbstractProxyInvoker.invoke(AbstractProxyInvoker.java:72)
            at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)
            at com.alibaba.dubbo.rpc.filter.ExceptionFilter.invoke(ExceptionFilter.java:64)
            at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
            at com.alibaba.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:75)
            at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
            at com.alibaba.dubbo.rpc.filter.TimeoutFilter.invoke(TimeoutFilter.java:42)
            at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
            at com.alibaba.dubbo.rpc.protocol.dubbo.filter.TraceFilter.invoke(TraceFilter.java:78)
            at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
            at com.alibaba.dubbo.rpc.filter.ContextFilter.invoke(ContextFilter.java:61)
            at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
            at com.alibaba.dubbo.rpc.filter.GenericFilter.invoke(GenericFilter.java:132)
            at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
            at com.alibaba.dubbo.rpc.filter.ClassLoaderFilter.invoke(ClassLoaderFilter.java:38)
            at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
            at com.alibaba.dubbo.rpc.filter.EchoFilter.invoke(EchoFilter.java:38)
            at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)
            at com.alibaba.dubbo.rpc.protocol.dubbo.DubboProtocol$1.reply(DubboProtocol.java:100)
            at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.handleRequest(HeaderExchangeHandler.java:98)
            at com.alibaba.dubbo.remoting.exchange.support.header.HeaderExchangeHandler.received(HeaderExchangeHandler.java:170)
            at com.alibaba.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:52)
            at com.alibaba.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:81)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
            at java.lang.Thread.run(Thread.java:748)
        Caused by: com.mongodb.MongoSocketReadException: Exception receiving message
            at com.mongodb.connection.InternalStreamConnection.translateReadException(InternalStreamConnection.java:483)
            at com.mongodb.connection.InternalStreamConnection.receiveMessage(InternalStreamConnection.java:228)
            at com.mongodb.connection.UsageTrackingInternalConnection.receiveMessage(UsageTrackingInternalConnection.java:96)
            at com.mongodb.connection.DefaultConnectionPool$PooledConnection.receiveMessage(DefaultConnectionPool.java:440)
            at com.mongodb.connection.CommandProtocol.execute(CommandProtocol.java:112)
            at com.mongodb.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:168)
            at com.mongodb.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:289)
            at com.mongodb.connection.DefaultServerConnection.command(DefaultServerConnection.java:176)
            at com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:216)
            at com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:207)
            at com.mongodb.operation.CommandOperationHelper.executeWrappedCommandProtocol(CommandOperationHelper.java:113)
            at com.mongodb.operation.FindOperation$1.call(FindOperation.java:516)
            at com.mongodb.operation.FindOperation$1.call(FindOperation.java:510)
            at com.mongodb.operation.OperationHelper.withConnectionSource(OperationHelper.java:431)
            at com.mongodb.operation.OperationHelper.withConnection(OperationHelper.java:404)
            at com.mongodb.operation.FindOperation.execute(FindOperation.java:510)
            at com.mongodb.operation.FindOperation.execute(FindOperation.java:81)
            at com.mongodb.Mongo.execute(Mongo.java:836)
            at com.mongodb.Mongo$2.execute(Mongo.java:823)
            at com.mongodb.DBCursor.initializeCursor(DBCursor.java:870)
            at com.mongodb.DBCursor.hasNext(DBCursor.java:142)
            at org.springframework.data.mongodb.core.MongoTemplate.executeFindMultiInternal(MongoTemplate.java:1964)
            ... 37 common frames omitted
        Caused by: java.net.SocketException: Connection reset
            at java.net.SocketInputStream.read(SocketInputStream.java:210)
            at java.net.SocketInputStream.read(SocketInputStream.java:141)
            at com.mongodb.connection.SocketStream.read(SocketStream.java:85)
            at com.mongodb.connection.InternalStreamConnection.receiveResponseBuffers(InternalStreamConnection.java:494)
            at com.mongodb.connection.InternalStreamConnection.receiveMessage(InternalStreamConnection.java:224)
            ... 57 common frames omitted

**java版本1.8。

Spring Boot 版本1.5.3。
与坞站一起部署。**

mongo.hosts=ip:port,ip:port,ip:port
mongo.database.name=dbname
mongo.username=username
mongo.password=pwd
mongo.connections.per.host=32
mongo.max.wait.time=2000
mongo.connect.timeout=2000
docker

2条答案

按热度按时间
k10s72fa

k10s72fa1#

您可以尝试，autoConnectRetry表示驱动程序在意外断开连接后将自动尝试重新连接到服务器。在生产环境中，您通常希望将此设置为true。
这是来自另一篇文章How to configure MongoDB Java driver MongoOptions for production use?

赞(0）分享  回复(0）举报  2022-12-18
7gs2gvoe

7gs2gvoe2#

对于遇到相同随机MongoSocketReadException的每个人，您可能需要socketTimeoutMS或maxIdleTimeMS参数，参数autoConnectRetry不再暴露在mongodb连接字符串中。
我方情况：我们切换到mongodb atlas无服务器的解决方案为我们的开发和测试环境，从那时起，我们得到了这个MongoSocketReadException喜欢每15分钟。或随机。我们也背后的企业防火墙。
根据https://www.mongodb.com/docs/v6.0/tutorial/connection-pool-performance-tuning/：
配置错误的防火墙会错误地关闭套接字连接，并且驱动程序无法检测到该连接是否被错误地关闭。2您需要=〉使用socketTimeoutMS来确保套接字始终关闭。3将socketTimeoutMS设置为驱动程序运行的最慢操作长度的两到三倍。
因为socketTimeoutMS默认为0，它永远不会超时。
另一个参数maxIdleTimeMS也会影响连接，因为如果套接字关闭，而客户端没有检测到它，则连接仍将在空闲时间等待，而不会关闭。默认值为0，表示它将永远等待，没有上限。
因此，将其配置为一个小的数量可能有助于驱动程序在尝试使用相同的连接连接到数据库并假定连接仍然存在之前，使用其关闭的套接字关闭有问题的连接。
所以我们的解决方案是：...mongodbUri...?socketTimeoutMS=150000&maxIdleTimeMS=150000
我们将socketTimeoutMS从0更改为15s，maxIdleTimeMS也是如此。

赞(0）分享  回复(0）举报  2022-12-18
我来回答

相关问题

    查看更多

    热门标签

    更多
    JavaquerypythonNode开发语言requestUtil数据库Table后端算法LoggerMessageElementParser

    最新问答

    更多
    • 蜀ICP备2022004421号-2 NULL123 https://www.null123.com © All rights reserved
    • 本站内容来源互联网,如果侵犯您的权益请联系我们删除, 联系方式：448109455@qq.com