May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8764) The WildFly pom.xml is overriding the version of WildFly discovery client

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-8764?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-8764: ----------------------------------- This raises an interesting problem: when core and another project (which is consumed by wildfly but not by core) specify differing versions of a dependency, there's no guarantee that the version specified in core will be used. > The WildFly pom.xml is overriding the version of WildFly discovery client > ------------------------------------------------------------------------- > > Key: WFLY-8764 > URL: https://issues.jboss.org/browse/WFLY-8764 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > This was introduce under the following commit to address transitive dependency issues: - > commit b49586d5c90e673aa1abceef3c047257da6cb19e > Author: Tomaz Cerar <tomaz.cerar(a)gmail.com> > Date: Mon Apr 24 17:13:16 2017 +0200 > JBEAP-10175 JBEAP-10174 Unmanaged transitive dependencies in EJB client BOM dependency tree > However the version override means a version upgrade in core does not get applied to EAP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2802) Upgrade remoting-jmx from 3.0.0.Beta3 to 3.0.0.Beta4

by James Perkins (JIRA)

James Perkins created WFCORE-2802: ------------------------------------- Summary: Upgrade remoting-jmx from 3.0.0.Beta3 to 3.0.0.Beta4 Key: WFCORE-2802 URL: https://issues.jboss.org/browse/WFCORE-2802 Project: WildFly Core Issue Type: Component Upgrade Components: JMX Reporter: James Perkins Assignee: Kabir Khan The {{org.jboss.remotingjmx:remote-jmx}} dependency should be upgraded from 3.0.0.Beta3 to 3.0.0.Beta4 to incorporate some minor changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2802) Upgrade remoting-jmx from 3.0.0.Beta3 to 3.0.0.Beta4

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2802?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFCORE-2802: ------------------------------------- Assignee: Darran Lofthouse (was: Kabir Khan) > Upgrade remoting-jmx from 3.0.0.Beta3 to 3.0.0.Beta4 > ---------------------------------------------------- > > Key: WFCORE-2802 > URL: https://issues.jboss.org/browse/WFCORE-2802 > Project: WildFly Core > Issue Type: Component Upgrade > Components: JMX > Reporter: James Perkins > Assignee: Darran Lofthouse > > The {{org.jboss.remotingjmx:remote-jmx}} dependency should be upgraded from 3.0.0.Beta3 to 3.0.0.Beta4 to incorporate some minor changes. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8764) The WildFly pom.xml is overriding the version of WildFly Client Config

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8764: --------------------------------- Summary: The WildFly pom.xml is overriding the version of WildFly Client Config Key: WFLY-8764 URL: https://issues.jboss.org/browse/WFLY-8764 Project: WildFly Issue Type: Bug Components: Build System Reporter: Tomaz Cerar Assignee: Tomaz Cerar This was introduce under the following commit to address transitive dependency issues: - commit b49586d5c90e673aa1abceef3c047257da6cb19e Author: Tomaz Cerar <tomaz.cerar(a)gmail.com> Date: Mon Apr 24 17:13:16 2017 +0200 JBEAP-10175 JBEAP-10174 Unmanaged transitive dependencies in EJB client BOM dependency tree However the version override means a version upgrade in core does not get applied to EAP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8764) The WildFly pom.xml is overriding the version of WildFly discovery client

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8764?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-8764: ------------------------------ Summary: The WildFly pom.xml is overriding the version of WildFly discovery client (was: The WildFly pom.xml is overriding the version of WildFly Client Config) > The WildFly pom.xml is overriding the version of WildFly discovery client > ------------------------------------------------------------------------- > > Key: WFLY-8764 > URL: https://issues.jboss.org/browse/WFLY-8764 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > This was introduce under the following commit to address transitive dependency issues: - > commit b49586d5c90e673aa1abceef3c047257da6cb19e > Author: Tomaz Cerar <tomaz.cerar(a)gmail.com> > Date: Mon Apr 24 17:13:16 2017 +0200 > JBEAP-10175 JBEAP-10174 Unmanaged transitive dependencies in EJB client BOM dependency tree > However the version override means a version upgrade in core does not get applied to EAP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2801) Upgrade jansi to 1.16

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFCORE-2801: ----------------------------------- Summary: Upgrade jansi to 1.16 Key: WFCORE-2801 URL: https://issues.jboss.org/browse/WFCORE-2801 Project: WildFly Core Issue Type: Component Upgrade Components: CLI Reporter: Tomaz Cerar Assignee: Tomaz Cerar Asked for it by prod guys in JBEAP-9365 as will help with prod process. Testing shows that upgrade of jansi doesn't cause any regression in aesh. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8762) WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8762?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-8762: ----------------------------------- after the proposed PR this is what happens when you try to remove worker {noformat} [standalone@localhost:9990 /] /subsystem=io/worker=default:remove { "outcome" => "failed", "failure-description" => "WFLYCTL0367: Cannot remove capability 'org.wildfly.io.worker.default' as it is required by other capabilities: capability 'org.wildfly.undertow.listener.https' requires it for attribute 'worker' at address '/subsystem=undertow/server=default-server/https-listener=https' capability 'org.wildfly.undertow.listener.default' requires it for attribute 'worker' at address '/subsystem=undertow/server=default-server/http-listener=default' capability 'org.wildfly.remoting.endpoint' requires it for attribute 'worker' at address '/subsystem=remoting/configuration=endpoint'", "rolled-back" => true } {noformat} > WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references > --------------------------------------------------------------------------------------- > > Key: WFLY-8762 > URL: https://issues.jboss.org/browse/WFLY-8762 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > > This makes it hard to remove or rename the 'default' worker (e.g. as part of doing performance tuning), because the requirement for that worker isn't shown in standalone.xml. Since there's no capability ref failure, boot proceeds to RUNTIME, ServletContainerService can't start but a whole lot of others can't start as well. So there's a lot of noise that obscures the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2800) contrib systemd script uses systemd enable|start wildfly.service

by Filippe Spolti (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2800?page=com.atlassian.jira.plugi... ] Filippe Spolti closed WFCORE-2800. ---------------------------------- Resolution: Duplicate > contrib systemd script uses systemd enable|start wildfly.service > ---------------------------------------------------------------- > > Key: WFCORE-2800 > URL: https://issues.jboss.org/browse/WFCORE-2800 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Filippe Spolti > Assignee: Filippe Spolti > Priority: Trivial > > The command used in the $WFLY_HOME/docs/contrib/scripts/systemd/README to enable and start the wildfly service is not correct. > The correct one is systemctl. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8763) WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8763: --------------------------------- Summary: WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references Key: WFLY-8763 URL: https://issues.jboss.org/browse/WFLY-8763 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Tomaz Cerar Assignee: Tomaz Cerar This makes it hard to remove or rename the 'default' worker (e.g. as part of doing performance tuning), because the requirement for that worker isn't shown in standalone.xml. Since there's no capability ref failure, boot proceeds to RUNTIME, ServletContainerService can't start but a whole lot of others can't start as well. So there's a lot of noise that obscures the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2800) contrib systemd script uses systemd enable|start wildfly.service

by Filippe Spolti (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2800?page=com.atlassian.jira.plugi... ] Filippe Spolti updated WFCORE-2800: ----------------------------------- Priority: Trivial (was: Major) > contrib systemd script uses systemd enable|start wildfly.service > ---------------------------------------------------------------- > > Key: WFCORE-2800 > URL: https://issues.jboss.org/browse/WFCORE-2800 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Filippe Spolti > Assignee: Filippe Spolti > Priority: Trivial > > The command used in the $WFLY_HOME/docs/contrib/scripts/systemd/README to enable and start the wildfly service is not correct. > The correct one is systemctl. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017