Max, Thanks for creating the JIRA entry. I'm adding the VM argument to the JBoss AS launcher. I've opened a JBoss Server View provided by JBoss Tools. I right-click on my server, edit launch configuration, then add the option to the VM arguments tab. This got me past the IPv6 issue, but the issue mentioned above regarding jboss-service.xml still remains. Like the IPv6 issue, this issue occurs only when launching JBoss 4.2 Enterprise Application Platform from within Eclipse with JBoss Tools. Launching from command line with run.sh starts successfully with no errors. I'm still looking for other interesting behavior in run.sh that might somehow be responsible for the difference. It may also be important to note that starting JBoss AS 4.2.0.GA from within Eclipse with JBoss Tools works just fine. The problem happens only when starting JBoss 4.2 Enterprise Application Platform from within Eclipse with JBoss Tools. One difference is I installed JBoss 4.2.0.GA from the zip, but I used enterprise-installer-4.2.0-1.ep1.1.jar to install the Enterprise Application Platform, including securing the web console and the like. ...in case that matters... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063118#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...