[
https://issues.apache.org/jira/browse/LENS-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15561908#comment-15561908
]
Hudson commented on LENS-1345:
------------------------------
UNSTABLE: Integrated in Jenkins build Lens-Commit-Java8 #273 (See
[https://builds.apache.org/job/Lens-Commit-Java8/273/])
LENS-1345: Fixing deadlock in jdbc query status update flow (rajatgupta59: rev
9ef7ce73693d039ab5a197b4227c5c09c2efcaa4)
* (edit)
lens-server/src/main/java/org/apache/lens/server/query/QueryExecutionServiceImpl.java
* (edit)
lens-server-api/src/main/java/org/apache/lens/server/api/driver/DriverQueryStatus.java
* (edit)
lens-driver-jdbc/src/test/java/org/apache/lens/driver/jdbc/TestJdbcDriver.java
* (edit)
lens-server/src/test/java/org/apache/lens/server/query/TestQueryService.java
* (edit)
lens-driver-jdbc/src/main/java/org/apache/lens/driver/jdbc/JDBCDriver.java
* (edit)
lens-server/src/test/java/org/apache/lens/server/common/RestAPITestUtil.java
* (edit)
lens-server-api/src/main/java/org/apache/lens/server/api/driver/AbstractLensDriver.java
* (edit)
lens-server-api/src/main/java/org/apache/lens/server/api/query/QueryContext.java
> 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
> Fix For: 2.7
>
> Attachments: LENS-1345.02.patch, LENS-1345.04.patch,
> LENS-1345.05.patch, LENS-1345.06.patch, LENS-1345.07.patch
>
>
> 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)
