[ https://issues.jboss.org/browse/JBIDE-15191?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15191: ------------------------------------- org.jboss.ide.eclipse.as.classpath.core.runtime.CustomRuntimeClasspathModel$PathProviderFileset.getAbsolutePaths(CustomRuntimeClasspathModel.java:62) We can see that it's not really project archives. It's just a fileset that we use to determine what jars to include on the classpath. This really shouldn't take very long. This may depend on what verison of the app-server you're using, but in general, this should be a fairly quick operation. It does need to traverse the entire tree of the app-server (I believe. It's possible its more efficient than that, but I'm going to assume it's not). I can do some informal speed tests later on, but not at the moment. This line, however, in the other thread: at org.jboss.ide.eclipse.as.core.server.bean.ServerBeanLoader.getServerBean(ServerBeanLoader.java:51) Also should not be taking very long. I fully admit it's possible that there is a bit of inefficiency in the server bean loader, but, in general, the operation is fairly quick. Each jboss server bean type basically looks only at specific jars that they use to find properties. Even considering that there are 15 server bean types, and each type might check 3 or 4 jars, that's still only through 60 jars or so. Certainly not enough to freeze eclipse. Also both threads are marked runnable, Neither are blocked or waiting on a lock. One thread has acquired a lock, but the other thread is not at all involved with, or even knows about, any of those objects, and cannot possibly be interfering there. I'm going to push this to 4.2.0, but there certainly does NOT seem to be a deadlock going on here at all, so it's possible the user just didn't wait long enough? Without more information from the user, I really can't know. I can try to run some perf tests, but I think it's obvious from the thread-dump that the two threads are NOT interfering with each other at all. -- 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