[JBoss JIRA] (WFCORE-4147) (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4147?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4147:
---------------------------------------
[~mkopecky] Correct. I would go with option 1. GC logging was unified in Java 9 so it should work on all compliant JVM's.
[~rstancel] Right, it does invoke the {{java -version}} to determine if the {{--add-modules}} argument is valid. It doesn't invoke it with the GC logging options though which is why it doesn't create a {{gc.log}} and {{gc.log.0}}.
> (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
> ---------------------------------------------------------------
>
> Key: WFCORE-4147
> URL: https://issues.jboss.org/browse/WFCORE-4147
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Marek Kopecký
> Assignee: Radovan Stancel
> Priority: Blocker
> Labels: Java11
>
> Wrong JAVA_OPTS propagation, wrong PowerShell GC logging
> Merging of [PR3496|https://github.com/wildfly/wildfly-core/pull/3496] introduces:
> * new blocker regression
> ** Wrong JAVA_OPTS propagation on JDK8
> *** Default JAVA_OPTS, like max heap size (xmx), xms, etc. are not propagated to JVM on bat scripts
> *** set "GC_LOG=true"
> *** standalone.bat
> *** ->
> *** {noformat}===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: "C:\Users\Administrator\playground\wfly.30.gc\wildfly"
> JAVA: "C:\Program Files\Java\jdk1.8.0_121\bin\java"
> JAVA_OPTS: ""-Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman" -Xloggc:"C:\Users\Administrator\playground\wfly.30.gc\wildfly\standalone\log\gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading "
> ==============================================================================={noformat}
> *** it looks like some quotation bug
> *** according to the jconsole - max heap size (Xmx) is not set correctly (~1.8GB), according to the cli - program.name is not set correctly (program.name = "standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman")
> * new blocker bug
> ** wrong PowerShell GC logging
> *** "standalone.bat + jdk11 + gc enabled" creates:
> **** standalone\log\gc.log
> **** standalone\log\gc.log.0
> *** "standalone.ps1 + jdk11 + gc enabled" creates:
> **** * standalone\log\gc.log
> Target release of this jira should be WF15
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (ELY-1697) IBM failing test CompatibilityClientTest
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELY-1697?page=com.atlassian.jira.plugin.s... ]
Farah Juma reassigned ELY-1697:
-------------------------------
Assignee: Farah Juma
> IBM failing test CompatibilityClientTest
> ----------------------------------------
>
> Key: ELY-1697
> URL: https://issues.jboss.org/browse/ELY-1697
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Testsuite
> Affects Versions: 1.7.0.CR2
> Reporter: Martin Choma
> Assignee: Farah Juma
> Priority: Major
>
> On ibm java
> {noformat}
> 08:56:01 + java -version
> 08:56:02 java version "1.8.0_181"
> 08:56:02 Java(TM) SE Runtime Environment (build 8.0.5.22 - pxa6480sr5fp22-20180919_01(SR5 FP22))
> 08:56:02 IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180915_397057 (JIT enabled, AOT enabled)
> 08:56:02 OpenJ9 - 6c152c2
> 08:56:02 OMR - 15647c3
> 08:56:02 IBM - d734883)
> 08:56:02 JCL - 20180821_01 based on Oracle jdk8u181-b12
> {noformat}
> I see error
> {noformat}
> 09:12:38 org.wildfly.security.sasl.digest.CompatibilityClientTest Time elapsed: 1.31 sec <<< ERROR!
> 09:12:38 org.wildfly.security.credential.store.CredentialStoreException: ELY09514: Unable to initialize credential store
> 09:12:38 at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.load(KeyStoreCredentialStore.java:871)
> 09:12:38 at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.initialize(KeyStoreCredentialStore.java:213)
> 09:12:38 at org.wildfly.security.credential.store.CredentialStoreBuilder.build(CredentialStoreBuilder.java:124)
> 09:12:38 at org.wildfly.security.sasl.digest.CompatibilityClientTest.setupCredentialStore(CompatibilityClientTest.java:98)
> 09:12:38 Caused by: java.io.IOException: com.sun.crypto.provider.SealedObjectForKeyProtector
> 09:12:38 at java.security.KeyStore.load(KeyStore.java:1456)
> 09:12:38 at org.wildfly.security.credential.store.impl.KeyStoreCredentialStore.load(KeyStoreCredentialStore.java:859)
> 09:12:38 ... 3 more
> {noformat}
> SealedObjectForKeyProtector exception is seen on IBM when keystore is created with nonIBM java. Which makes me think problem can be testsuite is run twice with -Djava8.home. Which is way we use to test with ibm 8 jdk. So probably credential store from previous run is used in run with ibm java.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3124) Nested GridCell/GridCellValue
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3124?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3124:
-------------------------------------
Sprint: 2018 Week 39-41 (was: 2018 Week 42-44)
> Nested GridCell/GridCellValue
> -----------------------------
>
> Key: DROOLS-3124
> URL: https://issues.jboss.org/browse/DROOLS-3124
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: Screenshot from 2018-10-12 10-10-01.png
>
>
> For some click/double click combination (not easy to reproduce) inside a gridcell, it seems that a nested GridCell or gridcellvallue will be created:
> in the screenshot it is shown by the empty box inside the cell below do2.mydo1.myint1
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (ELY-1698) Add profile for skipping default-tests
by Justin Cook (Jira)
[ https://issues.jboss.org/browse/ELY-1698?page=com.atlassian.jira.plugin.s... ]
Justin Cook commented on ELY-1698:
----------------------------------
To use the profile, specify with mvn clean install -P skip-default-tests. For example, to run only Java8 tests use: mvn clean install -P skip-default-tests -Djava8.home=/path/to/JDK8.
> Add profile for skipping default-tests
> --------------------------------------
>
> Key: ELY-1698
> URL: https://issues.jboss.org/browse/ELY-1698
> Project: WildFly Elytron
> Issue Type: Task
> Components: Build
> Reporter: Justin Cook
> Assignee: Justin Cook
> Priority: Major
>
> Currently, Elytron always run default-tests even when java8.home and/or java9.home are specified. This task is to add a profile to Elytron's build that allows skipping default-tests, for only Java8 and/or Java9 tests can be run if needed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (ELY-1698) Add profile for skipping default-tests
by Justin Cook (Jira)
Justin Cook created ELY-1698:
--------------------------------
Summary: Add profile for skipping default-tests
Key: ELY-1698
URL: https://issues.jboss.org/browse/ELY-1698
Project: WildFly Elytron
Issue Type: Task
Components: Build
Reporter: Justin Cook
Assignee: Justin Cook
Currently, Elytron always run default-tests even when java8.home and/or java9.home are specified. This task is to add a profile to Elytron's build that allows skipping default-tests, for only Java8 and/or Java9 tests can be run if needed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months