October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11123) Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFLY-11123?page=com.atlassian.jira.plugin... ] Martin Choma updated WFLY-11123: -------------------------------- Priority: Critical (was: Minor) > Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions > ------------------------------------------------------------------------- > > Key: WFLY-11123 > URL: https://issues.jboss.org/browse/WFLY-11123 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 14.0.1.Final > Environment: Windows 7 x64. Java 11: OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11+28-201810022317, mixed mode) > Reporter: Marco Del Percio > Assignee: Darran Lofthouse > Priority: Critical > Labels: Java11, access, elytron, illegal, reflective, wildfly > > After configuring HTTPS using the following guide: [Enable One-way SSL/TLS for Applications|http://docs.wildfly.org/14/WildFly_Elytron_Security.html#con...], configuration seems ok and server boots fine however an illegal reflective access warning comes up from jar within Elytron: > {color:red} > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.wildfly.extension.elytron.SSLDefinitions (jar:file:/D:/wildfly-14.0.1.Final_FleetManager/modules/system/layers/base/org/wildfly/extension/elytron/main/wildfly-elytron-integration-6.0.2.Final.jar!/) to method com.sun.net.ssl.internal.ssl.Provider.isFIPS() > WARNING: Please consider reporting this to the maintainers of org.wildfly.extension.elytron.SSLDefinitions > WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations > WARNING: All illegal access operations will be denied in a future release > {color} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11136) It is not possible to build Mojarra with JDK10+

by Jan Kašík (Jira)

Jan Kašík created WFLY-11136: -------------------------------- Summary: It is not possible to build Mojarra with JDK10+ Key: WFLY-11136 URL: https://issues.jboss.org/browse/WFLY-11136 Project: WildFly Issue Type: Bug Components: JSF Reporter: Jan Kašík Assignee: Farah Juma It is not possible to build Mojarra with JDK10+. See [issue on project page (upstream)|https://github.com/eclipse-ee4j/mojarra/issues/4461]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3088) FEEL Compiler: refactor to AST-based tree walk

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-3088: -------------------------------------- Summary: FEEL Compiler: refactor to AST-based tree walk Key: DROOLS-3088 URL: https://issues.jboss.org/browse/DROOLS-3088 Project: Drools Issue Type: Task Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi Current implementation of the compiler walks the parse tree generated by ANTLR, which is a bit cumbersome because of the way the grammar has to be written to deal with priorities/ambiguities. Luckily, many of such issues are solved by the interpreter implementation, which walks the parse tree and generates a neat, simpler Abstract Syntax Tree. This tasks is to refactor our current compiler to walk that AST, instead of the larger parse tree. Benefits: - less "visit" cases in the visitor - more opportunities to "optimize" the tree (e.g, tree rewrites, constant folding) - more opportunities to refactor tree walking phases (e.g. we could add a "type-evaluation" phase) - a chance to refactor code gen utilities to support classes, and simplify the code in general - cons: it takes a bit of time, but the AST nodes are really a handful, so it should not take that much -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-95) ResultSet.close() isn't called directly

by Jesper Pedersen (Jira)

Jesper Pedersen created AG-95: --------------------------------- Summary: ResultSet.close() isn't called directly Key: AG-95 URL: https://issues.jboss.org/browse/AG-95 Project: Agroal Issue Type: Bug Components: pool Affects Versions: 1.1 Reporter: Jesper Pedersen Assignee: Luis Barreiro When you call ResultSet.close() the underlying close() method isn't called until the statement tracker takes care of it -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3087) DMN Validation of DecisionService referencing a missing import

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3087: -------------------------------------- Summary: DMN Validation of DecisionService referencing a missing import Key: DROOLS-3087 URL: https://issues.jboss.org/browse/DROOLS-3087 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3073) Wrong full package if you use classes from another folder

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3073?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3073: -------------------------------------- [~jomarko], yes, correct, after importing the data object using the *Data Objects* tab, you need to save, close, and reopen the scenario. > Wrong full package if you use classes from another folder > ---------------------------------------------------------- > > Key: DROOLS-3073 > URL: https://issues.jboss.org/browse/DROOLS-3073 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Attachments: Screenshot from 2018-10-05 15-32-12.png, scesim.zip > > > Step to reproduce: > - Create a Data Object "Object1" in a specific package (i.e. com.myspace.myproject) > - Create a Test Scenario (Preview) "Test1" in a different package (i.e. com.myspace) > - Use Data Objects tab to import "Object1" to "Test1" > - Reload the asset and map a field of "Object1" to a column > - Fill "Test1" with valid values > - Run the scenario > Result: Impossible to load class com.myspace.Object1 > Minor bug: if "Test1" has been create in default package the error that you get is "Impossible to load class *.*Object1" so it should be impossible to create the asset into default package or it should consider it to avoid "." symbol at the beginning -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3073) Wrong full package if you use classes from another folder

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3073?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3073: --------------------------------- Tester: Klara Kufova > Wrong full package if you use classes from another folder > ---------------------------------------------------------- > > Key: DROOLS-3073 > URL: https://issues.jboss.org/browse/DROOLS-3073 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Attachments: Screenshot from 2018-10-05 15-32-12.png, scesim.zip > > > Step to reproduce: > - Create a Data Object "Object1" in a specific package (i.e. com.myspace.myproject) > - Create a Test Scenario (Preview) "Test1" in a different package (i.e. com.myspace) > - Use Data Objects tab to import "Object1" to "Test1" > - Reload the asset and map a field of "Object1" to a column > - Fill "Test1" with valid values > - Run the scenario > Result: Impossible to load class com.myspace.Object1 > Minor bug: if "Test1" has been create in default package the error that you get is "Impossible to load class *.*Object1" so it should be impossible to create the asset into default package or it should consider it to avoid "." symbol at the beginning -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2959) Create initial content for Scenario Simulation documentation.

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-2959?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-2959: -------------------------------------- [~danielezonca], is this already merged in {{master}}? Should I mark this issue as resolved? > Create initial content for Scenario Simulation documentation. > ------------------------------------------------------------- > > Key: DROOLS-2959 > URL: https://issues.jboss.org/browse/DROOLS-2959 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Klara Kufova > Priority: Major > > As a user I would like to know that this new tool exists and how to use it :-) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3085) Fix Scenario.getDescription() access

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3085?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3085: --------------------------------- Tester: Klara Kufova > Fix Scenario.getDescription() access > ------------------------------------ > > Key: DROOLS-3085 > URL: https://issues.jboss.org/browse/DROOLS-3085 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Daniele Zonca > Priority: Major > > accessing Scenario.getDescription() throws exception. Refactor to avoid that *or* catch all throwned exceptions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ] Kabir Khan commented on WFLY-11112: ----------------------------------- [~istraka] / [~msvehla] Is this a blocker for WF15, or for 7.2.0.GA? If it is for 7.2.0, we should clone a JBEAP. CC [~jmesnil] [~ehugonnet] > WildFly intermittently fails to add pooled-connection-factory but it still got registered after > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11112 > URL: https://issues.jboss.org/browse/WFLY-11112 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: server.log, standalone-full.xml > > > We see following error in log of WildFly (master): > {code} > 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("pooled-connection-factory" => "activemq-ra") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] > } > {code} > Factory is defined: > {code:java} > <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> > {code} > However factory is registered after and deployment is able to use it. Error is logged intermittently. > Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018