[
https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-12403.
---------------------------------
Fix Version/s: 3.3.2
Resolution: Done
This is a clear regression caused by commits to JBIDE-12229. The -server flag was kept in
synch, but in program arguments. It should not have been put in program args, but rather,
in the vm args. This has been fixed and re-tested and works properly.
Cannot start a server with JBT on eclipse Juno
----------------------------------------------
Key: JBIDE-12403
URL:
https://issues.jboss.org/browse/JBIDE-12403
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.4.0.M1
Environment: RHEL6
java -version
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.3) (rhel-1.48.1.11.3.el6_2-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz
http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
Reporter: Len DiMaggio
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.3.2, 3.4.0.M1
To recreate:
1) Install eclipse Juno (eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz)
2) Help->Install New Software - install JBoss tools:
http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
3) Create a new SOA-P 5.3 server runtime
4) Create a new SOA-P server - accept defaults for run config:
"-Dprogram.name=JBossTools: JBossTools: SOA-5.3" -server -Xms256m -Xmx768m
-XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
"-Djava.endorsed.dirs=/jboss/local/redhat_svn/jbds/jbosstools/esb/tests/org.jboss.tools.esb.ui.bot.test/target/requirements/jboss-soa-p-5/jboss-as/lib/endorsed"
5) Attempt to start the server - this error is returned:
JBossTools: JBossTools: SOA-5.3: invalid option -- s
--
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