[jboss-jira] [JBoss JIRA] Updated: (JBAS-4002) JBossWorkManager treats ExecutionContext transaction timeout as milliseconds when it should be seconds are per the API

Weston Price (JIRA) jira-events at jboss.com
Sun Jan 21 11:28:52 EST 2007


     [ http://jira.jboss.com/jira/browse/JBAS-4002?page=all ]

Weston Price updated JBAS-4002:
-------------------------------

    Workaround Description: A temporary work around is to pass the appropriate value in milliseconds (ie 60 seconds == 60000). However, this should really be fixed to reflect the correct intent of the API.   (was: A temporary work around is to pass the appropriate value in milliseconds (ie 60 seconds == 6000). However, this should really be fixed to reflect the correct intent of the API. )

> JBossWorkManager treats ExecutionContext transaction timeout as milliseconds when it should be seconds are per the API
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4002
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4002
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Weston Price
>         Assigned To: Weston Price
>             Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1
>
>
> As per the document for ExecutionContext found here
> http://java.sun.com/j2ee/1.4/docs/api/javax/resource/spi/work/ExecutionContext.html
> the transaction timeout is in seconds. The JBossWorkManager incorrectly treats this as milliseconds.

-- 
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

        



More information about the jboss-jira mailing list