October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11093) WildFly can't be build on Java 11

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created WFLY-11093: ---------------------------------------- Summary: WildFly can't be build on Java 11 Key: WFLY-11093 URL: https://issues.jboss.org/browse/WFLY-11093 Project: WildFly Issue Type: Bug Components: Server, XTS Reporter: Rostislav Svoboda Assignee: Ondra Chaloupka Priority: Blocker WildFly can't be build on Java 11. {code} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project wildfly-xts: Compilation failure [ERROR] /Users/rsvoboda/git/wildfly/xts/target/generated-sources/annotations/org/jboss/as/xts/logging/XtsAsLogger_$logger.java:[11,22] '.' expected [ERROR] {code} After reverting fix for https://issues.jboss.org/browse/WFLY-9455 I can build the server using Java 11. https://github.com/wildfly/wildfly/commit/b2674da738af714a05f30464e849544... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1653) JDK 11 Support

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/ELY-1653?page=com.atlassian.jira.plugin.s... ] Ondrej Kotek updated ELY-1653: ------------------------------ Labels: Java11 (was: ) > JDK 11 Support > -------------- > > Key: ELY-1653 > URL: https://issues.jboss.org/browse/ELY-1653 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Justin Cook > Labels: Java11 > Fix For: 1.7.0.CR3 > > > I suspect this will likely take three / four steps: - > # Convert he project to a multi-release built using Java 9 > # Eliminate the use of APIs in sun.misc and sun.reflect in the Java 9 variant > # Ensure the project can be build on JDK 11 > This final step may not be achievable in the short term until we can drop support for JDK 8 but by moving to the Java 9 MR jar our jar should be compatible on Java 10 and 11 as well. We may want to define a PR run that builds on Java 9 but tests in Java 11, this would mean the testsuite at least needs to be buildable on Java 11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1642) Compilation error on JDK 11: cannot find class sun.reflect.Reflection

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/ELY-1642?page=com.atlassian.jira.plugin.s... ] Ondrej Kotek updated ELY-1642: ------------------------------ Labels: Java11 (was: ) > Compilation error on JDK 11: cannot find class sun.reflect.Reflection > --------------------------------------------------------------------- > > Key: ELY-1642 > URL: https://issues.jboss.org/browse/ELY-1642 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Affects Versions: 1.5.1.Final > Environment: openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+25) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+25, mixed mode) > Reporter: Ondrej Kotek > Assignee: Justin Cook > Priority: Critical > Labels: Java11 > Fix For: 1.7.0.CR1 > > > {{mvn test}} results in compilation error: > {noformat} > [ERROR] /home/okotek/git/wildfly-elytron/src/main/java/org/wildfly/security/manager/WildFlySecurityManager.java:[58,19] cannot find symbol > symbol: class Reflection > location: package sun.reflect > {noformat} > Blocks testing on JDK 11, setting to Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3054) Highlight in expression builder previous selection in Scenario right panel

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3054?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3054: --------------------------------- Tester: Klara Kufova > Highlight in expression builder previous selection in Scenario right panel > -------------------------------------------------------------------------- > > Key: DROOLS-3054 > URL: https://issues.jboss.org/browse/DROOLS-3054 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Labels: UX, UXTeam > Attachments: Screen Shot 2018-09-28 at 3.45.25 PM.png > > > When the user edits the type of a column, the expression builder into the right panel should highlight the existing mapped type. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid

by Klara Kufova (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3053: --------------------------------- Tester: Klara Kufova > Warning popup of column type change in Scenario grid > ---------------------------------------------------- > > Key: DROOLS-3053 > URL: https://issues.jboss.org/browse/DROOLS-3053 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Minor > Labels: UX, UXTeam > > Implement a warning popup when the user changes the type of a column that has been already populated. > *Acceptance criteria* > - If the column contains no value, no confirmation is needed > - If old and new types are the same the user has to decide if the values should be removed or not > - If old and new types are not the same the user has to accept that old values will be removed > - All warning popups should contains also a "Cancel" command to abort the edit -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3041) [DMN Designer] Can not edit node after diagram cleared

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3041?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3041: -------------------------------- Description: If user clears the diagram and then add new node, he is unable to edit this node. h2. Acceptance test h3. New diagram (/) - Add nodes - Clear - Add new decision node - Put some expression inside h3. Non empty existing diagram (/) - Clear - Add new decision node - Put some expression inside - Save reopen was: If user clears the diagram and then add new node, he is unable to edit this node. h2. Acceptance test h3. New diagram (/) - Add nodes - Clear - Add new decision node - Put some expression inside h3. Non empty existing diagram - Clear - Add new decision node - Put some expression inside - Save reopen > [DMN Designer] Can not edit node after diagram cleared > ------------------------------------------------------ > > Key: DROOLS-3041 > URL: https://issues.jboss.org/browse/DROOLS-3041 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-09-26 13-18-33.png > > > If user clears the diagram and then add new node, he is unable to edit this node. > h2. Acceptance test > h3. New diagram (/) > - Add nodes > - Clear > - Add new decision node > - Put some expression inside > h3. Non empty existing diagram (/) > - Clear > - Add new decision node > - Put some expression inside > - Save reopen -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3041) [DMN Designer] Can not edit node after diagram cleared

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-3041?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3041: -------------------------------- Description: If user clears the diagram and then add new node, he is unable to edit this node. h2. Acceptance test h3. New diagram (/) - Add nodes - Clear - Add new decision node - Put some expression inside h3. Non empty existing diagram - Clear - Add new decision node - Put some expression inside - Save reopen was: If user clears the diagram and then add new node, he is unable to edit this node. h2. Acceptance test h3. New diagram - Add nodes - Clear - Add new decision node - Put some expression inside h3. Non empty existing diagram - Clear - Add new decision node - Put some expression inside - Save reopen > [DMN Designer] Can not edit node after diagram cleared > ------------------------------------------------------ > > Key: DROOLS-3041 > URL: https://issues.jboss.org/browse/DROOLS-3041 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.12.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: DMCommunity Challenge - March 2017.dmn, Screenshot from 2018-09-26 13-18-33.png > > > If user clears the diagram and then add new node, he is unable to edit this node. > h2. Acceptance test > h3. New diagram (/) > - Add nodes > - Clear > - Add new decision node > - Put some expression inside > h3. Non empty existing diagram > - Clear > - Add new decision node > - Put some expression inside > - Save reopen -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4143) Embed CLI failures on IBM jdk - checkLogging

by Petr Kremensky (JIRA)

Petr Kremensky created WFCORE-4143: -------------------------------------- Summary: Embed CLI failures on IBM jdk - checkLogging Key: WFCORE-4143 URL: https://issues.jboss.org/browse/WFCORE-4143 Project: WildFly Core Issue Type: Bug Components: Test Suite Environment: IBM JDK {noformat} java version "1.8.0_181" Java(TM) SE Runtime Environment (build 8.0.5.20 - pxa6480sr5fp20-20180802_01(SR5 FP20)) IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180731_393394 (JIT enabled, AOT enabled) OpenJ9 - bd23af8 OMR - ca1411c IBM - 98805ca) JCL - 20180719_01 based on Oracle jdk8u181-b12 {noformat} Reporter: Petr Kremensky {{testLogging}} for Cli tests in Wildfly-core testsuite fails on IBM JDK. *reproduce* cd wildfly-core/testsuite mvn clean test -fae -Dts.manualmode -pl manualmode,standalone -Dtest=CLIEmbedHostControllerTestCase,CLIEmbedServerTestCase,SilentModeTestCase ... [ERROR] Failures: [ERROR] SilentModeTestCase.testLogging:99->checkIfEmpty:152 [INFO] [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0 ... [ERROR] Failures: [ERROR] CLIEmbedHostControllerTestCase.testHelp:321->checkLogging:744 [ERROR] CLIEmbedHostControllerTestCase.testStdOutDefault:160->stdoutTest:188->checkClientSideLogging:231->checkLogging:744 [ERROR] CLIEmbedHostControllerTestCase.testStdOutDiscard:166->stdoutTest:188->checkClientSideLogging:231->checkLogging:744 [ERROR] CLIEmbedHostControllerTestCase.testStdOutEcho:172->stdoutTest:188->checkClientSideLogging:231->checkLogging:744 [ERROR] CLIEmbedServerTestCase.testHelp:543->checkLogging:764 [ERROR] CLIEmbedServerTestCase.testStdOutDefault:196->stdoutTest:224->checkClientSideLogging:267->checkLogging:764 [ERROR] CLIEmbedServerTestCase.testStdOutDiscard:202->stdoutTest:224->checkClientSideLogging:267->checkLogging:764 [ERROR] CLIEmbedServerTestCase.testStdOutEcho:208->stdoutTest:224->checkClientSideLogging:267->checkLogging:764 [INFO] [ERROR] Tests run: 51, Failures: 8, Errors: 0, Skipped: 0 {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11092) XtsAsLogger doesn't compile on JDK11

by Petr Kremensky (JIRA)

Petr Kremensky created WFLY-11092: ------------------------------------- Summary: XtsAsLogger doesn't compile on JDK11 Key: WFLY-11092 URL: https://issues.jboss.org/browse/WFLY-11092 Project: WildFly Issue Type: Bug Components: XTS Environment: {noformat} java version "11" 2018-09-25 Java(TM) SE Runtime Environment 18.9 (build 11+28) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode) {noformat} Reporter: Petr Kremensky Assignee: Ondra Chaloupka Compilation failure on JDK 11 introduced by https://github.com/wildfly/wildfly/pull/11702 {noformat} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project wildfly-xts: Compilation failure [ERROR] /home/pkremens/devel/wildfly/xts/target/generated-sources/annotations/org/jboss/as/xts/logging/XtsAsLogger_$logger.java:[11,22] '.' expected {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9455) WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9455?page=com.atlassian.jira.plugin.... ] Petr Kremensky commented on WFLY-9455: -------------------------------------- [~ochaloup] Heads up, this one doesn't compile on JDK11 {noformat} $ java -version java version "11" 2018-09-25 Java(TM) SE Runtime Environment 18.9 (build 11+28) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode) [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /home/pkremens/devel/wildfly/xts/target/generated-sources/annotations/org/jboss/as/xts/logging/XtsAsLogger_$logger.java:[11,22] '.' expected [INFO] 1 error {noformat} I'll file a separate issue. > WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions > ------------------------------------------------------------------------------------- > > Key: WFLY-9455 > URL: https://issues.jboss.org/browse/WFLY-9455 > Project: WildFly > Issue Type: Bug > Components: XTS > Affects Versions: 11.0.0.CR1 > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 15.0.0.Alpha1 > > > It happens to get exception > {code} > ERROR [org.jboss.as.txn] (default task-12) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0 > ERROR [org.jboss.as.txn] (default task-12) WFLYTX0001: Unable to roll back active transaction: javax.transaction.SystemException: WFTXN0032: Rollback not allowed on imported transaction > at org.wildfly.transaction.client.LocalTransaction.rollbackAndDissociate(LocalTransaction.java:100) > at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:83) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137) > at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1510) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} > when using XTS transactions bridged to JTA for EJB handling. This happens on change of integration layer for WFTC in WFLY11. > The integration issues were already discussed as part of the JBTM-2853. > Here I hit a trouble of having log filled with the exception mentioned above. This does not cause a functionality trouble but the log is ugly filled with ERRORs. > The trouble seems to be caused by the fact that transaction is imported on ivocation of WS > https://github.com/wildfly/wildfly/blob/master/webservices/server-integra... > but as it was suspended in the integration code before > https://github.com/jbosstm/narayana/blob/master/txbridge/src/main/java/or... > now the WFTC holds the notion about the transaction even on call of > https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... > and such transaction is tried to be rollback which is forbidden on WFTC for imported ones and thus at least ERROR msg is written to the log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018