It's useful in the specific context of the logged message, as it would reproduce it.

Still, yes you're right that it is not asserting against the logged message to happen: I included it anyway as we apparently where not having tests to verify that the massindexer would work fine from a JPA API..

It would be nice to develop a general purpose strategy to verify that something is being logged (or not), but in the context of this JIRA I merely wanted to track the issue (as it was reported via forums) and verify that _master_ is not affected. As a side effect, we include a nice new JPA test which was missing ;-)