[
https://issues.apache.org/jira/browse/OOZIE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695808#comment-13695808
]
Alejandro Abdelnur commented on OOZIE-1434:
-------------------------------------------
if the jdbc driver does not support it, then it should be something to
configure on the SQLServer itself, if not there either, then there is no
control from our side.
> Commands not releasing memory lock
> ----------------------------------
>
> Key: OOZIE-1434
> URL: https://issues.apache.org/jira/browse/OOZIE-1434
> Project: Oozie
> Issue Type: Bug
> Reporter: Virag Kothari
> Assignee: Virag Kothari
>
> If the command gets stuck in making a db call during loadState() after
> acquiring the lock, the lock will never be released and the job will be stuck
> forever.
> Need to introduce a timeout for the database call.
> There might be also be an issue with the implementation of MemoryLocks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
