[JAVA-619] null write concern should throw IllegalArgumentException for all methods that take one Created: 14/Aug/12 Updated: 29/Aug/12 Resolved: 14/Aug/12 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | API |
| Affects Version/s: | None |
| Fix Version/s: | 2.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Passing a null write concern to any update method causes the connection pool to be emptied, due to an NPE thrown in DBTCPConnector.say when dereferencing the write concern and the subsequent exception handling. Should fix this by throwing IllegalArgumentException from all public update methods that take a write concern if the write concern is null. |
| Comments |
| Comment by Jeffrey Yemin [ 29/Aug/12 ] |
|
Closing as part of 2.9.0 release process. |
| Comment by auto [ 14/Aug/12 ] |
|
Author: {u'date': u'2012-08-14T06:31:01-07:00', u'name': u'Jeff Yemin', u'email': u'jeff.yemin@10gen.com'}Message: |