[ https://jira.jboss.org/browse/TEIID-1006?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy reassigned TEIID-1006: ----------------------------------- Assignee: Ramesh Reddy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-1006?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy resolved TEIID-1006. --------------------------------- Resolution: Done During the deployment of the VDB, if deployer sees the VDB as dynamic VDB and it does not have cached metadata, deployer will invoke fetching of the metadata in separate thread for each source. The VDB status will be set to "inactive" during the fetching. Once all the threads are done, then the status is changed to "active", then connections to the VDB are allowed. The Admin API functionality is omitted currently for later as there is work around for this. The work around is redeploy the VDB or start the re-start the server with the "cache" flag not set. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira