December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14247) Error Page is not displayed when trying to access META-INF or WEB-INF

by Melvin Yam (Jira)

Melvin Yam created WFLY-14247: --------------------------------- Summary: Error Page is not displayed when trying to access META-INF or WEB-INF Key: WFLY-14247 URL: https://issues.redhat.com/browse/WFLY-14247 Project: WildFly Issue Type: Bug Affects Versions: 21.0.2.Final Reporter: Melvin Yam Assignee: Brian Stansberry Attachments: mywebapp.war I have a simple webapp war file with the following structure: {quote}{{Listing archive: mywebapp.war}}{{--}} {{Path = mywebapp.war}} {{Type = zip}} {{Physical Size = 1441}}{{Date Time Attr Size Compressed Name}} {{------------------- ----- ------------ ------------ ------------------------}} {{2020-12-23 20:09:20 ....A 18 18 error.html}} {{2020-12-23 20:09:02 ....A 18 18 index.html}} {{2020-12-23 20:10:13 D.... 0 0 META-INF}} {{2020-12-23 03:16:37 ....A 39 39 META-INF\MANIFEST.MF}} {{2020-12-23 20:12:38 D.... 0 0 WEB-INF}} {{2020-12-23 20:12:28 D.... 0 0 WEB-INF\classes}} {{2020-12-23 20:12:35 D.... 0 0 WEB-INF\lib}} {{2020-12-23 20:11:54 ....A 480 248 WEB-INF\web.xml}} {{------------------- ----- ------------ ------------ ------------------------}} {{2020-12-23 20:12:38 555 323 4 files, 4 folders}}{quote} In web.xml, it defines the error page: {quote}{{<?xml version="1.0" encoding="UTF-8"?>}} {{<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.jcp.org/xml/ns/javaee"}} {{ xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_4_0.xsd" version="4.0">}} {{ <display-name>mywebapp</display-name>}} {{ <welcome-file-list>}} {{ <welcome-file>index.html</welcome-file>}} {{ </welcome-file-list>}} {{ <error-page>}} {{ <location>/error.html</location>}} {{ </error-page>}} {{</web-app>}}{quote} After deploying the webapp successfully in local WildFly server. Accessing the following URL will trigger the error page to be shown: [http://127.0.0.1:8080/mywebapp/dummy] [http://127.0.0.1:8080/mywebapp/META-INF/MANIFEST.MF] [http://127.0.0.1:8080/mywebapp/META-INF/dummy/dummy] However, the following URL will NOT trigger the error page: [http://127.0.0.1:8080/mywebapp/META-INF] [http://127.0.0.1:8080/mywebapp/WEB-INF] [http://127.0.0.1:8080/mywebapp/WEB-INF/web.xml|http://127.0.0.1:8080/mywe...] [http://127.0.0.1:8080/mywebapp/WEB-INF/dummy/dummy] Instead, it just displays the text "404 - Not Found" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1248) Kiali soak test

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1248?page=com.atlassian.jira.plugi... ] Filip Brychta commented on SWSQE-1248: -------------------------------------- Created https://console-openshift-console.apps.kiali-soak.maistra.upshift.redhat.... > Kiali soak test > --------------- > > Key: SWSQE-1248 > URL: https://issues.redhat.com/browse/SWSQE-1248 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We need some long running instance of SM -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13995) Authentication on Management Console is not displayed in Chrome

by Yuriy Rudoy (Jira)

[ https://issues.redhat.com/browse/WFLY-13995?page=com.atlassian.jira.plugi... ] Yuriy Rudoy closed WFLY-13995. ------------------------------ Resolution: Done > Authentication on Management Console is not displayed in Chrome > --------------------------------------------------------------- > > Key: WFLY-13995 > URL: https://issues.redhat.com/browse/WFLY-13995 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 20.0.1.Final > Reporter: Yuriy Rudoy > Assignee: Harald Pehl > Priority: Major > Attachments: 2.JPG, hal.JPG, standalone.xml > > > I cant login to HAL in Chrome (86.0.4240.111) but it works in Firefox, IE, Edge > We have WildFly Full 20.0.1.Final and configured RBAC with LDAP (MS Active Directory) > Deleting history and cookies doesn't help. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5917) Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5917: ------------------------------------ Summary: Use LambdaConstraint predicate information to generate better comments in ANC for DMN Alpha Network Key: DROOLS-5917 URL: https://issues.redhat.com/browse/DROOLS-5917 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Luca Molteni Assignee: Luca Molteni It should be possible to put the actual constraints in comments in a generated ANC by leveraging the `PredicateInformation` class used in the executable model to give better error messages. In the compiled alpha network, instead of private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=Constraint for '0066e054-7241-4ccd-886d-ab6d7e08a99e' (index: null)] we should have private org.drools.modelcompiler.constraints.LambdaConstraint lambdaConstraint490; // [AlphaNode(490) constraint=x == true" (index: null)] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5916) Wrong BetaIndex with Or in executable-model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5916?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5916: ------------------------------------------- Fix version: 7.49.0.Final > Wrong BetaIndex with Or in executable-model > ------------------------------------------- > > Key: DROOLS-5916 > URL: https://issues.redhat.com/browse/DROOLS-5916 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.47.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > When a pattern inside "or" has a constraint which compares to a property of a bind variable, LambdaConstraint.indexingDeclaration is wrongly replaced (during LogicTransformer.transform()) so results in a wrong rule execution. > {noformat} > rule R > when > $p : Person(name == "Mark") or > ( $mark : Person(name == "Mark") > and > $p : Person(age == $mark.age) ) > $s: String(this == $p.name) > then > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5916) Wrong BetaIndex with Or in executable-model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5916?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-5916: ------------------------------------------- Fixed by https://github.com/kiegroup/drools/commit/425c77f012aa223be0f618f72206171... > Wrong BetaIndex with Or in executable-model > ------------------------------------------- > > Key: DROOLS-5916 > URL: https://issues.redhat.com/browse/DROOLS-5916 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.47.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > When a pattern inside "or" has a constraint which compares to a property of a bind variable, LambdaConstraint.indexingDeclaration is wrongly replaced (during LogicTransformer.transform()) so results in a wrong rule execution. > {noformat} > rule R > when > $p : Person(name == "Mark") or > ( $mark : Person(name == "Mark") > and > $p : Person(age == $mark.age) ) > $s: String(this == $p.name) > then > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5916) Wrong BetaIndex with Or in executable-model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5916?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5916: -------------------------------------- Description: When a pattern inside "or" has a constraint which compares to a property of a bind variable, LambdaConstraint.indexingDeclaration is wrongly replaced (during LogicTransformer.transform()) so results in a wrong rule execution. {noformat} rule R when $p : Person(name == "Mark") or ( $mark : Person(name == "Mark") and $p : Person(age == $mark.age) ) $s: String(this == $p.name) then ... {noformat} was: When a pattern inside "or" has a constraint which compares to a property of a bind variable, its betaIndex is wrongly processed (during LogicTransformer.transform()) so results in a wrong rule execution. {noformat} rule R when $p : Person(name == "Mark") or ( $mark : Person(name == "Mark") and $p : Person(age == $mark.age) ) $s: String(this == $p.name) then ... {noformat} > Wrong BetaIndex with Or in executable-model > ------------------------------------------- > > Key: DROOLS-5916 > URL: https://issues.redhat.com/browse/DROOLS-5916 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.47.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > When a pattern inside "or" has a constraint which compares to a property of a bind variable, LambdaConstraint.indexingDeclaration is wrongly replaced (during LogicTransformer.transform()) so results in a wrong rule execution. > {noformat} > rule R > when > $p : Person(name == "Mark") or > ( $mark : Person(name == "Mark") > and > $p : Person(age == $mark.age) ) > $s: String(this == $p.name) > then > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5916) Wrong BetaIndex with Or in executable-model

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5916?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5916: -------------------------------------- Summary: Wrong BetaIndex with Or in executable-model (was: Wrong BetaIndex with Or in executabel-model) > Wrong BetaIndex with Or in executable-model > ------------------------------------------- > > Key: DROOLS-5916 > URL: https://issues.redhat.com/browse/DROOLS-5916 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.47.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > When a pattern inside "or" has a constraint which compares to a property of a bind variable, its betaIndex is wrongly processed (during LogicTransformer.transform()) so results in a wrong rule execution. > {noformat} > rule R > when > $p : Person(name == "Mark") or > ( $mark : Person(name == "Mark") > and > $p : Person(age == $mark.age) ) > $s: String(this == $p.name) > then > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5916) Wrong BetaIndex with Or in executabel-model

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5916: ----------------------------------------- Summary: Wrong BetaIndex with Or in executabel-model Key: DROOLS-5916 URL: https://issues.redhat.com/browse/DROOLS-5916 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.47.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi When a pattern inside "or" has a constraint which compares to a property of a bind variable, its betaIndex is wrongly processed (during LogicTransformer.transform()) so results in a wrong rule execution. {noformat} rule R when $p : Person(name == "Mark") or ( $mark : Person(name == "Mark") and $p : Person(age == $mark.age) ) $s: String(this == $p.name) then ... {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-4674) Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path

by Hai Tran (Jira)

[ https://issues.redhat.com/browse/WFCORE-4674?page=com.atlassian.jira.plug... ] Hai Tran commented on WFCORE-4674: ---------------------------------- [~jamezp] thanks for the information! > Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path > -------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4674 > URL: https://issues.redhat.com/browse/WFCORE-4674 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: OpenShift, jdk11 > Fix For: 13.0.0.Beta1, 13.0.0.Final > > Attachments: standalone.conf, standalone.conf, wildfly-bugreport.zip > > > If the log manager is on the boot class path with Java 11, {{-Xbootclasspath/a:jboss-logmanager.jar}}, and a custom handler, formatter or filter is used the server will fail to boot as the log manager can't see the types in jboss-modules. This seems due to the fact that the log manager is on the boot class path and jboss-modules is on the system class path. > Example exception: > {code} > Failed to read or configure the org.jboss.logmanager.LogManager > java.lang.IllegalArgumentException: Failed to load module "org.jboss.logmanager" for formatter "JSON" > at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:65) > at org.jboss.logmanager.config.FormatterConfigurationImpl.<init>(FormatterConfigurationImpl.java:30) > at org.jboss.logmanager.config.LogContextConfigurationImpl.addFormatterConfiguration(LogContextConfigurationImpl.java:172) > at org.jboss.logmanager.PropertyConfigurator.configureFormatter(PropertyConfigurator.java:631) > at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:701) > at org.jboss.logmanager.PropertyConfigurator.configureLogger(PropertyConfigurator.java:583) > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:521) > at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97) > at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:170) > at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:132) > at java.util.logging.LogManager$3.run(LogManager.java:399) > at java.util.logging.LogManager$3.run(LogManager.java:396) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:396) > at java.util.logging.LogManager.access$800(LogManager.java:145) > at java.util.logging.LogManager$2.run(LogManager.java:345) > at java.security.AccessController.doPrivileged(Native Method) > at java.util.logging.LogManager.ensureLogManagerInitialized(LogManager.java:338) > at java.util.logging.LogManager.getLogManager(LogManager.java:378) > at org.jboss.modules.Main.main(Main.java:523) > Caused by: java.lang.NoClassDefFoundError: org/jboss/modules/ModuleLoader > at org.jboss.logmanager.config.AbstractPropertyConfiguration$ModuleFinder.getClassLoader(AbstractPropertyConfiguration.java:556) > at org.jboss.logmanager.config.AbstractPropertyConfiguration.<init>(AbstractPropertyConfiguration.java:63) > ... 19 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 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 December 2020