"clebert.suconic(a)jboss.com" wrote : Have you looked for this pattern in your code?
|
|
| | try
| | {
| |
| | }
| | catch (Exception e)
| | {
| | transaction.rolllback();
| | // no logs?
| | }
| |
|
| If you want to find the root cause of that exception, you should get some help from someone on JCA.
I don't actually use that type of pattern.
In fact I don't do any explicit transaction management myself. For the MDB, it's container managed (set to REQUIRED).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169935#4169935
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169935
Thanks, Ronald
I'm trying to implement an algorithm for building a chain of objects. I pick a position in the chain, select the most suitable object, insert that object and move on to next iteration. The whole process is a matter of several minutes, and I'm interested in its fastest completion. That's why I don't like the idea of syncing with the DB on each iteration, it is needless and slow in my scenario.
Obviously I couldn't imagine to run against this sort of limitation while choosing jBPM for this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169922#4169922
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169922