[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-2288) "Starting JBoss EAP 6.1+...e Server" stays 0% on Windows

[ https://issues.jboss.org/browse/TEIIDDES-2288?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on TEIIDDES-2288: ----------------------------------------------- Current investigation shows that when the server starts up as.core sends out notification the server is started. Teiid gets that notification, does a call that then blocks. meaning as.core never finishes and thus we have the 0%. What worries me is that one of the thread dumps shows this: org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) at java.lang.Object.wait(Object.java:503) at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192) - locked <0x00000000b3bbab18> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266) - locked <0x00000000b3bbab18> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:100) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) at org.teiid.adminapi.AdminFactory $AdminImpl.getChildNodeNames(AdminFactory.java:933) at org.teiid.adminapi.AdminFactory $AdminImpl.getDeployedResourceAdaptorNames(AdminFactory.java:1026) at org.teiid.adminapi.AdminFactory $AdminImpl.getResourceAdapterNames(AdminFactory.java:1012) at org.teiid.adminapi.AdminFactory $AdminImpl.getTemplatePropertyDefinitions(AdminFactory.java:1154) at org.teiid84.runtime.ExecutionAdmin.refreshTranslators(ExecutionAdmin.java:666) this shows teiid eclipse plugin calling *directly* into as.controller.client which a) should not be happening since we have the as plugins to handling making sure you are using the right client libraries with the right server b) could indicate teiid is using a different set of jars than it should. #b is my guess right now and we might have stumbled into some client lib combo that breaks. [~hisanobu.okuda] can you verify this is just when using "External managed server" ? if it is just external managed, can you say if it fails if you let as.core/eclipse start the server on its own ? (there is a difference in how we detect the server started so i'm wondering if that could make the difference) -- This message was sent by Atlassian JIRA (v6.2.6#6264)