October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4599) [DMN Designer] Decision Tables: Hit Policy select drop-down remains visible if popover closed

by Michael Anstis (Jira)

Michael Anstis created DROOLS-4599: -------------------------------------- Summary: [DMN Designer] Decision Tables: Hit Policy select drop-down remains visible if popover closed Key: DROOLS-4599 URL: https://issues.jboss.org/browse/DROOLS-4599 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.28.0.Final Reporter: Michael Anstis Assignee: Michael Anstis The _drop down_ component of the Hit Policy _select_ component remains visible if the popover is dismissed by clicking elsewhere (outside the popover). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2387) Message from a non-member causes FD_ALL to continually suspect it

by Dennis Reed (Jira)

Dennis Reed created JGRP-2387: --------------------------------- Summary: Message from a non-member causes FD_ALL to continually suspect it Key: JGRP-2387 URL: https://issues.jboss.org/browse/JGRP-2387 Project: JGroups Issue Type: Bug Affects Versions: 4.0.1 Reporter: Dennis Reed Assignee: Bela Ban If a FD_SOCK control message from a non-member is seen by FD_SOCK, it will start continually suspecting that node. If msg_counts_as_heartbeat=true then any message from a non-member triggers the issue. The issue is cleared on the next view change. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11978) EAR with 2+ JPA does not shutdown cleanly

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11978?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-11978: ------------------------------------- [~dlmiles] Could you please try to recreate with WildFly 18.0.0.Final, which should be released soon. Thanks, Scott > EAR with 2+ JPA does not shutdown cleanly > ----------------------------------------- > > Key: WFLY-11978 > URL: https://issues.jboss.org/browse/WFLY-11978 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 16.0.0.Final > Environment: Windows JDK8 WF16 > Reporter: Darryl Miles > Assignee: Scott Marlow > Priority: Major > Attachments: td8948.txt > > > EAR with 2+ JPA does not shutdown cleanly. > I see in the logs each JPA project have an entry: > WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'blah....jpa.project1' > WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service 'blah....jpa.project2' > then a few lines later: > WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'blah....jpa.project2' > I never see the "phase 1 of 2" entry for "jpa.project1" in the log. > The container will wait 300 seconds and timeout. > The management console during the time shows > Operation: undeploy > Execution Status: awaiting-stablility. > The container is killed and the configuration.xml still contains the EAR deployment info, as undeploy did not complete. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11887) [CVE-2016-3720]: Usage of vulnarable Jackson 1.9.13 libraries

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11887?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11887: ------------------------------------ Attachment: redhat-0006.txt > [CVE-2016-3720]: Usage of vulnarable Jackson 1.9.13 libraries > ------------------------------------------------------------- > > Key: WFLY-11887 > URL: https://issues.jboss.org/browse/WFLY-11887 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 14.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 18.0.0.Final > > Attachments: redhat-0006.txt > > > We have a couple of high prio vulnerabilities reported around usage of Jackson libraries on WildFly with regards to CVE-2016-3720: > {code:java} > jackson-core-asl-1.9.13.jar > jackson-jaxrs-1.9.13.jar > jackson-mapper-asl-1.9.13.jar > jackson-xc-1.9.13.jar > {code} > Could you please review and remove/update them? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11887) [CVE-2016-3720]: Usage of vulnarable Jackson 1.9.13 libraries

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11887?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11887: ------------------------------------ Security: (was: Security Issue) > [CVE-2016-3720]: Usage of vulnarable Jackson 1.9.13 libraries > ------------------------------------------------------------- > > Key: WFLY-11887 > URL: https://issues.jboss.org/browse/WFLY-11887 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 14.0.0.Final > Reporter: Radoslav Ivanov > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 18.0.0.Final > > > We have a couple of high prio vulnerabilities reported around usage of Jackson libraries on WildFly with regards to CVE-2016-3720: > {code:java} > jackson-core-asl-1.9.13.jar > jackson-jaxrs-1.9.13.jar > jackson-mapper-asl-1.9.13.jar > jackson-xc-1.9.13.jar > {code} > Could you please review and remove/update them? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12628) Downgrade MicroProfile Health to 2.0.1

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12628?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12628: ------------------------------------ Priority: Blocker (was: Major) > Downgrade MicroProfile Health to 2.0.1 > -------------------------------------- > > Key: WFLY-12628 > URL: https://issues.jboss.org/browse/WFLY-12628 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Health > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 18.0.0.Final > > > MP Health was upgraded to 2.1 in WFLY-12555 at the same time that smallrye-health was upgrade to 2.0.0 in WFLY-12554 > That was a mistake as smallrye-health is depending on MP Health 2.0.1. > There is no harm on staying on MP Health 2.1 as the API changes are internal to the API and do not require any implementation from the provider: > https://github.com/eclipse/microprofile-health/compare/2.0.1...2.1 > However, if we decide to keep WildFly 18 under the same MP Umbrella release (3.0) at the moment, it might be better to downgrade to 2.0.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12628) Downgrade MicroProfile Health to 2.0.1

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12628?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12628: ------------------------------------ Fix Version/s: 18.0.0.Final > Downgrade MicroProfile Health to 2.0.1 > -------------------------------------- > > Key: WFLY-12628 > URL: https://issues.jboss.org/browse/WFLY-12628 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Health > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 18.0.0.Final > > > MP Health was upgraded to 2.1 in WFLY-12555 at the same time that smallrye-health was upgrade to 2.0.0 in WFLY-12554 > That was a mistake as smallrye-health is depending on MP Health 2.0.1. > There is no harm on staying on MP Health 2.1 as the API changes are internal to the API and do not require any implementation from the provider: > https://github.com/eclipse/microprofile-health/compare/2.0.1...2.1 > However, if we decide to keep WildFly 18 under the same MP Umbrella release (3.0) at the moment, it might be better to downgrade to 2.0.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12348) JPA statistics fix (WFLY-10964) should be applied to JPA 2.1 as well

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12348?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12348: ------------------------------------- The [https://github.com/hibernate/hibernate-orm/tree/master/hibernate-jipijapa...] is a fork, I wanted to move all of the Hibernate integration code there, but I found out after that being discussed, that we needed to keep that code in WildFly, for addressing clustering issues. So, the Hibernate copy of that code, is a mostly for the Hibernate testsuite but could possibly be used by some users. The sources in Hibernate use tabs instead of spaces and have other cosmetic differences. I can mention some steps that you could take to sync changes made in WildFly with the forked code in the Hibernate project, if your interested in creating a Hibernate ORM pull request for that. Could you please verify that [https://github.com/scottmarlow/wildfly/tree/WFLY-12348_jpa2.1] contains the changes that you had in mind and work for you? I'll create a pull request for the change after I hear back from you. Thanks for reporting this! Scott > JPA statistics fix (WFLY-10964) should be applied to JPA 2.1 as well > -------------------------------------------------------------------- > > Key: WFLY-12348 > URL: https://issues.jboss.org/browse/WFLY-12348 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 17.0.1.Final > Reporter: Jippe Holwerda > Assignee: Scott Marlow > Priority: Major > > Microprofile Metrics in Wildfly 17.0.1 in combination with JPA 2.1 is currently broken. The fix done in WFLY-10964 (https://github.com/wildfly/wildfly/commit/9dac9810796469ab45cb2b6e0fde926...) should be applied to the JPA 2.1 version (wildfly/jpa/hibernate5) as well. > Also, the same faulty code is present in Hibernate: https://github.com/hibernate/hibernate-orm/tree/master/hibernate-jipijapa... > Not sure why it is in there as well, but it probably should be fixed or removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2386) Support for encryption ciphers that require an initialization vector

by Nick Sawadsky (Jira)

[ https://issues.jboss.org/browse/JGRP-2386?page=com.atlassian.jira.plugin.... ] Nick Sawadsky commented on JGRP-2386: ------------------------------------- Thanks [~belaban]! Linking the pull request: https://github.com/belaban/JGroups/pull/441 > Support for encryption ciphers that require an initialization vector > -------------------------------------------------------------------- > > Key: JGRP-2386 > URL: https://issues.jboss.org/browse/JGRP-2386 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.1.5, 3.6.19 > Reporter: Nick Sawadsky > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.6 > > > By default, Encrypt sets sym_algorithm to "AES". As a result, the default cipher mode is used, which is ECB. ECB encrypts a given plaintext block to the same ciphertext every time, which can allow attackers to see [patterns in messages being exchanged|https://crypto.stackexchange.com/questions/20941/why-shouldnt-i...]. > Modes like CBC, that use a random initialization vector (IV) avoid this problem (assuming a different IV is used for each message). > It would be good to modify Encrypt to support ciphers that require an IV, such as AES/CBC/PKCS5Padding. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12629) MicroProfile capability names are mangled "org.wildlfy..."

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12629?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12629: ---------------------------------- Description: Namely: org.wildlfy.microprofile.config org.wildlfy.microprofile.health.reporter org.wildlfy.extension.microprofile.metrics.wildfly-collector Lets fix these up before we properly support this since WF 19. was: Namely: org.wildlfy.microprofile.config org.wildlfy.microprofile.health.reporter org.wildlfy.extension.microprofile.metrics.wildfly-collector > MicroProfile capability names are mangled "org.wildlfy..." > ---------------------------------------------------------- > > Key: WFLY-12629 > URL: https://issues.jboss.org/browse/WFLY-12629 > Project: WildFly > Issue Type: Bug > Components: MP Config, MP Health, MP Metrics > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Namely: > org.wildlfy.microprofile.config > org.wildlfy.microprofile.health.reporter > org.wildlfy.extension.microprofile.metrics.wildfly-collector > Lets fix these up before we properly support this since WF 19. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 October 2019