[JBoss JIRA] (WFLY-10427) override the Hibernate ORM 5.3 JtaPlatform on WildFly for all deployments
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-10427?page=com.atlassian.jira.plugin... ]
Scott Marlow closed WFLY-10427.
-------------------------------
> override the Hibernate ORM 5.3 JtaPlatform on WildFly for all deployments
> -------------------------------------------------------------------------
>
> Key: WFLY-10427
> URL: https://issues.jboss.org/browse/WFLY-10427
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 13.0.0.CR1
>
>
> When applications call javax.persistence.Persistence.generateSchema() from active JTA transactions, Hibernate defaults to using org.hibernate.engine.transaction.jta.platform.internal.JBossStandAloneJtaPlatform, which uses com.arjuna.ats.jta.TransactionManager. We cannot use com.arjuna.ats.jta.TransactionManager directly anymore, instead we need to use the WildFly transaction client layer which wraps Arjuna TM.
> [https://paste.fedoraproject.org/paste/9y4vn4E0yT77u471LNL-Xw] shows the call stack of where error is thrown by LocalTransaction.verifyAssociation:
> {quote}
> Caused by: java.lang.IllegalStateException: WFTXN0073: Unexpected provider transaction mismatch; expected TransactionImple < ac, BasicAction: 0:ffff0a0000b0:3831261e:5b045a43:11 status: ActionStatus.RUNNING >, got null[javatest.batch] 13:59:36,576 INFO [stdout] (Thread-130)
> at org.wildfly.transaction.client.LocalTransaction.verifyAssociation(LocalTransaction.java:245)
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10448) Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-10448?page=com.atlassian.jira.plugin... ]
R Searls commented on WFLY-10448:
---------------------------------
There is no crashing out of the script, but
the scripts may not set '-server' in JAVA_OPTS as is done in earlier JDK versions.
I'm trying to determine if this is an issue or not when using JDK-10. The options '-server'
and '-client' are HotSpot options. I don't find in the JDK-10 documentation if these are needed or supported any longer.
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10448
> URL: https://issues.jboss.org/browse/WFLY-10448
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 13.0.0.CR1
> Reporter: R Searls
> Assignee: R Searls
>
> bin\scripts domain.sh, standalone.sh and appclient.sh have a section of code that uses java option -d32 and -d64 when calling java to check the HotSpot type. These 2 options have been removed from JDK-10. They are marked as deprecated in JDK-9 but still function.
> These options are used in determining if '-server' is added to JAVA_OPTS. Enhancements need to be made to the scripts to check the JDK version and take appropriate action is assigning the value '-server'.
> The code affected
> {code:java}
> # Check for -d32/-d64 in JAVA_OPTS
> JVM_OPTVERSION="-version"
> JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
> JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
> test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
> test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
> # If -server not set in JAVA_OPTS, set it, if supported
> SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
> if [ "x$SERVER_SET" = "x" ]; then
> # Check for SUN(tm) JVM w/ HotSpot support
> if [ "x$HAS_HOTSPOT" = "x" ]; then
> HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
> fi
> # Check for OpenJDK JVM w/server support
> if [ "x$HAS_OPENJDK" = "x" ]; then
> HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
> fi
> # Check for IBM JVM w/server support
> if [ "x$HAS_IBM" = "x" ]; then
> HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"`
> fi
> # Enable -server if we have Hotspot or OpenJDK, unless we can't
> if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then
> # MacOS does not support -server flag
> if [ "$darwin" != "true" ]; then
> PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS"
> HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS"
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> fi
> else
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> {code}
> Here is the output of the currently supported java versions
> Doc for jdk-8 states
> > java -help
> where options include:
> -d32 use a 32-bit data model if available
> -d64 use a 64-bit data model if available
> Using these options tell if the version supports 32-bit or 64-bit
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> java version "1.8.0_72"
> Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
> Doc for jdk-9 states
> > java -help
> where options include:
> -d32 Deprecated, will be removed in a future release
> -d64 Deprecated, will be removed in a future release
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> openjdk version "9.0.4"
> OpenJDK Runtime Environment (build 9.0.4+11)
> OpenJDK 64-Bit Server VM (build 9.0.4+11, mixed mode)
> Doc for jdk-10
> > java -help
> No documentation for these options listed
> > java -d32 -version
> Unrecognized option: -d32
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> > java -d64 -version
> Unrecognized option: -d64
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10448) Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-10448?page=com.atlassian.jira.plugin... ]
R Searls commented on WFLY-10448:
---------------------------------
related documentation
https://stackoverflow.com/questions/198577/real-differences-between-java-...
-server option is linked to HotSpot
https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html
In JDK-8
-server
Selects the Java HotSpot Server VM. The 64-bit version of the JDK
supports only the Server VM, so in that case the option is implicit.
The -server option is used in "Performance Tuning" of HotSpot
(e.g. java -d64 -XX:+UseG1GC -Xms26g Xmx26g -XX:MaxGCPauseMillis=500 -XX:+PrintGCTimeStamp)
https://docs.oracle.com/javase/10/jrockit-hotspot/command-line-options.ht...
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10448
> URL: https://issues.jboss.org/browse/WFLY-10448
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 13.0.0.CR1
> Reporter: R Searls
> Assignee: R Searls
>
> bin\scripts domain.sh, standalone.sh and appclient.sh have a section of code that uses java option -d32 and -d64 when calling java to check the HotSpot type. These 2 options have been removed from JDK-10. They are marked as deprecated in JDK-9 but still function.
> These options are used in determining if '-server' is added to JAVA_OPTS. Enhancements need to be made to the scripts to check the JDK version and take appropriate action is assigning the value '-server'.
> The code affected
> {code:java}
> # Check for -d32/-d64 in JAVA_OPTS
> JVM_OPTVERSION="-version"
> JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
> JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
> test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
> test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
> # If -server not set in JAVA_OPTS, set it, if supported
> SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
> if [ "x$SERVER_SET" = "x" ]; then
> # Check for SUN(tm) JVM w/ HotSpot support
> if [ "x$HAS_HOTSPOT" = "x" ]; then
> HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
> fi
> # Check for OpenJDK JVM w/server support
> if [ "x$HAS_OPENJDK" = "x" ]; then
> HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
> fi
> # Check for IBM JVM w/server support
> if [ "x$HAS_IBM" = "x" ]; then
> HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"`
> fi
> # Enable -server if we have Hotspot or OpenJDK, unless we can't
> if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then
> # MacOS does not support -server flag
> if [ "$darwin" != "true" ]; then
> PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS"
> HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS"
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> fi
> else
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> {code}
> Here is the output of the currently supported java versions
> Doc for jdk-8 states
> > java -help
> where options include:
> -d32 use a 32-bit data model if available
> -d64 use a 64-bit data model if available
> Using these options tell if the version supports 32-bit or 64-bit
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> java version "1.8.0_72"
> Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
> Doc for jdk-9 states
> > java -help
> where options include:
> -d32 Deprecated, will be removed in a future release
> -d64 Deprecated, will be removed in a future release
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> openjdk version "9.0.4"
> OpenJDK Runtime Environment (build 9.0.4+11)
> OpenJDK 64-Bit Server VM (build 9.0.4+11, mixed mode)
> Doc for jdk-10
> > java -help
> No documentation for these options listed
> > java -d32 -version
> Unrecognized option: -d32
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> > java -d64 -version
> Unrecognized option: -d64
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10448) Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-10448?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-10448:
------------------------------------
But what is the bug (i.e. how does it manifest)? Are the scripts failing to run?
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10448
> URL: https://issues.jboss.org/browse/WFLY-10448
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 13.0.0.CR1
> Reporter: R Searls
> Assignee: R Searls
>
> bin\scripts domain.sh, standalone.sh and appclient.sh have a section of code that uses java option -d32 and -d64 when calling java to check the HotSpot type. These 2 options have been removed from JDK-10. They are marked as deprecated in JDK-9 but still function.
> These options are used in determining if '-server' is added to JAVA_OPTS. Enhancements need to be made to the scripts to check the JDK version and take appropriate action is assigning the value '-server'.
> The code affected
> {code:java}
> # Check for -d32/-d64 in JAVA_OPTS
> JVM_OPTVERSION="-version"
> JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
> JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
> test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
> test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
> # If -server not set in JAVA_OPTS, set it, if supported
> SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
> if [ "x$SERVER_SET" = "x" ]; then
> # Check for SUN(tm) JVM w/ HotSpot support
> if [ "x$HAS_HOTSPOT" = "x" ]; then
> HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
> fi
> # Check for OpenJDK JVM w/server support
> if [ "x$HAS_OPENJDK" = "x" ]; then
> HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
> fi
> # Check for IBM JVM w/server support
> if [ "x$HAS_IBM" = "x" ]; then
> HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"`
> fi
> # Enable -server if we have Hotspot or OpenJDK, unless we can't
> if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then
> # MacOS does not support -server flag
> if [ "$darwin" != "true" ]; then
> PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS"
> HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS"
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> fi
> else
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> {code}
> Here is the output of the currently supported java versions
> Doc for jdk-8 states
> > java -help
> where options include:
> -d32 use a 32-bit data model if available
> -d64 use a 64-bit data model if available
> Using these options tell if the version supports 32-bit or 64-bit
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> java version "1.8.0_72"
> Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
> Doc for jdk-9 states
> > java -help
> where options include:
> -d32 Deprecated, will be removed in a future release
> -d64 Deprecated, will be removed in a future release
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> openjdk version "9.0.4"
> OpenJDK Runtime Environment (build 9.0.4+11)
> OpenJDK 64-Bit Server VM (build 9.0.4+11, mixed mode)
> Doc for jdk-10
> > java -help
> No documentation for these options listed
> > java -d32 -version
> Unrecognized option: -d32
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> > java -d64 -version
> Unrecognized option: -d64
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10448) Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-10448?page=com.atlassian.jira.plugin... ]
R Searls commented on WFLY-10448:
---------------------------------
In an email discussion Kabin states ....
{code:java}
.... we should not remove them. The reason is that we still support JDK 8, and OpenShift which the CD releases target uses JDK8. However, if JDK10 breaks with them in we need to think what to do.
{code}
To maintain backward compatibility the bug fix should involve checking the jdk version.
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10448
> URL: https://issues.jboss.org/browse/WFLY-10448
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 13.0.0.CR1
> Reporter: R Searls
> Assignee: R Searls
>
> bin\scripts domain.sh, standalone.sh and appclient.sh have a section of code that uses java option -d32 and -d64 when calling java to check the HotSpot type. These 2 options have been removed from JDK-10. They are marked as deprecated in JDK-9 but still function.
> These options are used in determining if '-server' is added to JAVA_OPTS. Enhancements need to be made to the scripts to check the JDK version and take appropriate action is assigning the value '-server'.
> The code affected
> {code:java}
> # Check for -d32/-d64 in JAVA_OPTS
> JVM_OPTVERSION="-version"
> JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
> JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
> test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
> test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
> # If -server not set in JAVA_OPTS, set it, if supported
> SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
> if [ "x$SERVER_SET" = "x" ]; then
> # Check for SUN(tm) JVM w/ HotSpot support
> if [ "x$HAS_HOTSPOT" = "x" ]; then
> HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
> fi
> # Check for OpenJDK JVM w/server support
> if [ "x$HAS_OPENJDK" = "x" ]; then
> HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
> fi
> # Check for IBM JVM w/server support
> if [ "x$HAS_IBM" = "x" ]; then
> HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"`
> fi
> # Enable -server if we have Hotspot or OpenJDK, unless we can't
> if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then
> # MacOS does not support -server flag
> if [ "$darwin" != "true" ]; then
> PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS"
> HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS"
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> fi
> else
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> {code}
> Here is the output of the currently supported java versions
> Doc for jdk-8 states
> > java -help
> where options include:
> -d32 use a 32-bit data model if available
> -d64 use a 64-bit data model if available
> Using these options tell if the version supports 32-bit or 64-bit
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> java version "1.8.0_72"
> Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
> Doc for jdk-9 states
> > java -help
> where options include:
> -d32 Deprecated, will be removed in a future release
> -d64 Deprecated, will be removed in a future release
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> openjdk version "9.0.4"
> OpenJDK Runtime Environment (build 9.0.4+11)
> OpenJDK 64-Bit Server VM (build 9.0.4+11, mixed mode)
> Doc for jdk-10
> > java -help
> No documentation for these options listed
> > java -d32 -version
> Unrecognized option: -d32
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> > java -d64 -version
> Unrecognized option: -d64
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10448) Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-10448?page=com.atlassian.jira.plugin... ]
R Searls updated WFLY-10448:
----------------------------
Summary: Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh (was: Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh)
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh, appclient.sh
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-10448
> URL: https://issues.jboss.org/browse/WFLY-10448
> Project: WildFly
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 13.0.0.CR1
> Reporter: R Searls
> Assignee: R Searls
>
> bin\scripts domain.sh, standalone.sh and appclient.sh have a section of code that uses java option -d32 and -d64 when calling java to check the HotSpot type. These 2 options have been removed from JDK-10. They are marked as deprecated in JDK-9 but still function.
> These options are used in determining if '-server' is added to JAVA_OPTS. Enhancements need to be made to the scripts to check the JDK version and take appropriate action is assigning the value '-server'.
> The code affected
> {code:java}
> # Check for -d32/-d64 in JAVA_OPTS
> JVM_OPTVERSION="-version"
> JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
> JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
> test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
> test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
> # If -server not set in JAVA_OPTS, set it, if supported
> SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
> if [ "x$SERVER_SET" = "x" ]; then
> # Check for SUN(tm) JVM w/ HotSpot support
> if [ "x$HAS_HOTSPOT" = "x" ]; then
> HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
> fi
> # Check for OpenJDK JVM w/server support
> if [ "x$HAS_OPENJDK" = "x" ]; then
> HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
> fi
> # Check for IBM JVM w/server support
> if [ "x$HAS_IBM" = "x" ]; then
> HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"`
> fi
> # Enable -server if we have Hotspot or OpenJDK, unless we can't
> if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then
> # MacOS does not support -server flag
> if [ "$darwin" != "true" ]; then
> PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS"
> HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS"
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> fi
> else
> JVM_OPTVERSION="-server $JVM_OPTVERSION"
> fi
> {code}
> Here is the output of the currently supported java versions
> Doc for jdk-8 states
> > java -help
> where options include:
> -d32 use a 32-bit data model if available
> -d64 use a 64-bit data model if available
> Using these options tell if the version supports 32-bit or 64-bit
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> java version "1.8.0_72"
> Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
> Doc for jdk-9 states
> > java -help
> where options include:
> -d32 Deprecated, will be removed in a future release
> -d64 Deprecated, will be removed in a future release
> > java -d32 -version
> Error: This Java instance does not support a 32-bit JVM.
> Please install the desired version.
> > java -d64 -version
> openjdk version "9.0.4"
> OpenJDK Runtime Environment (build 9.0.4+11)
> OpenJDK 64-Bit Server VM (build 9.0.4+11, mixed mode)
> Doc for jdk-10
> > java -help
> No documentation for these options listed
> > java -d32 -version
> Unrecognized option: -d32
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> > java -d64 -version
> Unrecognized option: -d64
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10448) Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
by R Searls (JIRA)
R Searls created WFLY-10448:
-------------------------------
Summary: Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
Key: WFLY-10448
URL: https://issues.jboss.org/browse/WFLY-10448
Project: WildFly
Issue Type: Bug
Components: Scripts
Affects Versions: 13.0.0.CR1
Reporter: R Searls
Assignee: R Searls
bin\scripts domain.sh, standalone.sh and appclient.sh have a section of code that uses java option -d32 and -d64 when calling java to check the HotSpot type. These 2 options have been removed from JDK-10. They are marked as deprecated in JDK-9 but still function.
These options are used in determining if '-server' is added to JAVA_OPTS. Enhancements need to be made to the scripts to check the JDK version and take appropriate action is assigning the value '-server'.
The code affected
{code:java}
# Check for -d32/-d64 in JAVA_OPTS
JVM_OPTVERSION="-version"
JVM_D64_OPTION=`echo $JAVA_OPTS | $GREP "\-d64"`
JVM_D32_OPTION=`echo $JAVA_OPTS | $GREP "\-d32"`
test "x$JVM_D64_OPTION" != "x" && JVM_OPTVERSION="-d64 $JVM_OPTVERSION"
test "x$JVM_D32_OPTION" != "x" && JVM_OPTVERSION="-d32 $JVM_OPTVERSION"
# If -server not set in JAVA_OPTS, set it, if supported
SERVER_SET=`echo $JAVA_OPTS | $GREP "\-server"`
if [ "x$SERVER_SET" = "x" ]; then
# Check for SUN(tm) JVM w/ HotSpot support
if [ "x$HAS_HOTSPOT" = "x" ]; then
HAS_HOTSPOT=`"$JAVA" $JVM_OPTVERSION -version 2>&1 | $GREP -i HotSpot`
fi
# Check for OpenJDK JVM w/server support
if [ "x$HAS_OPENJDK" = "x" ]; then
HAS_OPENJDK=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i OpenJDK`
fi
# Check for IBM JVM w/server support
if [ "x$HAS_IBM" = "x" ]; then
HAS_IBM=`"$JAVA" $JVM_OPTVERSION 2>&1 | $GREP -i "IBM J9"`
fi
# Enable -server if we have Hotspot or OpenJDK, unless we can't
if [ "x$HAS_HOTSPOT" != "x" -o "x$HAS_OPENJDK" != "x" -o "x$HAS_IBM" != "x" ]; then
# MacOS does not support -server flag
if [ "$darwin" != "true" ]; then
PROCESS_CONTROLLER_JAVA_OPTS="-server $PROCESS_CONTROLLER_JAVA_OPTS"
HOST_CONTROLLER_JAVA_OPTS="-server $HOST_CONTROLLER_JAVA_OPTS"
JVM_OPTVERSION="-server $JVM_OPTVERSION"
fi
fi
else
JVM_OPTVERSION="-server $JVM_OPTVERSION"
fi
{code}
Here is the output of the currently supported java versions
Doc for jdk-8 states
> java -help
where options include:
-d32 use a 32-bit data model if available
-d64 use a 64-bit data model if available
Using these options tell if the version supports 32-bit or 64-bit
> java -d32 -version
Error: This Java instance does not support a 32-bit JVM.
Please install the desired version.
> java -d64 -version
java version "1.8.0_72"
Java(TM) SE Runtime Environment (build 1.8.0_72-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode)
Doc for jdk-9 states
> java -help
where options include:
-d32 Deprecated, will be removed in a future release
-d64 Deprecated, will be removed in a future release
> java -d32 -version
Error: This Java instance does not support a 32-bit JVM.
Please install the desired version.
> java -d64 -version
openjdk version "9.0.4"
OpenJDK Runtime Environment (build 9.0.4+11)
OpenJDK 64-Bit Server VM (build 9.0.4+11, mixed mode)
Doc for jdk-10
> java -help
No documentation for these options listed
> java -d32 -version
Unrecognized option: -d32
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
> java -d64 -version
Unrecognized option: -d64
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Obsolete java options -d32, -d64 in jdk-10 affect scripts domain.sh, standalone.sh
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-9939) Eliminate the need to override the org.jboss.as.clustering.jgroups module in our openshift images
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9939?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-9939:
----------------------------------------
There are separate CLOUD JIRA for option #2 above.
> Eliminate the need to override the org.jboss.as.clustering.jgroups module in our openshift images
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-9939
> URL: https://issues.jboss.org/browse/WFLY-9939
> Project: WildFly
> Issue Type: Enhancement
> Components: Clustering
> Reporter: Brian Stansberry
> Assignee: Paul Ferraro
>
> Our openshift images are overriding the org.jboss.as.clustering.jgroups module.xml in order to include a dependency on the org.openshift.ping module. This is fragile because any update to the overridden module.xml needs to be applied to the override file as well, and that can easily break.
> Let's make the need for this go away. Possibilities:
> 1) Add an optional dependency on module "org.openshift.ping" to the org.jboss.as.clustering.jgroups module. The openshift images then just add that module. In bare metal installations the module is not present.
> 2) Change the standalone-openshift.xml configs such that whatever is using this module declares a "module" attribute, removing the need for the module.xml dependency. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track making the config change and removing the override.)
> 3) Ship whatever's needed from org.openshift.ping in WF itself, eliminating the need for that module. This may already be in progress as I've seen some relevant JIRAs. (If this is the correct solution, please move this issue to the CLOUD JIRA project where we can use it to track removing the override and the installation of the org.openshift.ping module.)
> [~luck3y] FYI.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months