[JAVA-1534] com.mongodb.DBPortPool gotError WARNING: emptying DBPortPool to /ip:port b/c of error Created: 06/Nov/14 Updated: 11/Sep/19 Resolved: 07/Nov/14 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Connection Management |
| Affects Version/s: | 2.11.4 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Claire Lee | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | com.mongodb.DBPortPool, connection, socket | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
mongo-java-driver-2.11.4.jar, Java 8, Tomcat 8, MongoDB 2.6.3 |
||
| Description |
|
My JAVA application is run on Tomcat Server with a single MongoDB. This error occurs some times a day.
MongoClientOptions options = MongoClientOptions.builder() This issue is really worrying..Please, help me. |
| Comments |
| Comment by Ross Lawley [ 27/Jan/15 ] |
|
Hi huoyingoo this ticket has been closed. Please can you post your question to the mongodb user forum. It's a better place for your question and hopefully you'll get the answers you need there. Please remember to provide as much information as you can eg what driver version, mongodb version etc.. Regards, Ross |
| Comment by huoyingoo [ 27/Jan/15 ] |
|
I have met this exception too.and can not find some solution,while i open a page for a long time and no operation,and then request the connection to mongodb,it's probably happend.but the service not down,refresh the page,it's working normally. it seems that after the mongodb server closed the a long connection,and mongo-java-driver dont know the current socket has been closed? |
| Comment by Jeffrey Yemin [ 07/Nov/14 ] |
|
Connection reset is a confusing message, but I can almost guarantee you that it's not something that the driver itself is responsible for. Something is going on between your application and the MongoDB server its connected to that is resetting the socket. I'm going to close this issue unless you have any other questions about the driver itself. In the future, please consider asking these types of questions in our user forum. Thanks, |
| Comment by Claire Lee [ 06/Nov/14 ] |
|
Thank you for this comment. I cloned this issue mistakenly and it resulted in creating the issue ( |
| Comment by Jeffrey Yemin [ 06/Nov/14 ] |
|
The is due to a network error, as evidenced by the "SocketException: Connection reset". This socket exception occurred while executing a count command against the server. The most common cause is that the MongoDB server (or a router sitting between the application and the MongoDB server) closed the connection. This can happen, for example, if the MongoDB server is restarted. I suggest checking the server logs to see if you can find any correlating messages at the time of the log message in the Tomcat application. |