Sorry late here.
OptionallyWrapInJTATransaction is not about timeout. It's about
explicitly starting a JTA transaction like a CMT entity bean would to so
that Hibernate ORM does not complain.
On Mon 2013-11-11 17:29, Sanne Grinovero wrote:
in case you get very bored at Devoxx :)
I remember you implementing a quite complex fix for my initial
MassIndexer which involved avoiding the transactions we use from
This is probably more than a year old, but there is a user on the
forums now using 4.4.0.Final and having a suspiciously similar
I've looked into our code, but I'm not understanding how the class
is supposed to prevent the transaction from timing out?
Do you have any idea on the problem?
I recently had to apply some refactoring so I might have introduced a
regression but I need another pair of eyes.