[
https://issues.apache.org/jira/browse/LUCENE-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623437#action_12623437
]
Otis Gospodnetic commented on LUCENE-1358:
------------------------------------------
It sounds like you are simply demonstrating an old bug, right? If so, then we
can close this issue, since LUCENE-1346 fixed the bug you described (I didn't
verify that).
> Deadlock for some Query objects in the equals method (f.ex. PhraseQuery) in a
> concurrent environment
> ----------------------------------------------------------------------------------------------------
>
> Key: LUCENE-1358
> URL: https://issues.apache.org/jira/browse/LUCENE-1358
> Project: Lucene - Java
> Issue Type: Bug
> Components: Other
> Affects Versions: 2.3.2
> Reporter: Torbjørn Køhler
> Priority: Minor
> Attachments: TestDeadLock.java
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Some Query objects in lucene 2.3.2 (and previous versions) have internal
> variables using Vector. These variables are used during the call to the
> equals method. In a concurrent environment a deadlock might occur. The
> attached code example shows this happening in lucene 2.3.2, but the patch in
> LUCENE-1346 fixes this issue (though that doesn't seem to be the intention of
> that patch according to the description :-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
