[ https://issues.jboss.org/browse/TEIID-2322?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2322. ----------------------------------- Fix Version/s: 8.3 Resolution: Done Switched our internal paradigm for tracking reusable executions from node id to something resembling a pool. node ids are generally not sufficient for tracking due to: - concurrent source queries from the same node (this issue) - and the ids are not unique across independent plans (such as using a cached virtual procedure plan within a relational plan) which means that we would could return the wrong executions. Command affinity is likely, but not enforced. Thus the pooling approach means that the ReusableExecution.reset method must be observed as the command may change between usages of the execution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira