[JAVA-2] connection management should take available memory into account Created: 18/Apr/09 Updated: 18/May/09 Resolved: 18/May/09 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Liam Staskawicz | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
It's possible to run into Out Of Memory errors pretty quickly when a Mongo() instance creates multiple connections to the DB and the JVM has been invoked without specifying enough memory. The connection management should ideally take into account the available memory when allocating new connections. In a debug or verbose mode, the driver might indicate that it would have liked to create more connections but couldn't due to memory restrictions. |