[JAVA-1312] mongo-db java driver 2.10.x connection timeout problem Created: 12/Jul/14 Updated: 11/Sep/19 Resolved: 14/Jul/14 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | None |
| Affects Version/s: | 2.10.1 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Critical - P2 |
| Reporter: | Amarnath Bhattacharya | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | driver | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux on WindowsVM,SpringData-MongoDB,MONGO 2.4.x with Replica Set |
||
| Description |
|
I've developed a CMS(Content Management System) with MONGO DB using JAVA,SpringData-MongoDB for one of our client.But in one environment at client premises called Performance Environment I'm getting the error:
According to MONGO document I've reduced the tcp_keepalive_time to 300 seconds(default ws 7200 seconds) at the client machine from where the connection have been made to the MONGO REPLICA set.And also changed the values tcp_keepalive_intvl and tcp_keepalive_probes to increase the TCP acknowledgement frequency and also applied the retry logic but still getting the problem in that environment.This problem is particularly happening in that environment not at QA or UAT. Don't know why? And more over why this problem is occurring with MONGO driver not with JDBC driver for RDBMS? Please help me as things are going worse day by day as we don't have to say to the client as why it is happening? |
| Comments |
| Comment by Amarnath Bhattacharya [ 15/Jul/14 ] |
|
Hi Stephen, Thanks, |
| Comment by Stennie Steneker (Inactive) [ 14/Jul/14 ] |
|
Hi Amarnath, The JAVA project is for reporting bugs or feature suggestions for the MongoDB Java driver. For MongoDB-related support discussion, please post on the mongodb-users group (http://groups.google.com/group/mongodb-user) or Stack Overflow with the mongodb tag. This question looks like a networking/firewall issue, so I would suggest posting a question on ServerFault, a StackExchange community which focuses on server & networking questions. MongoDB team members are active on these community forums, but you will also reach a broader audience who may have experience to help. Since your application code works in your QA/UAT environments but not in the client/production environment, I would start by looking for specific differences in configuration and versions between your environments. In particular I would consider whether the problematic environment has stricter firewall rules or perhaps other networking components such as a load balancer that might interfere with your application connectivity. I'm going to close this issue as it's currently out of scope for the Java driver, but if you learn more specific details to identify & reproduce the issue in the problematic environment please feel free to follow up here. Thanks, |