[ https://issues.jboss.org/browse/TEIID-2526?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2526. --------------------------------- Labels: CR2 (was: ) Resolution: Done Since OData is web based application + it does not have any session affinity it is ignorant of the VDB reloads, thus the original issue. There is clean way do this unless there is some kind event monitoring we can listen on. The solution is elected does check the metadata store of the VDB every "skiptoken-cache-time" which is defaulted at 5 mins to refresh to the updated metadata. The user always has option to re-cycle the server to get to the updated metadata immediately. The same skiptoken value is also used for results cursoring when using OData. The skiptoken out value is also configurable. Since VDB reloads are not common in the runtime environments, this should be acceptable solution -- 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