]
Rob Stryker commented on JBIDE-19854:
-------------------------------------
I do see that the wrong separator is being used in some of the args, but I'm not sure
if that could be the root cause or not. More investigation needed.
When Wildfly starts in debug mode occurs ClassNotFoundException with
org.jboss.modules.Main
-------------------------------------------------------------------------------------------
Key: JBIDE-19854
URL:
https://issues.jboss.org/browse/JBIDE-19854
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Environment: OS: Windows 8.1; Intel Core i3 540 3.07Ghz; 4GB DDR3 1333Mhz; Java
Version 1.7.0_75;
Reporter: Giancarlo giulian
Labels: classnotfound, debug, debugging, jboss, main, wildfly
Fix For: 4.3.x
Attachments: image2.png, image3.png, imagem1.png
This problem has recently begun, before that is it working in debug mode. Errors log are
not created and doesn't appear in console output using Eclipse Luna.
Program Arguments:
{quote}
-mp "C:/wildfly-8.1/modules" -jaxpmodule javax.xml.jaxp-provider
org.jboss.as.standalone -b localhost --server-config=standalone.xml
-Djboss.server.base.dir=C:\wildfly-8.1\standalone
{quote}
VM Arguments:
{quote}
"-Dprogram.name=JBossTools: WildFly 8.1" -server -Xms64m -Xmx512m
-XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
"-Dorg.jboss.boot.log.file=C:/wildfly-8.1/standalone/log/boot.log"
"-Dlogging.configuration=file:/C:/wildfly-8.1/standalone/configuration/logging.properties"
"-Djboss.home.dir=C:/wildfly-8.1" -Dorg.jboss.logmanager.nocolor=true
-Djboss.bind.address.management=localhost
{quote}
Images:
https://www.dropbox.com/s/g0hdwh1tz543q1p/imagem1.png
https://www.dropbox.com/s/ivpnd3ggaprtl2v/image2.png