[ https://issues.jboss.org/browse/JBIDE-24758?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24758: --------------------------------------- What's worse, when I actually tried to start the server, it still tried to use the old location: The archive: /Users/rasp/tmp/jboss-eap-6.4/jboss-modules.jar which is referenced by the classpath, does not exist. I expected that the server start simply failed - it was an error pop up window. But it keeps Starting, even though there is no output in the console. I had to quit it using the stop button in servers view. I checked again in the server editor and Runtime Environment and it shows the correct path there. So something is fishy. I then tried to go through Behavior Profile and just clicked Finish, hoping that this would reset the server and it would work now. But no, the server still won't start. If I go to Preferences -> Server -> Runtimes and then Edit on the runtime, it contains the correct path. So I think it must be some kind of caching problem. I restarted the IDE and it still fails. Again, I checked that the runtime has the correct path. And now I also checked the launch config. And that seems ok too - these are the calculated arguments, all containing the correct path: {code} -mp "/Users/rasp/jbossqa/runtimes/jboss-eap-6.4/modules" -jaxpmodule javax.xml.jaxp-provider -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=/Users/rasp/jbossqa/runtimes/jboss-eap-6.4/standalone {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)