[ https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-12403: ----------------------------------------- The same error happens with EAP 4 and 5. For EAP 6 the error is different: {code} 08:47:46,032 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA-redhat-1 JBAS015801: Invalid option '-server'Usage: ./standalone.sh [args...] where args include: --admin-only Set the server's running type to ADMIN_ONLY causing it to open administrative interfaces and accept management requests but not start other runtime services or accept end user requests. -b=<value> Set system property jboss.bind.address to the given value -b <value> Set system property jboss.bind.address to the given value -b<interface>=<value> Set system property jboss.bind.address.<interface> to the given value -c=<config> Name of the server configuration file to use (default is "standalone.xml") -c <config> Name of the server configuration file to use (default is "standalone.xml") -D<name>[=<value>] Set a system property -h Display this message and exit --help Display this message and exit -P=<url> Load system properties from the given url -P <url> Load system properties from the given url --properties=<url> Load system properties from the given url -S<name>[=<value>] Set a security property --server-config=<config> Name of the server configuration file to use (default is "standalone.xml") -u=<value> Set system property jboss.default.multicast.address to the given value -u <value> Set system property jboss.default.multicast.address to the given value -V Print version and exit -v Print version and exit --version Print version and exit {code} -- 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

[ https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-12403: --------------------------------- Summary: Cannot start a server with JBT on eclipse Juno (was: Cannot start a SOA-P server with JBT on eclipse Juno) -- 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

[ https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi... ] Csaba Toth commented on JBIDE-12403: ------------------------------------ I tried to remove the extra "-server" arguments manually, but the JBT plugin keeps adding them back again. Here is what I tried: 1. I stopped Eclipse (so the configuration stored in memory run-time won't overwrite my changes. 2. I went to my related Eclipse workspace folder. 3. Went to .metadata/.plugins/org.eclipse.debug.core/ 4. Opened up my server's .launch file 5. Manually removed the "-server" argument (it is still there 3 times even after remove it from VM arguments), and saved the file 6. Started Eclipse 7. Started the server The launch file gets overwritten and for some reason JBT annoyingly puts back the "-server arguments. -- 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

[ https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12403: ------------------------------------- The re-addition of the -server argument is due to JBIDE-12229, and is intended. Some users complained that upon changing their VM to a VM that no longer had the proper server libs, the -server flag should be removed. Others suggested that when moving from a JRE that did not support -server to one that did, the -server flag should be automatically added. And thus, now, the -server flag is one of the flags that are automatically kept "up to date" based on the jre / jdk you are using. -- 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

[ 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. -- 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

[ https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi... ] Csaba Toth commented on JBIDE-12403: ------------------------------------ It's working here too! Thanks! -- 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