This content has been marked as final.
Show 3 replies
-
1. Re: Seam performance problem with JTA
ggavrilo Apr 14, 2008 5:52 PM (in response to ggavrilo)Why entityRefsToIds is called in case transaction is not rolled back only? BTW, reentrant flag is cleared only if transaction is not rolled back too. Is it correct?
public Object aroundInvoke(InvocationContext ctx) throws Exception { if (reentrant) { return ctx.proceed(); } else { reentrant = true; entityIdsToRefs(ctx); try { return ctx.proceed(); } finally { if (!isTransactionRolledBackOrMarkedRollback()) { entityRefsToIds(ctx); reentrant = false; } } } }
-
2. Re: Seam performance problem with JTA
pmuir May 7, 2008 11:18 AM (in response to ggavrilo)Please file a JIRA issue about the finally.
-
3. Re: Seam performance problem with JTA
pkorros Jun 17, 2008 11:59 AM (in response to ggavrilo)Hi,
I am having the same issue in my application. 40% is spent on looking up the UserTransaction from JNDI (http://www.seamframework.org/Community/PerformanceIssueRegardingTransactioninstance).
Did you filed a JIRA issue for this? could you please post here the issue id so I can track it?
Thanks