May 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13380) Upgrade dom4j from 2.1.1 to 2.1.3

by Radoslav Ivanov (Jira)

[ https://issues.redhat.com/browse/WFLY-13380?page=com.atlassian.jira.plugi... ] Radoslav Ivanov commented on WFLY-13380: ---------------------------------------- [~brian.stansberry], there is a critical CVE-2020-10683 reported for dom4j-2.1.1, which is available on previous versions of WildFly. It could be mitigated by "enabling safe bahavior": {code:java} dom4j before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j. {code} Could you please provide a note/instruction on how we can apply/mitigate on existing older versions of WildFly? > Upgrade dom4j from 2.1.1 to 2.1.3 > --------------------------------- > > Key: WFLY-13380 > URL: https://issues.redhat.com/browse/WFLY-13380 > Project: WildFly > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Labels: downstream_dependency > Fix For: 19.1.0.Final, 20.0.0.Beta1 > > > https://github.com/dom4j/dom4j/compare/version-2.1.1...version-2.1.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12516) EJBContext principal is not popped back after invoking another EJB using a different Security Domain

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12516?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12516: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13281 (was: https://github.com/wildfly/wildfly/pull/13271) > EJBContext principal is not popped back after invoking another EJB using a different Security Domain > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12516 > URL: https://issues.redhat.com/browse/WFLY-12516 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13453) Near cache should auto-enable when hotrod session manager is used.

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13453?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13453: -------------------------------- Summary: Near cache should auto-enable when hotrod session manager is used. (was: Near cache should auto-enable for when hotrod session manager is used.) > Near cache should auto-enable when hotrod session manager is used. > ------------------------------------------------------------------ > > Key: WFLY-13453 > URL: https://issues.redhat.com/browse/WFLY-13453 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Currently, the logic to create a custom near cache based on the web deployment's max-active-sessions gets bypassed if the associated cache manager does not explicitly enable near cache. > This results in unexpected behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13455) The 'Extension' discussion of the Admin Guide should clarify what an extension is

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13455: --------------------------------------- Summary: The 'Extension' discussion of the Admin Guide should clarify what an extension is Key: WFLY-13455 URL: https://issues.redhat.com/browse/WFLY-13455 Project: WildFly Issue Type: Enhancement Components: Documentation, Management Reporter: Brian Stansberry Assignee: Brian Stansberry https://docs.wildfly.org/19.1/Admin_Guide.html#extensions doesn't really explain what an Extension is so it's easy for people to think it's talking about any module added to the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13454) Remote cache store should never use a near cache

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13454: ----------------------------------- Summary: Remote cache store should never use a near cache Key: WFLY-13454 URL: https://issues.redhat.com/browse/WFLY-13454 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 19.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Using a near cache with a remote cache store is pointless, as the parent cache already serves this function. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0

by Ashley Abdel-Sayed (Jira)

[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed commented on WFLY-13256: ------------------------------------------- [~jim.ma] I was wondering if you had any thoughts on my last comment? > Upgrade bouncycastle to 1.65.0 > ------------------------------ > > Key: WFLY-13256 > URL: https://issues.redhat.com/browse/WFLY-13256 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, Server > Reporter: Bartosz Spyrko-Smietanko > Assignee: Brian Stansberry > Priority: Blocker > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > Attachments: handshake-error.log, handshake-success.log > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13453) Near cache should auto-enable for when hotrod session manager is used.

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13453: ----------------------------------- Summary: Near cache should auto-enable for when hotrod session manager is used. Key: WFLY-13453 URL: https://issues.redhat.com/browse/WFLY-13453 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 19.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, the logic to create a custom near cache based on the web deployment's max-active-sessions gets bypassed if the associated cache manager does not explicitly enable near cache. This results in unexpected behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13452) RemoteCacheContainer.getTransactionManager() always returns null

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13452: ----------------------------------- Summary: RemoteCacheContainer.getTransactionManager() always returns null Key: WFLY-13452 URL: https://issues.redhat.com/browse/WFLY-13452 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 19.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5320) Rule compilation error when binding fields indexed with square brackets from different Fact types

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5320?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5320: -------------------------------- Sprint: 2020 Week 19-21 (from May 4) > Rule compilation error when binding fields indexed with square brackets from different Fact types > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-5320 > URL: https://issues.redhat.com/browse/DROOLS-5320 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.37.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: binding-field-indexed-with-square-brackets2.zip > > > Similar to DROOLS-5216, but occurs when binding the field from a different Fact type. > Example: > {noformat} > rule "binding field indexed with square brackets from different fact type" > when Pojo2($firstItem : simpleInt) > Pojo($firstItem == integerList[this.integerList.size()-1]) > then > end > {noformat} > Error: > {noformat} > Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 > text=Comparison operation requires compatible types. Found int and class java.lang.Object] > {noformat} > The example works fine when compiling without executable model. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5320) Rule compilation error when binding fields indexed with square brackets from different Fact types

by Matteo Casalino (Jira)

[ https://issues.redhat.com/browse/DROOLS-5320?page=com.atlassian.jira.plug... ] Matteo Casalino updated DROOLS-5320: ------------------------------------ Description: Similar to DROOLS-5216, but occurs when binding the field from a different Fact type. Example: {noformat} rule "binding field indexed with square brackets from different fact type" when Pojo2($firstItem : simpleInt) Pojo($firstItem == integerList[this.integerList.size()-1]) then end {noformat} Error: {noformat} Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Comparison operation requires compatible types. Found int and class java.lang.Object] {noformat} The example works fine when compiling without executable model. was: Similar to DROOLS-5216, but occurs when binding the collection from a different Fact type. Example: {noformat} rule "binding field indexed with square brackets from different fact type" when Pojo2($firstItem : simpleInt) Pojo($firstItem == integerList[this.integerList.size()-1]) then end {noformat} Error: {noformat} Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 text=Comparison operation requires compatible types. Found int and class java.lang.Object] {noformat} The example works fine when compiling without executable model. > Rule compilation error when binding fields indexed with square brackets from different Fact types > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-5320 > URL: https://issues.redhat.com/browse/DROOLS-5320 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.37.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: binding-field-indexed-with-square-brackets2.zip > > > Similar to DROOLS-5216, but occurs when binding the field from a different Fact type. > Example: > {noformat} > rule "binding field indexed with square brackets from different fact type" > when Pojo2($firstItem : simpleInt) > Pojo($firstItem == integerList[this.integerList.size()-1]) > then > end > {noformat} > Error: > {noformat} > Message [id=1, kieBase=binding-field-indexed-with-square-brackets, level=ERROR, path=org/drools/reproducer/rules.drl, line=-1, column=0 > text=Comparison operation requires compatible types. Found int and class java.lang.Object] > {noformat} > The example works fine when compiling without executable model. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 May 2020