[jboss-jira] [JBoss JIRA] Commented: (JBAS-3399) Transaction timeout fires too late

[tbech (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3399?page=comments#action_12343565 ] 
            
tbech commented on JBAS-3399:
-----------------------------

>>  Its only going to throw an error if you access a transacted resource 
and
>> Doesn't matter what timeout is set, server does whole job (few hours even) and at the end throws exception. Shouldn't container:
>> a) throw an error after timeout 

What I was saying is:
for long transaction - (lets say 10000 gueries/updates, one after another), the exception is not thrown until commit (and the transacted resource is used all the time in this transaction).
This is a bug, (and you agree - "Its only going to throw an error if you access a transacted resource ", but it doesn't throw an exception). So why rejected?


> Transaction timeout fires too late
> ----------------------------------
>
>                 Key: JBAS-3399
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3399
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Manager
>    Affects Versions: JBossAS-4.0.3 SP1
>            Reporter: tbech
>            Priority: Minor
>
> Transaction timeout is fired in the 'commit' probably. It is far too late in order to really limit the transaction.
> Scenario:
> - do long job in transaction (CMT);
> - job is finished;
> - commit;
> - timeout exception is thrown;
> Doesn't matter what timeout is set, server does whole job (few hours even) and at the end throws exception. Shouldn't container:
> a) throw an error after timeout 
> b) stop the called EJB method ???

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira