[ https://issues.jboss.org/browse/TEIIDDES-1813?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1813: ------------------------------------------- Identified race condition between the DqpPlugin bundle starting and the org.eclipse.wst.server.core ResourceManager. On startup, the ServerCore class is responsible for initialising the JBoss servers listed in the Servers view. It hands-off to its ResourceManager which calls its init() method. However, this method is not protected in any way so that if subsequent calls are made to it, while it is initialising then it simply returns. Thus, calls to ServerCore.getServers() returns empty while ServerCore is being initialised. The DqpPlugin adds the TeiidParentServerListener instance to each JBoss server on startup. However, if the ResourceManager is in the middle of initialising, it actually adds the listener to nothing since the servers collection returned from ServerCore is empty. Likewise, any part of the UI (such as the ServerStatusPanel in the Model Explorer) that requires the TeiidServerManager will fail to initialise correctly. Since the TeiidServerManager is initialised and restored on startup, it requires ServerCore's servers to set as parents on the saved TeiidServers. If there are no parent servers then the TeiidServers are orphaned and never added to the manager's own server collection. Thus, no TeiidServers are available even though the JBoss Servers are initialised correctly in the Servers view. Thus, it is necessary to delay anything involving ServerCore's servers until its ResourceManager has correctly initialised its server collection. -- 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