May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1559) "default" as default name for long-running-threads and short-running-threads leads to thread groups with the same name default-threads

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1559?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-1559: ----------------------------------- Assignee: (was: Jason Greene) > "default" as default name for long-running-threads and short-running-threads leads to thread groups with the same name default-threads > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1559 > URL: https://issues.jboss.org/browse/WFCORE-1559 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 2.1.0.Final > Reporter: Martin Simka > Priority: Minor > > /subsystem=jca/workmanager=default/short-running-threads=default > /subsystem=jca/workmanager=default/long-running-threads=default > Thread group with name {{default-threads}} is created for both of these addresses. It's because thread group name is created from last element of resource's address + string {{-threads}}. > [ThreadPoolManagementUtils.java#L166|https://github.com/wildfly/wildfly-co...] > {code:java} > params.name = pathAddress.getLastElement().getValue(); > {code} > [ThreadFactoryResolver.java#L149|https://github.com/wildfly/wildfly-core/b...] > {code:java} > protected String getThreadGroupName(String threadPoolName) { > return threadPoolName + "-threads"; > } > {code} > Thread groups for different resources shouldn't have the same name. Also such a general name {{default-threads}} could be confusing when debugging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6624) Frequent intermittent failures in coarse/fine web session passivation tests

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-6624: ---------------------------------- Summary: Frequent intermittent failures in coarse/fine web session passivation tests Key: WFLY-6624 URL: https://issues.jboss.org/browse/WFLY-6624 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 10.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6621) wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6621?page=com.atlassian.jira.plugin.... ] Vsevolod Golovanov commented on WFLY-6621: ------------------------------------------ bq. because one clearly shows where the problem for el-api comes from. Which it now obviously doesn't - it doesn't show who's managing the wrong versions. > wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api > -------------------------------------------------------- > > Key: WFLY-6621 > URL: https://issues.jboss.org/browse/WFLY-6621 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Vsevolod Golovanov > Assignee: Tomaz Cerar > Attachments: pom_el.png, pom_jsf.png > > > Manages el-api to 1.0.4.Final, should be 1.0.5.Final: !pom_el.png|thumbnail! > Manages jsf-api to 2.2.11, should be 2.2.12: !pom_jsf.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6622) Upgrade Resteasy to release 3.0.17.Final

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/WFLY-6622?page=com.atlassian.jira.plugin.... ] Weinan Li updated WFLY-6622: ---------------------------- Fix Version/s: 10.1.0.Final (was: 11.0.0.CR1) Affects Version/s: 10.0.0.Final > Upgrade Resteasy to release 3.0.17.Final > ---------------------------------------- > > Key: WFLY-6622 > URL: https://issues.jboss.org/browse/WFLY-6622 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Affects Versions: 10.0.0.Final > Reporter: Weinan Li > Assignee: Weinan Li > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6623) Upgrade Resteasy to release 3.0.17.Final

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/WFLY-6623?page=com.atlassian.jira.plugin.... ] Weinan Li closed WFLY-6623. --------------------------- Resolution: Duplicate Issue > Upgrade Resteasy to release 3.0.17.Final > ---------------------------------------- > > Key: WFLY-6623 > URL: https://issues.jboss.org/browse/WFLY-6623 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Weinan Li > Assignee: Weinan Li > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6623) Upgrade Resteasy to release 3.0.17.Final

by Weinan Li (JIRA)

Weinan Li created WFLY-6623: ------------------------------- Summary: Upgrade Resteasy to release 3.0.17.Final Key: WFLY-6623 URL: https://issues.jboss.org/browse/WFLY-6623 Project: WildFly Issue Type: Component Upgrade Reporter: Weinan Li Assignee: Weinan Li Fix For: 10.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6622) Upgrade Resteasy to release 3.0.17.Final

by Weinan Li (JIRA)

Weinan Li created WFLY-6622: ------------------------------- Summary: Upgrade Resteasy to release 3.0.17.Final Key: WFLY-6622 URL: https://issues.jboss.org/browse/WFLY-6622 Project: WildFly Issue Type: Component Upgrade Components: REST Reporter: Weinan Li Assignee: Weinan Li Fix For: 11.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6621) wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/WFLY-6621?page=com.atlassian.jira.plugin.... ] Vsevolod Golovanov commented on WFLY-6621: ------------------------------------------ [~ctomc], no, I included the screenshots just because one clearly shows where the problem for el-api comes from. I was wrong that it's just wildfly-spec-api. It's BOM + spec-api: {code} <dependencyManagement> <dependencies> <dependency> <groupId>org.wildfly.bom</groupId> <artifactId>wildfly-javaee7-with-tools</artifactId> <version>10.0.1.Final</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.wildfly</groupId> <artifactId>wildfly-spec-api</artifactId> <version>10.0.0.Final</version> <type>pom</type> <scope>provided</scope> </dependency> </dependencies> {code} mvn dependency:tree: {code} [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building WildFly Quickstarts: Kitchensink 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ reproducer --- [WARNING] The POM for commons-collections:commons-collections:jar:3.2.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [INFO] my.testcase:reproducer:war:1.0-SNAPSHOT [INFO] \- org.wildfly:wildfly-spec-api:pom:10.0.0.Final:provided [INFO] +- org.glassfish:javax.json:jar:1.0.3:provided [INFO] +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.batch:jboss-batch-api_1.0_spec:jar:1.0.0.Final:provided [INFO] | \- javax.inject:javax.inject:jar:1:provided [INFO] +- org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.el:jboss-el-api_3.0_spec:jar:1.0.4.Final:provided [INFO] +- org.jboss.spec.javax.enterprise.concurrent:jboss-concurrency-api_1.0_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.faces:jboss-jsf-api_2.2_spec:jar:2.2.11:provided [INFO] +- org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.resource:jboss-connector-api_1.7_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.security.auth.message:jboss-jaspi-api_1.1_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.security.jacc:jboss-jacc-api_1.5_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.servlet.jsp:jboss-jsp-api_2.3_spec:jar:1.0.1.Final:provided [INFO] +- org.jboss.spec.javax.servlet.jstl:jboss-jstl-api_1.2_spec:jar:1.1.2.Final:provided [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final:provided [INFO] +- org.jboss.spec.javax.websocket:jboss-websocket-api_1.1_spec:jar:1.1.0.Final:provided [INFO] +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:provided [INFO] +- org.jboss.spec.javax.xml.rpc:jboss-jaxrpc-api_1.1_spec:jar:1.0.1.Final:provided [INFO] +- org.jboss.spec.javax.xml.soap:jboss-saaj-api_1.3_spec:jar:1.0.3.Final:provided [INFO] +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:provided [INFO] +- org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final:provided [INFO] +- javax.enterprise:cdi-api:jar:1.2:provided [INFO] +- com.sun.mail:javax.mail:jar:1.5.3:provided [INFO] | \- javax.activation:activation:jar:1.1.1:provided [INFO] +- org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final:provided [INFO] +- javax.validation:validation-api:jar:1.1.0.Final:provided [INFO] +- org.jboss.spec.javax.management.j2ee:jboss-j2eemgmt-api_1.1_spec:jar:1.0.1.Final:provided [INFO] \- org.wildfly.checkstyle:wildfly-checkstyle-config:jar:1.0.4.Final:provided [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2.174 s [INFO] Finished at: 2016-05-18T17:37:00+03:00 [INFO] Final Memory: 13M/367M [INFO] ------------------------------------------------------------------------ {code} > wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api > -------------------------------------------------------- > > Key: WFLY-6621 > URL: https://issues.jboss.org/browse/WFLY-6621 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Vsevolod Golovanov > Assignee: Tomaz Cerar > Attachments: pom_el.png, pom_jsf.png > > > Manages el-api to 1.0.4.Final, should be 1.0.5.Final: !pom_el.png|thumbnail! > Manages jsf-api to 2.2.11, should be 2.2.12: !pom_jsf.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1559) "default" as default name for long-running-threads and short-running-threads leads to thread groups with the same name default-threads

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1559?page=com.atlassian.jira.plugi... ] Martin Simka moved JBEAP-4611 to WFCORE-1559: --------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1559 (was: JBEAP-4611) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server (was: Server) Target Release: (was: 7.backlog.GA) Affects Version/s: 2.1.0.Final (was: 7.0.0.GA) > "default" as default name for long-running-threads and short-running-threads leads to thread groups with the same name default-threads > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1559 > URL: https://issues.jboss.org/browse/WFCORE-1559 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Affects Versions: 2.1.0.Final > Reporter: Martin Simka > Assignee: Jason Greene > Priority: Minor > > /subsystem=jca/workmanager=default/short-running-threads=default > /subsystem=jca/workmanager=default/long-running-threads=default > Thread group with name {{default-threads}} is created for both of these addresses. It's because thread group name is created from last element of resource's address + string {{-threads}}. > [ThreadPoolManagementUtils.java#L166|https://github.com/wildfly/wildfly-co...] > {code:java} > params.name = pathAddress.getLastElement().getValue(); > {code} > [ThreadFactoryResolver.java#L149|https://github.com/wildfly/wildfly-core/b...] > {code:java} > protected String getThreadGroupName(String threadPoolName) { > return threadPoolName + "-threads"; > } > {code} > Thread groups for different resources shouldn't have the same name. Also such a general name {{default-threads}} could be confusing when debugging. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6621) wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6621?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-6621. ----------------------------- Assignee: Tomaz Cerar (was: Jason Greene) Resolution: Rejected Closing as it looks like gui tool used in reporting is wrongly resolving dependencies. > wildfly-spec-api:10.0.0.Final mismanages el-api, jsf-api > -------------------------------------------------------- > > Key: WFLY-6621 > URL: https://issues.jboss.org/browse/WFLY-6621 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Vsevolod Golovanov > Assignee: Tomaz Cerar > Attachments: pom_el.png, pom_jsf.png > > > Manages el-api to 1.0.4.Final, should be 1.0.5.Final: !pom_el.png|thumbnail! > Manages jsf-api to 2.2.11, should be 2.2.12: !pom_jsf.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 2016