So the concurrent modification is not a problem and we can safely silence it in our logs?
On Feb 21, 2012, at 11:05 AM, Ludovic Orban wrote:
Actually we have found several places where classes are marked @Transactional and there are methods that aren't involved in transactions.
We are gonna to try to clean them up.
Does this makes sense?
That's fair. Or you can just disable warnAboutZeroResourceTransaction if you don't want to be bothered by those warnings as they're harmless.
In the latter case, you have to make sure Hibernate only uses BTM's connection pool as without it, BTM cannot track what's happening on your DB behind the scene and won't be able to commit or rollback atomically.
I'm not sure I follow you. We configure our entity manager via spring and is wired through to the entity manager via the bitronix.tm.resource.jdbc.PoolingDataSource
So there is really no way for any of the code to get at the db directly.
In that case, you shouldn't worry at all. It's just that I've seen too many times users trying to use BTM with another connection pool like C3P0 and expecting everything to work. That's exactly the reason why this warning was built-in: to make sure that your setup is sane, which seems to be your case.