[
https://issues.jboss.org/browse/JBIDE-26094?page=com.atlassian.jira.plugi...
]
Jan Richter commented on JBIDE-26094:
-------------------------------------
Trying to launch wildfly 12 in debug mode, gets stuck 'starting', the only output
from the server process is
{noformat}Listening for transport dt_socket at address: 34881{noformat}
The debug info from server/startServerAsync
{noformat}Object {status: Object, details: Object}
details: Object {cmdLine: Array(23), workingDir:
"/home/jrichter/Downloads/wildfly-12.0.0.Final/bin", properties: Object}
cmdLine: Array(23) ["/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc…",
"-agentlib:jdwp=transport=dt_socket,server=y,suspen…",
"-Dprogram.name=JBossTools: id", …]
length: 23
0: "/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/bin/java"
1:
"-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=localhost:41881"
2: "-Dprogram.name=JBossTools: id"
3: "-server"
4: "-Xms64m"
5: "-Xmx512m"
6: "-Dorg.jboss.resolver.warning=true"
7: "-Djava.net.preferIPv4Stack=true"
8: "-Dsun.rmi.dgc.client.gcInterval=3600000"
9: "-Dsun.rmi.dgc.server.gcInterval=3600000"
10: "-Djboss.modules.system.pkgs=org.jboss.byteman"
11: "-Djava.awt.headless=true"
12:
"-Dorg.jboss.boot.log.file=/home/jrichter/Downloads/wildfly-12.0.0.Final/standalone/log/boot.log"
13:
"-Dlogging.configuration=file:/home/jrichter/Downloads/wildfly-12.0.0.Final/standalone/configuration/logging.properties"
14: "-Djboss.home.dir=/home/jrichter/Downloads/wildfly-12.0.0.Final"
15: "-Dorg.jboss.logmanager.nocolor=true"
16: "-Djboss.bind.address.management=localhost"
17: "-classpath"
18:
"/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/charsets.jar:/home/jrichter/Downloads/wildfly-12.0.0.Final/jboss-modules.jar"
19: "org.jboss.modules.Main"
20: "-mp"
21: "/home/jrichter/Downloads/wildfly-12.0.0.Final/modules"
22: "org.jboss.as.standalone"
properties: Object {debug.details.host: "localhost", debug.details.type:
"java", debug.details.port: "41881", …}
debug.details.host: "localhost"
debug.details.port: "41881"
debug.details.type: "java"
debug.java.server: "y"
debug.java.suspend: "y"
debug.java.transport: "dt_socket"
workingDir: "/home/jrichter/Downloads/wildfly-12.0.0.Final/bin"
status: Object {severity: 0, pluginId: "unknown", code: 0, …}
code: 0
message: "ok"
pluginId: "unknown"
severity: 0{noformat}
Is the implementation too basic for the server to start, or am I missing something?
Debugging support: Basic Implementation
---------------------------------------
Key: JBIDE-26094
URL:
https://issues.jboss.org/browse/JBIDE-26094
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: stack-server-protocol
Affects Versions: 4.6.0.AM2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.6.0.Final
Allow for basic support for debugging. The two usecases which should be covered are:
1) server/getLaunchCommand
2) server/startServerAsync
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)