March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9940) Reduce unnecessary lambda usage in clustering modules

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9940?page=com.atlassian.jira.plugin.... ] Paul Ferraro reopened WFLY-9940: -------------------------------- > Reduce unnecessary lambda usage in clustering modules > ----------------------------------------------------- > > Key: WFLY-9940 > URL: https://issues.jboss.org/browse/WFLY-9940 > Project: WildFly > Issue Type: Task > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 13.0.0.Beta1 > > > Lambdas chew up a lot of resources and we use a lot of them. Eliminate whenever possible. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2441) DMN runtime not using the kiecontainer root classloader to load classes

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2441?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2441: --------------------------------------- I attached an example to reproduce this problem. This one also requires a dependency to apache commons, that also needs to work after changing the classloader: <dependency> <groupId>org.apache.commons</groupId> <artifactId>commons-math3</artifactId> <version>3.6.1</version> </dependency> > DMN runtime not using the kiecontainer root classloader to load classes > ----------------------------------------------------------------------- > > Key: DROOLS-2441 > URL: https://issues.jboss.org/browse/DROOLS-2441 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.6.0.Final > Reporter: Edson Tirelli > Assignee: Matteo Mortari > Priority: Blocker > Fix For: 7.8.0.Final > > Attachments: Standard Deviation.dmn, StandardDeviation.java > > > The FunctionDefNode is not using the kie container root classloader to load classes. I even added a comment for that, just a shame comments are not executable: > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m... > {code:title=FunctionDefNode.java} > // might need to explicitly use a classloader here > Class<?> clazz = Class.forName( clazzName ); > {code} > To reproduce the problem, create a java class with a static method, add it to the kjar, create a DMN model that invokes that model, and try to execute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2441) DMN runtime not using the kiecontainer root classloader to load classes

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2441?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-2441: ---------------------------------- Attachment: StandardDeviation.java > DMN runtime not using the kiecontainer root classloader to load classes > ----------------------------------------------------------------------- > > Key: DROOLS-2441 > URL: https://issues.jboss.org/browse/DROOLS-2441 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.6.0.Final > Reporter: Edson Tirelli > Assignee: Matteo Mortari > Priority: Blocker > Fix For: 7.8.0.Final > > Attachments: Standard Deviation.dmn, StandardDeviation.java > > > The FunctionDefNode is not using the kie container root classloader to load classes. I even added a comment for that, just a shame comments are not executable: > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m... > {code:title=FunctionDefNode.java} > // might need to explicitly use a classloader here > Class<?> clazz = Class.forName( clazzName ); > {code} > To reproduce the problem, create a java class with a static method, add it to the kjar, create a DMN model that invokes that model, and try to execute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2441) DMN runtime not using the kiecontainer root classloader to load classes

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2441?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-2441: ---------------------------------- Attachment: Standard Deviation.dmn > DMN runtime not using the kiecontainer root classloader to load classes > ----------------------------------------------------------------------- > > Key: DROOLS-2441 > URL: https://issues.jboss.org/browse/DROOLS-2441 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.6.0.Final > Reporter: Edson Tirelli > Assignee: Matteo Mortari > Priority: Blocker > Fix For: 7.8.0.Final > > Attachments: Standard Deviation.dmn, StandardDeviation.java > > > The FunctionDefNode is not using the kie container root classloader to load classes. I even added a comment for that, just a shame comments are not executable: > https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m... > {code:title=FunctionDefNode.java} > // might need to explicitly use a classloader here > Class<?> clazz = Class.forName( clazzName ); > {code} > To reproduce the problem, create a java class with a static method, add it to the kjar, create a DMN model that invokes that model, and try to execute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2441) DMN runtime not using the kiecontainer root classloader to load classes

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-2441: ------------------------------------- Summary: DMN runtime not using the kiecontainer root classloader to load classes Key: DROOLS-2441 URL: https://issues.jboss.org/browse/DROOLS-2441 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.6.0.Final Reporter: Edson Tirelli Assignee: Matteo Mortari Priority: Blocker Fix For: 7.8.0.Final The FunctionDefNode is not using the kie container root classloader to load classes. I even added a comment for that, just a shame comments are not executable: https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m... {code:title=FunctionDefNode.java} // might need to explicitly use a classloader here Class<?> clazz = Class.forName( clazzName ); {code} To reproduce the problem, create a java class with a static method, add it to the kjar, create a DMN model that invokes that model, and try to execute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10156) Java EE 7 REST Service not called

by Viggo Navarsete (JIRA)

Viggo Navarsete created WFLY-10156: -------------------------------------- Summary: Java EE 7 REST Service not called Key: WFLY-10156 URL: https://issues.jboss.org/browse/WFLY-10156 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 12.0.0.Final Reporter: Viggo Navarsete Assignee: Jason Greene Current setup that works: Wildfly 10.0.0.Final Keycloak 3.4.3.Final - Deployed a REST endpoint (/zupplyio-orderservice/orders) to Wildfly 10.0.0.Final - Access the endpoint through a React app with a token received from Keycloak. - Returns a 200 http response with payload - undertow server.log: 19:35:33,356 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:35:33 +0200] "OPTIONS /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36" 19:35:33,994 INFO [stdout] (default task-2) *** Calling getOrders *** 19:35:34,121 INFO [io.undertow.accesslog] (default task-2) 127.0.0.1 [30/Mar/2018:19:35:34 +0200] "GET /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36" Setup that doesn't work: Wildfly 12.0.0.Final Keycloak 3.4.3.Final - Deployed a REST endpoint (/zupplyio-orderservice/orders) to Wildfly 10.0.0.Final - Access the endpoint through a React app with a token received from Keycloak. - Returns a 200 http response with NO payload - undertow server.log: 19:25:22,707 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:25:22 +0200] "OPTIONS /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36" 19:25:23,491 INFO [io.undertow.accesslog] (default task-1) 127.0.0.1 [30/Mar/2018:19:25:23 +0200] "GET /zupplyio-orderservice/orders HTTP/1.1" 200 "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Mobile Safari/537.36" As you can see from the server.log, my endpoint is probably not called in Wildfly 12.0.0.Final since the log output isn't written to server.log -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBEE-191) JAXB API loading default impl fails in Java 9

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBEE-191?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved JBEE-191. ------------------------------ Resolution: Won't Fix This doesn't need fixing. The platform JAXB provider can never be accessible from a non-platform API, so it's going to fail regardless. The correct fix is to ensure that the implementation is always on the API classpath no matter what. > JAXB API loading default impl fails in Java 9 > --------------------------------------------- > > Key: JBEE-191 > URL: https://issues.jboss.org/browse/JBEE-191 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jaxb-api > Affects Versions: jboss-jaxb-api_2.3_spec-1.0.1.Final > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: jboss-jaxb-api_2.3_spec-1.0.2.Final > > > The platform default provider is instantiated with a null class loader, which is not likely to work since the JDK will be linking against the wrong API. In addition, these classes are private in Java 9+ so even if it did link correctly, the instantiation would fail due to the non-exported package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBEE-191) JAXB API loading default impl fails in Java 9

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBEE-191?page=com.atlassian.jira.plugin.s... ] David Lloyd updated JBEE-191: ----------------------------- Fix Version/s: (was: jboss-jaxb-api_2.2_spec-1.0.5.Final) > JAXB API loading default impl fails in Java 9 > --------------------------------------------- > > Key: JBEE-191 > URL: https://issues.jboss.org/browse/JBEE-191 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jaxb-api > Affects Versions: jboss-jaxb-api_2.3_spec-1.0.1.Final > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: jboss-jaxb-api_2.3_spec-1.0.2.Final > > > The platform default provider is instantiated with a null class loader, which is not likely to work since the JDK will be linking against the wrong API. In addition, these classes are private in Java 9+ so even if it did link correctly, the instantiation would fail due to the non-exported package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBEE-191) JAXB API loading default impl fails in Java 9

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBEE-191?page=com.atlassian.jira.plugin.s... ] David Lloyd updated JBEE-191: ----------------------------- Affects Version/s: (was: jboss-jaxb-api_2.2_spec-1.0.4.Final) > JAXB API loading default impl fails in Java 9 > --------------------------------------------- > > Key: JBEE-191 > URL: https://issues.jboss.org/browse/JBEE-191 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Components: jboss-jaxb-api > Affects Versions: jboss-jaxb-api_2.3_spec-1.0.1.Final > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: jboss-jaxb-api_2.3_spec-1.0.2.Final > > > The platform default provider is instantiated with a null class loader, which is not likely to work since the JDK will be linking against the wrong API. In addition, these classes are private in Java 9+ so even if it did link correctly, the instantiation would fail due to the non-exported package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBEE-191) JAXB API loading default impl fails in Java 9

by David Lloyd (JIRA)

David Lloyd created JBEE-191: -------------------------------- Summary: JAXB API loading default impl fails in Java 9 Key: JBEE-191 URL: https://issues.jboss.org/browse/JBEE-191 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-jaxb-api Affects Versions: jboss-jaxb-api_2.2_spec-1.0.4.Final, jboss-jaxb-api_2.3_spec-1.0.1.Final Reporter: David Lloyd Assignee: David Lloyd Fix For: jboss-jaxb-api_2.2_spec-1.0.5.Final, jboss-jaxb-api_2.3_spec-1.0.2.Final The platform default provider is instantiated with a null class loader, which is not likely to work since the JDK will be linking against the wrong API. In addition, these classes are private in Java 9+ so even if it did link correctly, the instantiation would fail due to the non-exported package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 March 2018