It seems that the AbstractDatabaseManager behavior is now to close the connection after the buffer is flushed (or immediately after a write if there is no buffer). These are the calls to commitAndClose().
The intended behavior for close() is that it would return a connection to the connection pool. That would make sense for most good database drivers.
However, the MongoDBProvider simply closes the MongoClient, releasing the entire pool. This means that further attempts to write to the log, after the first time, will fail.
|Field||Original Value||New Value|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||2.0-rc2 [ 12326292 ]|
|Assignee||Matt Sicker [ jvz ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|4d 12h 24m||1||Matt Sicker||06/Apr/14 04:36|