We have a Spring project that has a unit test annotated @Transactional.
This uses a DAO to save a sample Entity before invoking a Camel route that
accepts a JMS message and sends it to some Processors.

The problem we have is when the test itself is annotated @Transactional.
The route stops having received the message and begin performing a database
query - it literally hangs performing the SELECT. Naturally after 20s the
time-out is hit.

If we remove @Transactional from the test the route continues but finds
nothing in the database as the initial Entity save had no effect (it
appears).

So we're clearly missing something here - how should we seed test data if
@Transactional hangs and without it the data is not committed?

Thanks,

James

Reply via email to