Java-574 New SemaphoresOut constructor accepting int which caller can define number of allowed permits.
Merge branch 'ExceptionMessaging'
2.9.2-SNAPSHOT prep
fixed findAndModifyTest under 2.0.7
Reverting to correct mongod port
JAVA-656: Don't checkMaster on slaveOk queries
JAVA-656: Don't checkMaster on slaveOk queries
JAVA-658: Making ReadPreference.primary == ReadPreference.primary() so that it's safe to do equality comparision
JAVA-652: Synchronizing on correct object in close method
JAVA-658: Making ReadPreference.primary == ReadPreference.primary() so that it's safe to do equality comparision
JAVA-652: Synchronizing on correct object in close method
Fixed up write concerns in secondaryReadTest
JAVA-660: Took call to OutMessage.doneWithMessage out of the recursively-called method, to avoid having it called more than once.  Protected OutMessage by setting the buffer to null and checking for null everywhere it's used.
JAVA-666, JAVA-641: Created two subclasses of DBPortPool: MongoConnectionPool and Java5MongoConnectionPool.  The former is an MBean and the latter is an MXBean.  When creating a DBPortPool, conditionally create one or the other depending on whether java.version system property indicates that this is a 1.5 virtual machine.  This should avoid JXM registration errors when running on Java 5 VMs. Also, by using MongoConnectionPool as the name of the MXBean, avoids incompatibilities in JMX implementations that require the MXBean name to be the same as the MXBean interface that it implements (minus the MXBean suffix).
Added serialVersionUID to MongoInterruptedException
Added upload of sources and javadoc for snapshot deployment
JAVA-660: Took call to OutMessage.doneWithMessage out of the recursively-called method, to avoid having it called more than once.  Protected OutMessage by setting the buffer to null and checking for null everywhere it's used.
JAVA-666, JAVA-641: Created two subclasses of DBPortPool: MongoConnectionPool and Java5MongoConnectionPool.  The former is an MBean and the latter is an MXBean.  When creating a DBPortPool, conditionally create one or the other depending on whether java.version system property indicates that this is a 1.5 virtual machine.  This should avoid JXM registration errors when running on Java 5 VMs. Also, by using MongoConnectionPool as the name of the MXBean, avoids incompatibilities in JMX implementations that require the MXBean name to be the same as the MXBean interface that it implements (minus the MXBean suffix).
Updating to 2.10.0-SNAPSHOT
Updating to 2.10.0-SNAPSHOT