[jbossws-issues] [JBoss JIRA] (JBWS-3914) Arquillian is unable to start during testsuite when running with 32-bit JDK
Jan Blizňák created JBWS-3914:
---------------------------------
Summary: Arquillian is unable to start during testsuite when running with
32-bit JDK
Key: JBWS-3914
URL: https://issues.jboss.org/browse/JBWS-3914
Project: JBoss Web Services
Issue Type: Bug
Components: jbossws-cxf
Affects Versions: jbossws-cxf-5.0.0.Final
Reporter: Jan Blizňák
export JAVA_HOME=/path/to/32bit/jdk
export PATH=$JAVA_HOME/bin:$PATH
mvn -Pwildfly900 integration-test
will eventually fail on container startup by arquillian:
{code}
May 12, 2015 4:55:44 AM
org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
INFO: Starting container with: [/qa/tools/opt/jdk1.8.0.unlimited.BC/bin/java,
-D[Standalone], -Xms64m, -Xmx512m, -XX:MaxPermSize=256m, -Djava.net.preferIPv4Stack=true,
-server, -XX:+UseCompressedOops, -Djboss.socket.binding.port-offset=0, -ea,
....(trimmed)]
Java HotSpot(TM) Server VM warning: ignoring option MaxPermSize=256m; support was removed
in 8.0
Unrecognized VM option 'UseCompressedOops'
Did you mean '(+/-)CheckCompressedOops'?
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}
According to this http://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html the
default for UseCompressedOops is true for 64-bit JDK, so we should be safe to remove the
setting from arquillian.xml and pom.xml files in testsuite module
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)