-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mongo 3.0 support? #131
Comments
Hi at the moment I have no plan on upgrading. But yes please feel free to fork and send me pull request if you can get it done |
We're running this library in production with Mongo 3 and the wiredTiger storageEngine... we've noted no problems so far (other than Robomongo not working with it) |
@shoon how's your dependencies.yml? Mine is as follows, and its not working: require: repositories: Thanks in advance! |
in my case i cant even connect to mongodb. 16:56:55,896 WARN ~ You're running Play! in DEV mode @6ndh6mnd0 Oops: RuntimeException play.exceptions.UnexpectedException: Unexpected Error @6ndh6mnd1 Oops: RuntimeException play.exceptions.UnexpectedException: Unexpected Error |
Your code failed at here: if (!S.empty(username) && !S.empty(password)) {
if (!db.isAuthenticated() && !db.authenticate(username, password.toCharArray())) {
throw new RuntimeException("MongoDB authentication failed: " + dbName);
}
} Question have you configured the username password correctly? |
I think it might be the new authentication scheme in 3.0... Try setting this to go back to the old authentication. I just tried it on an auth database and it worked (users were created after the change)
Here's a discussion about this: |
.. and my deps: I'm using the latest play1 from the 1.3x branch mongo driver updated from this pull: |
+1 |
Hi, there's any intention of upgrading this library to support mongo 3.0 ?
I'll be pleased to help in that update.
The text was updated successfully, but these errors were encountered: