Hi Pinaki, I think the annot 'TransactionAttributeType.REQUIRES' is not feasible here, because the existing transaction would then be used. But this Tx will be rolled back, therefore my actions on task table would be rolled back as well.
Unfortunately I am still not able to reproduce this on my system, but i happens regularly at client site. Therefore I will now got for another approach where as I will maintain the Tasks outside this bean method. Not nice, but hopefully bringing some progress in this issue. Thanks. ----- Kind regards Matthias -- View this message in context: http://openjpa.208410.n2.nabble.com/cursor-prepared-statement-problem-with-WebLogic-10-3-2-tp5724027p5749357.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
