[
https://issues.jboss.org/browse/JBIDE-11283?page=com.atlassian.jira.plugi...
]
Leo Breuss updated JBIDE-11283:
-------------------------------
Description:
The remote path to jboss-modules.jar is rewritten with the wrong filepath separator.
Source platform is Eclipse 3.7 on Windows 7
Remote platform is Linux (CentOS 6.2)
Remote Home is "/opt/jboss-as/"
In der Server view, double clicking the remote server, Open Launch Configuration. Last tab
Remote Launch shows a start command (Automatically Calculated by default) which has an
invalid remote path with backslashes for the jboss-modules.jar:
... -jar \opt\jboss-as\jboss-modules.jar ...
The full start command:
java -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dorg.jboss.resolver.warning=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=/opt/jboss-as/standalone/log/boot.log"
"-Dlogging.configuration=file:/opt/jboss-as/standalone/configuration/logging.properties"
"-Djboss.home.dir=/opt/jboss-as" -jar \opt\jboss-as\jboss-modules.jar -mp
"/opt/jboss-as/modules" -jaxpmodule javax.xml.jaxp-provider
org.jboss.as.standalone&
The arguments to the class org.jboss.as.standalone are omitted. In the tag Arguments
(possibly to a local instance) it has a custom binding and configuration: " -b
192.168.187.130 --server-config=standalone-full.xml ".
Not sure, if my proposal is appropriate: The standalone.sh/.bat could be called instead of
this long start command.
was:
The remote path to jboss-modules.jar is rewritten with the wrong filepath separator.
Source platform is Eclipse 3.7 on Windows 7
Remote platform is Linux (CentOS 6.2)
Remote Home is "/opt/jboss-as/"
In der Server view, double clicking the remote server, Open Launch Configuration. Last tab
Remote Launch shows a start command (Automatically Calculated by default) which has an
invalid remote path with backslashes for the jboss-modules.jar:
... -jar \opt\jboss-as\jboss-modules.jar ...
The full start command:
java -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dorg.jboss.resolver.warning=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=/opt/jboss-as/standalone/log/boot.log"
"-Dlogging.configuration=file:/opt/jboss-as/standalone/configuration/logging.properties"
"-Djboss.home.dir=/opt/jboss-as" -jar \opt\jboss-as\jboss-modules.jar -mp
"/opt/jboss-as/modules" -jaxpmodule javax.xml.jaxp-provider
org.jboss.as.standalone&
Workaround Description: copy the Automatically Calculated start command, uncheck the
mark and modify the wrong path. Add the missing " -b 192.168.187.130
--server-config=standalone-full.xml " at the (but before the '&'
ampersand of course). (was: copy the Automatically Calculated start command, uncheck the
mark and modify the wrong path.)
Remote Server Launch Configuration, wrong filepath separators in path
to jboss-modules.jar in Automatically Calculated start command
------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-11283
URL:
https://issues.jboss.org/browse/JBIDE-11283
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.Beta2
Environment: Eclipse 3.7 on Windows 7, JBoss Tools 3.3.0 Beta2
Reporter: Leo Breuss
The remote path to jboss-modules.jar is rewritten with the wrong filepath separator.
Source platform is Eclipse 3.7 on Windows 7
Remote platform is Linux (CentOS 6.2)
Remote Home is "/opt/jboss-as/"
In der Server view, double clicking the remote server, Open Launch Configuration. Last
tab Remote Launch shows a start command (Automatically Calculated by default) which has an
invalid remote path with backslashes for the jboss-modules.jar:
... -jar \opt\jboss-as\jboss-modules.jar ...
The full start command:
java -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dorg.jboss.resolver.warning=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=/opt/jboss-as/standalone/log/boot.log"
"-Dlogging.configuration=file:/opt/jboss-as/standalone/configuration/logging.properties"
"-Djboss.home.dir=/opt/jboss-as" -jar \opt\jboss-as\jboss-modules.jar -mp
"/opt/jboss-as/modules" -jaxpmodule javax.xml.jaxp-provider
org.jboss.as.standalone&
The arguments to the class org.jboss.as.standalone are omitted. In the tag Arguments
(possibly to a local instance) it has a custom binding and configuration: " -b
192.168.187.130 --server-config=standalone-full.xml ".
Not sure, if my proposal is appropriate: The standalone.sh/.bat could be called instead
of this long start command.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira