May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3582) Redesign mod_cluster xml subsystem parsers

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3582?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3582: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Redesign mod_cluster xml subsystem parsers > ------------------------------------------ > > Key: WFLY-3582 > URL: https://issues.jboss.org/browse/WFLY-3582 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2 > > > As per https://github.com/wildfly/wildfly/pull/6449 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3573) Adding incorrect JGroups protocol should provide better error description than CNFE

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3573?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3573: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Adding incorrect JGroups protocol should provide better error description than CNFE > ----------------------------------------------------------------------------------- > > Key: WFLY-3573 > URL: https://issues.jboss.org/browse/WFLY-3573 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: JBoss AS7 7.2.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 9.0.0.CR2 > > > As reported by the community user: > {noformat} > [standalone@localhost:9990 / #] list-batch > #1 /subsystem=jgroups/stack=test:add() > #2 /subsystem=jgroups/stack=test/transport=TRANSPORT:add(type="udp",socket-binding=jgroups-udp) > #3 /subsystem=jgroups/stack=test:add-protocol(type=FD_SOCK,socket-binding=jgroups-udp-fd) > [standalone@localhost:9990 / #] run-batch > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0158: Operation handler failed: java.lang.ClassNotFoundException: org.jgroups.protocols.udp from [Module \"org.jboss.as.clustering.jgroups:main\" from local module loader @4d9f6ce5 (finder: local module finder @1da65633 (roots: /home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules,/home/rhusar/as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base))]"}} > [standalone@localhost:9990 / #] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3608) Expose configuring allowed file extensions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3608?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3608: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Expose configuring allowed file extensions > ------------------------------------------ > > Key: WFLY-3608 > URL: https://issues.jboss.org/browse/WFLY-3608 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: CentOs 5.5 & Ubuntu 10.04/12.04, Wildfly 8.1.0 Final, java version 1.7.0_60 > Reporter: Thomas Brenna > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR2 > > > It should be possible to modify allowed extensions without adding web.xml entry as we have it now. > It should be an configuration option of servlet-container element. in undertow subsystem. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3615) Clustering TS: mod_cluster integration test

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3615?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3615: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Clustering TS: mod_cluster integration test > ------------------------------------------- > > Key: WFLY-3615 > URL: https://issues.jboss.org/browse/WFLY-3615 > Project: WildFly > Issue Type: Task > Affects Versions: JBoss AS7 7.2.0.Final, 8.0.0.Final, 8.1.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3612) Implement missing transformers for new bean validation subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3612?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3612: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Implement missing transformers for new bean validation subsystem > ---------------------------------------------------------------- > > Key: WFLY-3612 > URL: https://issues.jboss.org/browse/WFLY-3612 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, EE > Reporter: Brian Stansberry > Assignee: Eduardo Martins > Fix For: 9.0.0.CR2 > > > The initial work on WFLY-3551 will be merged without needed transformers, because the transformer support we have won't allow the needed transformation. This JIRA is a reminder to add it once the required work in WFLY-3563 is done. > From my comment on the PR for the WFLY-3551 work: > There needs to be a discard of this resource if a legacy slave is involved. The presence of the resource means BV is wanted, and by default the legacy slave will have BV, so if this resource exists, the legacy slave is compatible. The resource just needs to be discarded so the legacy slave doesn't fail when it sees resources/ops for this subsystem it can't understand. > If this subsystem is omitted in a config with ee, the legacy slave will be out of sync with newer ones running the same profile, because the old ones will have BV and the new ones won't. But > 1) it's a corner case > 2) it may not matter anyway in terms of behavior of an app > 3) the transformer logic we have doesn't allow us to do anything about it anyway. > Re: that last part, when doing this work double check on skipping that, in case the WFLY-3563 work makes it real easy. Unlikely though. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3663) WildFly should manage JGroups and Infinispan thread pools by default

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3663?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3663: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > WildFly should manage JGroups and Infinispan thread pools by default > -------------------------------------------------------------------- > > Key: WFLY-3663 > URL: https://issues.jboss.org/browse/WFLY-3663 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR2 > > > In our default configuration, both JGroups and Infinispan manage their own thread pools. Unfortunately, both projects do not handle thread pool lifecycle so well. Both projects use ExecutorService.shutdownNow() to end their thread pool lifecycles. This means that a channel or cache can stop, but still leave active threads running (albeit interrupted). We should have services that manage the lifecycle of our thread pools which ensure that all threads have terminated during Service.stop(). > This causes occasional OOMs in the Windows CI testsuite runs, due to too many threads lying around. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3639) default-web-module doesn't work for non default host

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3639?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3639: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > default-web-module doesn't work for non default host > ---------------------------------------------------- > > Key: WFLY-3639 > URL: https://issues.jboss.org/browse/WFLY-3639 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 9.0.0.CR2 > > > If you use config like this: > {code:xml} > <host name="default-host" default-web-module="myapp1.war" alias="webapp.domain1.com"/> > <host name="other-host" default-web-module="myapp2.war" alias="test.domain2.net"/> > {code} > and have apps myapp1.war & myapp2.war deployed myappwar2.war won't be bind to other-host. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3681) General Schema Sync with EAP

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3681?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3681: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > General Schema Sync with EAP > ---------------------------- > > Key: WFLY-3681 > URL: https://issues.jboss.org/browse/WFLY-3681 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 9.0.0.CR2 > > > This may actually be more about pushing some changes to EAP, new schemas are being tracked by individual issues but for the remaining schemas where cosmetic changes have been made or corrections to default values and min/max occurs we need to sync with EAP. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3679) Port jboss-as-infinispan_1_5.xsd schema from EAP to WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3679?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3679: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Port jboss-as-infinispan_1_5.xsd schema from EAP to WildFly > ----------------------------------------------------------- > > Key: WFLY-3679 > URL: https://issues.jboss.org/browse/WFLY-3679 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Radoslav Husar > Priority: Blocker > Fix For: 9.0.0.CR2 > > > In addition to this the remaining infinispan schemas differ due to changes in the default values - these should be synchronized accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3678) Port jboss-as-ee_1_2.xsd schema from EAP to WildFly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3678?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3678: ------------------------------- Fix Version/s: 9.0.0.CR2 (was: 9.0.0.CR1) > Port jboss-as-ee_1_2.xsd schema from EAP to WildFly > --------------------------------------------------- > > Key: WFLY-3678 > URL: https://issues.jboss.org/browse/WFLY-3678 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Darran Lofthouse > Assignee: David Lloyd > Priority: Blocker > Fix For: 9.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 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 2015