You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lens.apache.org by "Rajat Khandelwal (JIRA)" <ji...@apache.org> on 2016/10/05 07:24:21 UTC

[jira] [Created] (LENS-1345) Deadlock in jdbc query status update

Rajat Khandelwal created LENS-1345:
--------------------------------------

             Summary: Deadlock in jdbc query status update
                 Key: LENS-1345
                 URL: https://issues.apache.org/jira/browse/LENS-1345
             Project: Apache Lens
          Issue Type: Bug
            Reporter: Rajat Khandelwal
            Assignee: Rajat Khandelwal


JDBC query is launched in a thread. On query finish, the thread calls back the query service to update status, which creates a FinishedQuery instance. In the constructor, FinishedQuery is fetching result from the jdbc driver, which waits on the original thread to complete. Basically the thread is waiting for itself. 

In the callback, query context is acquired by the thread, and can't be acquired again. Which means that get calls for this query won't return and will stay blocked. This can end up blocking all the grizzly threads. 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)