[jira] Resolved: (TRANSACTION-6) [transaction] Timeout is not passed in org.apache.commons.transaction.locking.GenericLockManager#lock(Object ownerId, Object resourceId, int targetLockLevel, boolean reentrant, long timeoutMSecs)

["Oliver Zeigermann (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/TRANSACTION-6?page=all ]
     
Oliver Zeigermann resolved TRANSACTION-6:
-----------------------------------------

    Resolution: Fixed

Bug fixed. Thanks for reporting!

> [transaction] Timeout is not passed in org.apache.commons.transaction.locking.GenericLockManager#lock(Object ownerId, Object resourceId, int targetLockLevel, boolean reentrant, long timeoutMSecs)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: TRANSACTION-6
>          URL: http://issues.apache.org/jira/browse/TRANSACTION-6
>      Project: Commons Transaction
>         Type: Bug

>     Versions: 1.1 Final
>  Environment: Operating System: All
> Platform: All
>     Reporter: Mathieu Baudier

>
> The timeOutMSecs argument is not passed in the lock(Object ownerId, Object
> resourceId, int targetLockLevel, boolean reentrant, long timeoutMSecs) method of
> GenericLocakManager, as can be seen below:
> public void lock(Object ownerId, Object resourceId, int targetLockLevel, boolean
> reentrant,
>         long timeoutMSecs) throws LockException {
>     lock(ownerId, resourceId, targetLockLevel, reentrant ?
> GenericLock.COMPATIBILITY_REENTRANT
>             : GenericLock.COMPATIBILITY_NONE, false, globalTimeoutMSecs);
> }
> globalTimeoutMSecs will therefore be used instead. It is set in the constructor
> <init>(int maxLockLevel, LoggerFacade logger, long timeoutMSecs,long
> checkThreshholdMSecs).
> In the case we faced, we were using the <init>(int maxLockLevel, LoggerFacade
> logger) constructor, so the timeout value is always DEFAULT_TIMEOUT (that is
> 30000 ms) and we have no way to configure it externally without changing our own
> code.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org