What is the best approach then for a task which might last for 1-6 hours, which
is the case with mine. I have increased the transaction timeout already to 2h,
but yesterday the task stopped after 2h, without raiging any exceptions.
I found the following message in the logs:
anonymous wrote :
Well, I'm not sure this discussion really belongs in the Seam forum, but if all
the work *really* needs to take place in one transaction, there is usually a
programmatic way to set the transaction timeout for the current transaction.
For example: UserTransaction.setTransactionTimeout().
But the outer transaction is always bound to the TransactionTimeout. In
essence I'm just looking for a way so that a method is allowed to run as long
as it needs to to get the job done. Is it possible in seam to run the whole
batch without a transaction?
View the original post :
Most TMs have some kind of transaction timeout if a tx lasts too long. That
might be a problem here.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4051968#4051968
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4051968
