[jira] [Commented] (GEODE-890) CompiledLike member variables are not thread safe

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on GEODE-890:
-------------------------------------------------------

Commit 09c0c8dd8bc9d83392e53fbb92aee7e45317de1d in incubator-geode's branch refs/heads/develop from [~huynhja]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=09c0c8d ]

GEODE-890:CompiledLike member variables are not thread safe

Member variables in CompiledLike need to be thread safe.
Added the member variables into the execution context, this should
prevent threads/queries from sharing these variable values and
prevent a possible stack overflow/ infinite loop from occuring.

Added a Multithreaded test helper and test to reproduce the original issue.


> CompiledLike member variables are not thread safe
> -------------------------------------------------
>
>                 Key: GEODE-890
>                 URL: https://issues.apache.org/jira/browse/GEODE-890
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Jason Huynh
>            Assignee: Jason Huynh
>
> If a compiled like query is used concurrently, for example a bind parameter query from a client), the member variables are not thread safe and can possibly lead to a stack over flow.  
> This is because the CompiledLike is unique in that it creates new junctions when executing and if one of the member variables is set to true at a certain point, can lead to an infinite recursion.
> The fix is to move the member variables into the execution context.



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