April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13389) (7.3.z) WFLY-13273 - Create tests for WFCORE-4860

by Ilia Vassilev (Jira)

Ilia Vassilev created WFLY-13389: ------------------------------------ Summary: (7.3.z) WFLY-13273 - Create tests for WFCORE-4860 Key: WFLY-13389 URL: https://issues.redhat.com/browse/WFLY-13389 Project: WildFly Issue Type: Task Components: Logging Reporter: Ilia Vassilev Assignee: James Perkins Fix For: 20.0.0.Beta1 WFCORE-4860 makes some change in behavior for how the log context selector works. This is to help with some performance issues with Java 9+. The tests need to live in WildFly as we need multiple deployments and EAR's which the core test suite cannot handle. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13389) (7.3.z) WFLY-13273 - Create tests for WFCORE-4860

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-13389?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFLY-13389: ------------------------------------ Assignee: Ilia Vassilev (was: James Perkins) > (7.3.z) WFLY-13273 - Create tests for WFCORE-4860 > ------------------------------------------------- > > Key: WFLY-13389 > URL: https://issues.redhat.com/browse/WFLY-13389 > Project: WildFly > Issue Type: Task > Components: Logging > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > WFCORE-4860 makes some change in behavior for how the log context selector works. This is to help with some performance issues with Java 9+. The tests need to live in WildFly as we need multiple deployments and EAR's which the core test suite cannot handle. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4933) (7.3.z) WFCORE-4860 - Performance degradation with the LogContextSelector on Java 11

by Ilia Vassilev (Jira)

Ilia Vassilev created WFCORE-4933: ------------------------------------- Summary: (7.3.z) WFCORE-4860 - Performance degradation with the LogContextSelector on Java 11 Key: WFCORE-4933 URL: https://issues.redhat.com/browse/WFCORE-4933 Project: WildFly Core Issue Type: Enhancement Components: Logging Reporter: Ilia Vassilev Assignee: James Perkins Fix For: 12.0.0.Beta1 As described in LOGMGR-263 there is a performance impact on Java 11 when using the {{ClassLoaderLogContextSelector}}. In WildFly for users that do not use per-deployment logging we could get around this by not using that log context selector. This would not fix the performance impact for users using Java 11 and per-deployment logging however. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4933) (7.3.z) WFCORE-4860 - Performance degradation with the LogContextSelector on Java 11

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-4933?page=com.atlassian.jira.plug... ] Ilia Vassilev reassigned WFCORE-4933: ------------------------------------- Assignee: Ilia Vassilev (was: James Perkins) > (7.3.z) WFCORE-4860 - Performance degradation with the LogContextSelector on Java 11 > ------------------------------------------------------------------------------------- > > Key: WFCORE-4933 > URL: https://issues.redhat.com/browse/WFCORE-4933 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Fix For: 12.0.0.Beta1 > > > As described in LOGMGR-263 there is a performance impact on Java 11 when using the {{ClassLoaderLogContextSelector}}. In WildFly for users that do not use per-deployment logging we could get around this by not using that log context selector. This would not fix the performance impact for users using Java 11 and per-deployment logging however. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13144) Resource Adapter can't be deleted after restarting server

by Dmitrii Pogorelov (Jira)

[ https://issues.redhat.com/browse/WFLY-13144?page=com.atlassian.jira.plugi... ] Dmitrii Pogorelov commented on WFLY-13144: ------------------------------------------ thx [~shawkins] for your comment, I'll try your idea once I have free time. I'll write here about any results. > Resource Adapter can't be deleted after restarting server > --------------------------------------------------------- > > Key: WFLY-13144 > URL: https://issues.redhat.com/browse/WFLY-13144 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 14.0.1.Final, 11.0.0.Final, 17.0.1.Final > Reporter: Dmitrii Pogorelov > Assignee: Ivo Studensky > Priority: Critical > Attachments: jca-demo-1.0.rar, jcademo-source-code.rar > > > The issue is related to the WFLY-6774 issue. I'm working with Teiid and should create/delete resource adapters many times, especially resource adapters based on the same archive. The WFLY-6774 fix works well before the restarting server allowing me to create/delete resource adapters without restarting the server. Once I restart the server and try to remove a resource adapter based on an archive I'll get the following error: > {code:noformat} > [standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=jcaDemo_VDB_ID_1:remove{allow-resource-service-restart=true} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.resourceadapters.ra.jcaDemo_VDB_ID_1 was depended upon by service jboss.deployment.unit.\"jca-demo-1.0.rar\".INSTALL", > "rolled-back" => true > } > {code} > After showing the error server will rollback the "remove" command deploying the jca-demo-1.0.rar archive again and re-creating the jcaDemo_VDB_ID_1 resource adapter. As a result I can't remove the resource adapter via cli commands, it can be removed only manually (removing the resource adapter in standalone.xml). The bug can be reproduced (at least versions which I checked) on WildFly 11.0.0.Final, WildFly 14.0.1.Final and WildFly 17.0.1.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13144) Resource Adapter can't be deleted after restarting server

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13144?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on WFLY-13144: --------------------------------------- In the teiid admin code when we remove a source we remove both the connection-definitions and the resource-adapter, have you tried this sequence but with removing the connection-definitions before removing the resource-adapter? > Resource Adapter can't be deleted after restarting server > --------------------------------------------------------- > > Key: WFLY-13144 > URL: https://issues.redhat.com/browse/WFLY-13144 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 14.0.1.Final, 11.0.0.Final, 17.0.1.Final > Reporter: Dmitrii Pogorelov > Assignee: Ivo Studensky > Priority: Critical > Attachments: jca-demo-1.0.rar, jcademo-source-code.rar > > > The issue is related to the WFLY-6774 issue. I'm working with Teiid and should create/delete resource adapters many times, especially resource adapters based on the same archive. The WFLY-6774 fix works well before the restarting server allowing me to create/delete resource adapters without restarting the server. Once I restart the server and try to remove a resource adapter based on an archive I'll get the following error: > {code:noformat} > [standalone@localhost:9990 /] /subsystem=resource-adapters/resource-adapter=jcaDemo_VDB_ID_1:remove{allow-resource-service-restart=true} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0171: Removing services has lead to unsatisfied dependencies: > Service jboss.resourceadapters.ra.jcaDemo_VDB_ID_1 was depended upon by service jboss.deployment.unit.\"jca-demo-1.0.rar\".INSTALL", > "rolled-back" => true > } > {code} > After showing the error server will rollback the "remove" command deploying the jca-demo-1.0.rar archive again and re-creating the jcaDemo_VDB_ID_1 resource adapter. As a result I can't remove the resource adapter via cli commands, it can be removed only manually (removing the resource adapter in standalone.xml). The bug can be reproduced (at least versions which I checked) on WildFly 11.0.0.Final, WildFly 14.0.1.Final and WildFly 17.0.1.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4932) Reading of identity from security domain causes NPE

by Diana Vilkolakova (Jira)

Diana Vilkolakova created WFCORE-4932: ----------------------------------------- Summary: Reading of identity from security domain causes NPE Key: WFCORE-4932 URL: https://issues.redhat.com/browse/WFCORE-4932 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Diana Vilkolakova Assignee: Diana Vilkolakova Security domain in the elytron subsystem has operation `read-identity`. Description of this opearation is the following: `Reads an identity from a security domain if it exists.` However, this operation causes NPE when called on the security domain backed by the filesystem realm (see steps to reproduce) or jdbc realm. This issue is to address that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-263) Logger Lookup is much slower as with JDK 8

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/LOGMGR-263?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated LOGMGR-263: --------------------------------- Labels: downstream_dependency (was: ) > Logger Lookup is much slower as with JDK 8 > ------------------------------------------ > > Key: LOGMGR-263 > URL: https://issues.redhat.com/browse/LOGMGR-263 > Project: JBoss Log Manager > Issue Type: Bug > Environment: WildFly 17, OpenJDK 11 > Reporter: Andreas Liebscher > Assignee: James Perkins > Priority: Critical > Labels: downstream_dependency > Fix For: 2.1.15.Final, 2.2.0.Final, 3.0.0.Final > > Attachments: ClassInEar.java, LogContextCacher.java, getlogger-stack.txt, grafik1570016303722 (1).png, grafik1570016303722.png, grafik1570016791285.png, logger-demo.war, responsetimes.png > > > During upgrading a Java EE application from WildFly 13 with JDK 8 to WildFly 17 with JDK 11 we had a serious performance issue. We identified the usage of the logging framework SLF4J with the pattern `Logger log = LoggerFactory.getLogger(XXX.class)` was the reason when a lot of calls to `getLogger` occur in parallel. As workaround we added `static` to some code hotspots to get back the performance we were used to. Also WildFly 13 with JDK 8 got a performance improvement with the added `static` keyword. > Please check the VisualVM output as prove of JDKSpecific got slower: -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4930) Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFCORE-4930?page=com.atlassian.jira.plug... ] Ilia Vassilev updated WFCORE-4930: ---------------------------------- Labels: downstream_dependency (was: ) > Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final > ---------------------------------------------------------- > > Key: WFCORE-4930 > URL: https://issues.redhat.com/browse/WFCORE-4930 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > > Upgrade {{org.jboss.logmanager:jboss-logmanager}} to 2.1.15.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13388) Undertow subsystem use org.wildfly.security.jacc-policy capability without registering a requirement for it

by Tomasz Adamski (Jira)

Tomasz Adamski created WFLY-13388: ------------------------------------- Summary: Undertow subsystem use org.wildfly.security.jacc-policy capability without registering a requirement for it Key: WFLY-13388 URL: https://issues.redhat.com/browse/WFLY-13388 Project: WildFly Issue Type: Bug Reporter: Tomasz Adamski Assignee: Tomasz Adamski Undertow has 'enable-jacc' attribute which, if true, result in the code doing a service dep using the org.wildfly.security.jacc-policy capability. But there's no registration of a requirement for that capability, so if it were removed (which requires reload) the inconsistent model would not be detected and a subsequent reboot/restart would fail. This can't be fixed until WFCORE-3354 is, because right now that capability isn't registered either! Fixing this isn't as simple as recording this as a fixed requirement of the relevant ejb/undertow capability, as it's only a requirement if the attribute value is 'true'. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020