[jbosstools-issues] [JBoss JIRA] (JBIDE-19049) Enable JBoss servers to run with java 9
Martin Malina (JIRA)
issues at jboss.org
Tue Jan 20 08:16:49 EST 2015
Martin Malina created JBIDE-19049:
-------------------------------------
Summary: Enable JBoss servers to run with java 9
Key: JBIDE-19049
URL: https://issues.jboss.org/browse/JBIDE-19049
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.2.2.Final
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.0.Alpha1
I briefly tried to use java 9 for our tooling and to run servers.
I downloaded it from here:
https://jdk9.java.net/download/
{code}
nattura:8.0.2 rasp$ java -version
java version "1.9.0-ea"
Java(TM) SE Runtime Environment (build 1.9.0-ea-b45)
Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b45, mixed mode)
{code}
There are a couple of problems:
1. When I add a WildFly 8.2 server into JBDS 8.0.2, I cannot change the runtime to use java 9 - it seems we restrict that.
2. Even if I could, we need to make sure -XX:MaxPermSize is not used in the server launch command. When I tried to run WildFly 8.2 from the terminal, it wouldn't work unless I removed the max perm size argument. Apparently java 9 does not just ignore this parameter (as java 8 did), but it does not allow it at all.
{code}
nattura:bin rasp$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/rasp/jbossqa/runtimes/wildfly-8.2.0.Final
JAVA: /Library/Java/JavaVirtualMachines/jdk1.9.0.jdk/Contents/Home/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
Unrecognized VM option 'MaxPermSize=256m'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}
Of course it's questionable if we should allow java 9 for current servers at all as they don't support it officially. But I would say there is no need to restrict it if it works.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jbosstools-issues
mailing list