Excepion when running multiple tests using MongoDbRule + Spring+Real remote Mongo Db+ CLEAN_INSERT Strategy about nosql-unit HOT 10 CLOSED

I will try to do today, if I finish one thing :) if not then hope that during this week. Sorry :)

from nosql-unit.

Any updates on this? :(

from nosql-unit.

No idea, why this is happening in this case, notice that for example here https://github.com/lordofthejars/nosql-unit/blob/master/nosqlunit-demo/src/test/java/com/lordofthejars/nosqlunit/demo/mongodb/WhenYouFindAllBooks.java I am using two tests. Can you debug https://github.com/lordofthejars/nosql-unit/blob/master/nosqlunit-mongodb/src/main/java/com/lordofthejars/nosqlunit/mongodb/MongoOperation.java tocheck what is happening to MongoClient?

from nosql-unit.

The connection to Mongo obtained from Spring, is closed in AbstractNoSqlTestRule#apply()'s finally block, after the first test method has run. So subsequent attempts to insert data in following tests failed because the connection is closed (in fact, there is a safety assertion: isTrue("open", !isClosed()); in Mongo impl. to ensure that).

In your example, the second test method use the DELETE_ALL strategy (and not a CLEAN_INSERT or INSERT as in my use case): so there is no 2nd attempt to insert data in the db, just a deletion.

Besides, your are using a newMongoDbRule().defaultEmbeddedMongoDb()
to get the MongoDbRule, which internally used a inMemoryMongoDb Fongo implementation (not a real remote db as in my use case...).

As i have mentioned, the Fongo implementation works great, simply because there is no isTrue("open", !isClosed()); assertion as in the Mongo's.

from nosql-unit.

I see, I think that the problem happens because of Spring integration, because then the Mongo Client is started by Spring but closed by NoSQLUnit. I will need to figure out if there is a way to detect this

from nosql-unit.

Yep. Maybe SpringMongoDbRule should override close() to do nothing... and let Spring manage the closing when destroying the context at the end of the tests?

That's the workaround i've implemented for my tests...

from nosql-unit.

Yes I think this is right. Can you provide a PR?

from nosql-unit.

Sure, i will push it tonight

from nosql-unit.

Hello @lordofthejars

when is this fix to be expected to be included into a release?

from nosql-unit.

The change does not exist in the latest release of the maven:
https://mvnrepository.com/artifact/com.lordofthejars/nosqlunit-mongodb/1.0.0-rc.5 and it dates back to more than a year ago.
Is there any more recent repository for maven artifacts ?

from nosql-unit.