[JBoss JIRA] (WFLY-9773) Bug in Module Classloading
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-9773?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-9773:
-------------------------------
Component/s: Web (Undertow)
(was: Class Loading)
> Bug in Module Classloading
> --------------------------
>
> Key: WFLY-9773
> URL: https://issues.jboss.org/browse/WFLY-9773
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final, 11.0.0.Final
> Environment: Windows 10
> Java 1.8.0_112
> WildFly 10.1.Final
> Reporter: Thomas Isaksen
> Assignee: David Lloyd
> Attachments: IgniteHandler.zip, gatekeeper-token-config.xml.zip
>
>
> Custom module class loading fails with ClassNotFoundException
> I have attached a reproducible example here but it is also available on the forum thread mentioned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9773) Bug in Module Classloading
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-9773?page=com.atlassian.jira.plugin.... ]
jaikiran pai updated WFLY-9773:
-------------------------------
Affects Version/s: 11.0.0.Final
> Bug in Module Classloading
> --------------------------
>
> Key: WFLY-9773
> URL: https://issues.jboss.org/browse/WFLY-9773
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final, 11.0.0.Final
> Environment: Windows 10
> Java 1.8.0_112
> WildFly 10.1.Final
> Reporter: Thomas Isaksen
> Assignee: David Lloyd
> Attachments: IgniteHandler.zip, gatekeeper-token-config.xml.zip
>
>
> Custom module class loading fails with ClassNotFoundException
> I have attached a reproducible example here but it is also available on the forum thread mentioned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9773) Bug in Module Classloading
by Thomas Isaksen (JIRA)
[ https://issues.jboss.org/browse/WFLY-9773?page=com.atlassian.jira.plugin.... ]
Thomas Isaksen updated WFLY-9773:
---------------------------------
Steps to Reproduce:
unzip IgniteHandler.zip into $WILDFLY_HOME/modules
set $IGNITE_HOME and unzip gatekeeper-token-config.xml.zip to that location
Add a filter and a filter-red in standalone.xml as follows:
<filter-ref name="igniteHandler" priority="100"/>
<filter name="igniteHandler" class-name="no.toyota.gatekeeper.handler.IgniteHandler" module="no.toyota.gatekeeper:simplified"/>
was:Download
Workaround Description:
A workaround was provided by https://developer.jboss.org/people/jaikiran
public IgniteHandler() {
final ClassLoader oldCL = Thread.currentThread().getContextClassLoader();
try {
Thread.currentThread().setContextClassLoader(TokenBouncerHandler.class.getClassLoader());
// rest of your existing code goes here
....
} finally {
Thread.currentThread().setContextClassLoader(oldCL);
}
> Bug in Module Classloading
> --------------------------
>
> Key: WFLY-9773
> URL: https://issues.jboss.org/browse/WFLY-9773
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 10.1.0.Final
> Environment: Windows 10
> Java 1.8.0_112
> WildFly 10.1.Final
> Reporter: Thomas Isaksen
> Assignee: David Lloyd
> Attachments: IgniteHandler.zip, gatekeeper-token-config.xml.zip
>
>
> Custom module class loading fails with ClassNotFoundException
> I have attached a reproducible example here but it is also available on the forum thread mentioned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2305) Drools compiler does not recognize Java 9
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2305?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-2305.
---------------------------------
Resolution: Done
Fixed by https://github.com/kiegroup/drools/commit/857c70589e95f05cb1520d7e59bcea8...
> Drools compiler does not recognize Java 9
> -----------------------------------------
>
> Key: DROOLS-2305
> URL: https://issues.jboss.org/browse/DROOLS-2305
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.5.0.Final
> Reporter: Jon Kranes
> Assignee: Mario Fusco
>
> The Drools compiler class org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration
> does not include Java 9 as a valid language level. Instead, when run using Java 9, the assumed java version is set to the default value of "1.7".
> As a consequence, when compiling a rules file requiring Java 8 specific language features, the compilation will fail. For example, if a rule RHS contains the statement:
> {code:java}
> Arrays.asList("a","b","c").forEach(System.out::println);
> {code}
> The rule compilation fails with the error:
> {code:java}
> [ERROR] Unable to build KieBaseModel:default
> Rule Compilation error : [Rule name='test']
> defaultpkg/Rule_test959974052.java (7:387) : Method references are allowed only at source level 1.8 or above
> {code}
> The problem can be worked around by adding a configuration file META-INF/kie.properties.conf containing the line:
> {code:java}
> drools.dialect.java.compiler.lnglevel = 1.8
> {code}
> The Drools compiler code will use this value instead of the System "java.version" value, avoiding the problem.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (DROOLS-2309) Drools compiler does not recognize Java 9
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-2309:
-----------------------------------
Summary: Drools compiler does not recognize Java 9
Key: DROOLS-2309
URL: https://issues.jboss.org/browse/DROOLS-2309
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.5.0.Final
Reporter: Jon Kranes
Assignee: Mario Fusco
The Drools compiler class org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration
does not include Java 9 as a valid language level. Instead, when run using Java 9, the assumed java version is set to the default value of "1.7".
As a consequence, when compiling a rules file requiring Java 8 specific language features, the compilation will fail. For example, if a rule RHS contains the statement:
{code:java}
Arrays.asList("a","b","c").forEach(System.out::println);
{code}
The rule compilation fails with the error:
{code:java}
[ERROR] Unable to build KieBaseModel:default
Rule Compilation error : [Rule name='test']
defaultpkg/Rule_test959974052.java (7:387) : Method references are allowed only at source level 1.8 or above
{code}
The problem can be worked around by adding a configuration file META-INF/kie.properties.conf containing the line:
{code:java}
drools.dialect.java.compiler.lnglevel = 1.8
{code}
The Drools compiler code will use this value instead of the System "java.version" value, avoiding the problem.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9773) Bug in Module Classloading
by Thomas Isaksen (JIRA)
Thomas Isaksen created WFLY-9773:
------------------------------------
Summary: Bug in Module Classloading
Key: WFLY-9773
URL: https://issues.jboss.org/browse/WFLY-9773
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 10.1.0.Final
Environment: Windows 10
Java 1.8.0_112
WildFly 10.1.Final
Reporter: Thomas Isaksen
Assignee: David Lloyd
Attachments: IgniteHandler.zip, gatekeeper-token-config.xml.zip
Custom module class loading fails with ClassNotFoundException
I have attached a reproducible example here but it is also available on the forum thread mentioned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3522) Module dependency order for a deployment is wrong
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3522?page=com.atlassian.jira.plugi... ]
Jeff Mesnil updated WFCORE-3522:
--------------------------------
Fix Version/s: 4.0.0.Beta1
> Module dependency order for a deployment is wrong
> -------------------------------------------------
>
> Key: WFCORE-3522
> URL: https://issues.jboss.org/browse/WFCORE-3522
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.8.Final
> Reporter: Ken Finnigan
> Assignee: David Lloyd
> Priority: Blocker
> Fix For: 4.0.0.Beta1
>
>
> Within WildFly Swarm we need the ability to override the `javax.ws.rs.client.ClientBuilder` service file for a deployment to provide custom handling for implementing Eclipse MicroProfile.
> With a service file present in the deployment, the existing RESTEasy service file is always found first because the deployment module is added as a dependency after other non local dependencies. See https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/...
> After discussing with [~dmlloyd] on IRC, he agreed this was a bug and a better solution was for the deployment's dependency to always be first if `isLocalLast()` is false, and instead remove any spec packages that might be present on the deployment path instead.
> He explained the purpose of this ordering was to prevent a user deploying `javax.servlet.api` and breaking things, but it appears this can be achieved by alternative methods.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3584) Stability monitor should be exposed to DUP's
by Stuart Douglas (JIRA)
Stuart Douglas created WFCORE-3584:
--------------------------------------
Summary: Stability monitor should be exposed to DUP's
Key: WFCORE-3584
URL: https://issues.jboss.org/browse/WFCORE-3584
Project: WildFly Core
Issue Type: Bug
Reporter: Stuart Douglas
Assignee: Stuart Douglas
There are some use cases (e.g. shared java:global bindings) that result in services being installed outside of a deployments ServiceTarget. This means that are not added to the stability monitor, which results in intermittent test failures due to a false stability being achieved before all services have come up.
At present it is not possible to access this stability monitor, so there is no way to fix this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months