[ https://issues.jboss.org/browse/ISPN-2142?page=com.atlassian.jira.plugin.... ] Manik Surtani updated ISPN-2142: -------------------------------- Description: This causes nasty side effects on Query as it listens to write operations and needs to strictly discard those not originating locally. InvocationContext used with the APPLY_STATE command should have local=false. was:This causes nasty side effects on Query as it listens to write operations and needs to strictly discard those not originating locally Assignee: Adrian Nistor (was: Manik Surtani) Affects Version/s: 5.1.5.FINAL Component/s: Querying State transfer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-2142?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2142: -------------------------------- Fix Version/s: 5.2.0.Alpha4 (was: 5.2.0.Alpha3) -- 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

[ https://issues.jboss.org/browse/ISPN-2142?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2142: ----------------------------------- Fix Version/s: 5.2.0.Final -- 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

[ https://issues.jboss.org/browse/ISPN-2142?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-2142: ------------------------------------- Yes Galder this is still relevant because the new ST code still uses CACHE_MODE_LOCAL flag for the put commands during apply state. Maybe we can remove CACHE_MODE_LOCAL flag and add SKIP_INDEXING to avoid the side effect in Query module? Not sure if this is a legal move. -- 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

[ https://issues.jboss.org/browse/ISPN-2142?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-2142: --------------------------------------- The indexing interceptor needs to listen to state transfer events to keep the index in sync with it's owned entries, in the case the index is not shared across all nodes. Using SKIP_INDEXING it would not trigger indexing, but I actually need it to be indexed in this configuration case. Also it interprets the _local_ flag to decide what to do according to configuration options like {code}indexLocalOnly="true"{code} IMHO these options should not be messed by, we rely on them to tell the truth, and not to be hijacked for other purposes. -- 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

[ https://issues.jboss.org/browse/ISPN-2142?page=com.atlassian.jira.plugin.... ] Adrian Nistor edited comment on ISPN-2142 at 9/24/12 5:20 AM: -------------------------------------------------------------- Ok, I'll try to use a remote context then. Is there any particular test that was failing because of this? was (Author: anistor): Ok, I'll try to use a remote context then. -- 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

[ https://issues.jboss.org/browse/ISPN-2142?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2142: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done -- 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