[ https://issues.jboss.org/browse/JBIDE-18737?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18737: ------------------------------------- The fix should already be in mars, but it won't make it into our maintenance until Luna SR2. So if this is still replicatable in Mars, then that workaround isn't the issue. I'm assuming these are for servers in local+fs profile and all have runtimes? As far as I can tell, jboss.71.default.ports.properties exists in the built plugin, (as.core) which is the file responsible for creating the xpaths when a new server is added. This is the same plugin that declares the server types, so there's really no chance this plugin is somehow missing from your environment. When a new server is added, my listener first checks the server has a runtime, and then fires a job to create all the xpaths. The job is scheduled with no delay, but of course there can always be a small delay based on when Eclipse decides to execute the job. Have you tried debugging your automated tests to make sure the listener is reached? You could set a breakpoint in org.jboss.ide.eclipse.as.core.extensions.descriptors.XPathModel class on the serverAdded(etc) method. -- This message was sent by Atlassian JIRA (v6.3.8#6338)