January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12885) Upgrade JSF based on Mojarra 2.3.9.SP05 to 2.3.9.SP06

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12885?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12885: --------------------------------- Summary: Upgrade JSF based on Mojarra 2.3.9.SP05 to 2.3.9.SP06 (was: Upgrade JSF based on Mojarra 2.3.9.SP05 to ...) > Upgrade JSF based on Mojarra 2.3.9.SP05 to 2.3.9.SP06 > ----------------------------------------------------- > > Key: WFLY-12885 > URL: https://issues.redhat.com/browse/WFLY-12885 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Farah Juma > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-482: -------------------------------------- [~walkerca] I don't think so as the {{Appender}} interface is part of the {{org.apache.logging.log4j:log4j-core}} project which is a full log manager implementation. There is no current plan to fork log4j2 which would be required for that to happen I'd think. It's something that could be researched at some point though. For the integration the main idea is that if you just use the {{log4j-api}} then it will have an implementation that writes to the jboss-logmanager. One idea I would like to implement and do have it working, but it's a bit clumsy, is if you include {{log4j-core}} in a deployment that it would take over the log manager duties for the deployment. Do you have some expectations on how you'd expect it to work? That's the main thing that has held up the integration work, besides time :), is I'm not sure what end users expect. > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.redhat.com/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Major > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12967) Improve tests in integration/multinode/../transaction/async/TransactionPropagationTestCase

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-12967?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFLY-12967: ------------------------------ Description: This is for tests in {{testsuite/integration/multinode/src/test/java/org/jboss/as/test/multinode/transaction/async/TransactionPropagationTestCase.java}} * replace the {{sleep()}} in test method with {{Future.get()}} after calling async methods * improve jndi lookup ** close context ** cache context at class level ** replace with @EJB injection > Improve tests in integration/multinode/../transaction/async/TransactionPropagationTestCase > ------------------------------------------------------------------------------------------ > > Key: WFLY-12967 > URL: https://issues.redhat.com/browse/WFLY-12967 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 19.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > > This is for tests in {{testsuite/integration/multinode/src/test/java/org/jboss/as/test/multinode/transaction/async/TransactionPropagationTestCase.java}} > * replace the {{sleep()}} in test method with {{Future.get()}} after calling async methods > * improve jndi lookup > ** close context > ** cache context at class level > ** replace with @EJB injection -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12967) Improve tests in integration/multinode/../transaction/async/TransactionPropagationTestCase

by Cheng Fang (Jira)

Cheng Fang created WFLY-12967: --------------------------------- Summary: Improve tests in integration/multinode/../transaction/async/TransactionPropagationTestCase Key: WFLY-12967 URL: https://issues.redhat.com/browse/WFLY-12967 Project: WildFly Issue Type: Enhancement Components: EJB Affects Versions: 19.0.0.Beta1 Reporter: Cheng Fang Assignee: Cheng Fang -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-482) Add log4j2 support for WildFly

by Carl Walker (Jira)

[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] Carl Walker commented on WFCORE-482: ------------------------------------ Will we be able to use the Management Console to set Log4J2 Loggers? How will the integration look if WF packages Log4J2 or if our WARs and EARs package Log4J2? > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.redhat.com/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Task > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Major > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12966) Upgrade Hibernate ORM from 5.3.14 to 5.3.15

by Gail Badner (Jira)

Gail Badner created WFLY-12966: ---------------------------------- Summary: Upgrade Hibernate ORM from 5.3.14 to 5.3.15 Key: WFLY-12966 URL: https://issues.redhat.com/browse/WFLY-12966 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Gail Badner Assignee: Gail Badner Fix For: 19.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12965) (7.3.z) org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase fails

by Ilia Vassilev (Jira)

Ilia Vassilev created WFLY-12965: ------------------------------------ Summary: (7.3.z) org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase fails Key: WFLY-12965 URL: https://issues.redhat.com/browse/WFLY-12965 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Ilia Vassilev Assignee: Gail Badner The following fixes in Hibernate ORM 5.3.15.Final cause {{org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase}} to fail: https://hibernate.atlassian.net/browse/HHH-13432 https://hibernate.atlassian.net/browse/HHH-12858 There are 2 assertions in the test that fail with those fixes because the Map returned by {{EntityManagerFactory#getProperties}}: 1) does not contain a value for property {{hibernate.connection.driver_class}}. 2) contains a property for {{hibernate.connection.datasource}} that is a {{WildFlyDataSource}} instance, instead of the String {{"java:jboss/datasources/ExampleDS"}}. For 1), Hibernate ORM removes the {{hibernate.connection.driver_class}} property from its copy because it makes no sense when a datasource is provided via {{hibernate.connection.datasource}}. For 2), Hibernate ORM replaces the {{String}} value for {{hibernate.connection.datasource}} with the {{WildFlyDataSource}} instance. I reviewed the JPA 2.2 specification and discussed this issue with [~smarlow], and we agreed that these were acceptable changes to the copy of properties that Hibernate ORM contains. I have confirmed that these fixes do not cause any Jakarta standalone TCK failures. The fix will involve replacing references to those properties with properties that Hibernate ORM does not change. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12964) org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase fails

by Gail Badner (Jira)

Gail Badner created WFLY-12964: ---------------------------------- Summary: org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase fails Key: WFLY-12964 URL: https://issues.redhat.com/browse/WFLY-12964 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Gail Badner Assignee: Gail Badner The following fixes in Hibernate ORM 5.3.15.Final cause {{org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase}} to fail: https://hibernate.atlassian.net/browse/HHH-13432 https://hibernate.atlassian.net/browse/HHH-12858 There are 2 assertions in the test that fail with those fixes because the Map returned by {{EntityManagerFactory#getProperties}}: 1) does not contain a value for property {{hibernate.connection.driver_class}}. 2) contains a property for {{hibernate.connection.datasource}} that is a {{WildFlyDataSource}} instance, instead of the String {{"java:jboss/datasources/ExampleDS"}}. For 1), Hibernate ORM removes the {{hibernate.connection.driver_class}} property from its copy because it makes no sense when a datasource is provided via {{hibernate.connection.datasource}}. For 2), Hibernate ORM replaces the {{String}} value for {{hibernate.connection.datasource}} with the {{WildFlyDataSource}} instance. I reviewed the JPA 2.2 specification and discussed this issue with [~smarlow], and we agreed that these were acceptable changes to the copy of properties that Hibernate ORM contains. I have confirmed that these fixes do not cause any Jakarta standalone TCK failures. The fix will involve replacing references to those properties with properties that Hibernate ORM does not change. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12963) Use maven project.groupId for wildfly-microprofile-jwt-smallrye dependencies

by Yeray Borges (Jira)

Yeray Borges created WFLY-12963: ----------------------------------- Summary: Use maven project.groupId for wildfly-microprofile-jwt-smallrye dependencies Key: WFLY-12963 URL: https://issues.redhat.com/browse/WFLY-12963 Project: WildFly Issue Type: Task Components: Build System Reporter: Yeray Borges Assignee: Yeray Borges The use of maven property ${project.groupid} instead of the hardcoded org.wildfly group id facilitates the transition to the product branches. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4935) Memory leak in PrometheusKieServerExtension

by Karel Suta (Jira)

Karel Suta created DROOLS-4935: ---------------------------------- Summary: Memory leak in PrometheusKieServerExtension Key: DROOLS-4935 URL: https://issues.redhat.com/browse/DROOLS-4935 Project: Drools Issue Type: Bug Components: kie server Affects Versions: 7.31.0.Final Reporter: Karel Suta Assignee: Maciej Swiderski Prometheus Kie server extensions contains support for custom metrics [1]. These metrics are added when a new container is called [2]. However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 January 2020