[
https://issues.apache.org/jira/browse/LOG4J2-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423392#comment-17423392
]
Gary D. Gregory commented on LOG4J2-3140:
-----------------------------------------
Is it possible that the connection from Log4j goes stale because it has not
been used in a "long" time. If that is the case, maybe our reconnect logic is
not kicking in when it should. Or, does your app log immediately and this fails
immediately?
> Mongo4 appender stays in TimeOut
> --------------------------------
>
> Key: LOG4J2-3140
> URL: https://issues.apache.org/jira/browse/LOG4J2-3140
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.14.1
> Environment: OpenJDK 11 and 13, Windows 10, IntelliJ, MongoDB 4.4.8,
> mongo-driver-sync 4.3.1.
> Reporter: Marc Segond
> Priority: Major
> Labels: MongoDB, log4j2, mongodb4
>
> I have configured a Mongo4 Appender for logging into my MongoDB Atlas Cluster.
> I have the mongo-driver-sync 4.3.1 in my pom.xml, and I use a connection
> string of type:
> |mongodb+srv://<username>:<password>@myproject.ne6as.mongodb.net/myFirstDatabase?retryWrites=true&w=majority|
> When my app tries to log, the mongodb connection keeps stalling in the
> 30000ms timeout waiting for the cluster description.
> The strange thing is that my app does other things with this very same
> MongoDB, so I have coded a MongoDBService class that handles the connection
> etc...and my code works perfectly using the same driver and the same
> connection string: no "waiting for cluster description"...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
