[ 
https://issues.apache.org/jira/browse/HIVE-15002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586331#comment-15586331
 ] 

Zoltan Haindrich edited comment on HIVE-15002 at 10/18/16 6:57 PM:
-------------------------------------------------------------------

[~taoli-hwx]
1: i've attached a stacktrace of an affected proccess, I think this caused it.
2: there were two usages of that variable...and the other one was inside the 
'catch' block...if we get there it doesnt really matter to re-get the 
operationManager - and this way I didn't left any method invocations outside: 
in the "non-protected" zone - I can put it back if you think it makes it better 
;)


was (Author: kgyrtkirk):
[~taoli-hwx]
1: i've attached a stacktrace of an affected proccess, I think this caused it.
2: there were two usages of that variable...and the other one was inside the 
'catch' block...if we get there it doesnt really matter to re-get the 
operationManager - and this way I didn't left any method invocations outside: 
in the "non-protected" zone.

> HiveSessionImpl#executeStatementInternal may leave locks in an inconsistent 
> state
> ---------------------------------------------------------------------------------
>
>                 Key: HIVE-15002
>                 URL: https://issues.apache.org/jira/browse/HIVE-15002
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>         Attachments: HIVE-15002.1.patch, stacktrace.txt
>
>
> {{TestEmbeddedThriftBinaryCLIService}} have showed me this behaviour.
> Thrift service may hang because of this issue.
> {{TestEmbeddedThriftBinaryCLIService}} can reproduce this problem with a very 
> bad probability...but I was able to 
> Its not able to aquire the semaphore; because most probably because an 
> earlier command have produced an SQLException in the unprotected parts.



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

Reply via email to