January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9678) Expand clustering test cases to 3-node cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9678?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9678: --------------------------------- Fix Version/s: (was: 12.0.0.Alpha1) > Expand clustering test cases to 3-node cluster > ---------------------------------------------- > > Key: WFLY-9678 > URL: https://issues.jboss.org/browse/WFLY-9678 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The core of the problem is that since all cases run against 2-node cluster a remote fetch is never tested given that numOwners defaults to 2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9678) Expand clustering test cases to 3-node cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9678?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9678: --------------------------------- Description: The core of the problem is that since all cases run against 2-node cluster a remote get(..) is never being tested given that numOwners defaults to 2. (was: The core of the problem is that since all cases run against 2-node cluster a remote fetch is never tested given that numOwners defaults to 2.) > Expand clustering test cases to 3-node cluster > ---------------------------------------------- > > Key: WFLY-9678 > URL: https://issues.jboss.org/browse/WFLY-9678 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The core of the problem is that since all cases run against 2-node cluster a remote get(..) is never being tested given that numOwners defaults to 2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3562) Deployment disable-all doesn't correct function at domain

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3562?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3562: ---------------------------------------------- [~vmarek], are you 100% sure of your steps? I did: [domain@localhost:9990 /] deployment deploy-file ../../NetBeansProjects/TestApp/dist/TestApp.war --server-groups=main-server-group,other-server-group --name=Test2 [domain@localhost:9990 /] deployment deploy-file ../../NetBeansProjects/TestApp/dist/TestApp.war --server-groups=main-server-group,other-server-group [domain@localhost:9990 /] deployment disable Test2 --server-groups=other-server-group [domain@localhost:9990 /] deployment disable TestApp.war --server-groups=main-server-group [domain@localhost:9990 /] deployment disable-all --all-relevant-server-groups And it worked as expected. Am I missing something? Thank-you. > Deployment disable-all doesn't correct function at domain > --------------------------------------------------------- > > Key: WFCORE-3562 > URL: https://issues.jboss.org/browse/WFCORE-3562 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Vratislav Marek > Assignee: Jean-Francois Denise > > Domain > {noformat} > [domain@localhost:9990 /] deployment disable-all --all-relevant-server-groups > org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment. > [domain@localhost:9990 /] > {noformat} > {noformat} > [domain@localhost:9990 /] undeploy * --keep-content --all-relevant-server-groups > org.jboss.as.cli.operation.OperationFormatException: None of the server groups is specified or references specified deployment. > [domain@localhost:9990 /] > {noformat} > {noformat} > [domain@localhost:9990 /] deployment disable-all --server-groups=main-server-group > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0216: Management resource '[ > (\"server-group\" => \"main-server-group\"), > (\"deployment\" => \"cli-test-app2-deploy-all.war\") > ]' not found"}} > [domain@localhost:9990 /] > {noformat} > {noformat} > [domain@localhost:9990 /] undeploy * --keep-content --server-groups=main-server-group > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-4" => "WFLYCTL0216: Management resource '[ > (\"server-group\" => \"main-server-group\"), > (\"deployment\" => \"cli-test-app2-deploy-all.war\") > ]' not found"}} > [domain@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9745) Missing clustering API documentation in wildfly-capabilities

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9745: ------------------------------------ Summary: Missing clustering API documentation in wildfly-capabilities Key: WFLY-9745 URL: https://issues.jboss.org/browse/WFLY-9745 Project: WildFly Issue Type: Task Components: Clustering, Documentation Reporter: Radoslav Husar Assignee: Paul Ferraro -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9745) Missing clustering API documentation in wildfly-capabilities

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9745?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9745: --------------------------------- Description: e.g. https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... linked from wildscribe > Missing clustering API documentation in wildfly-capabilities > ------------------------------------------------------------- > > Key: WFLY-9745 > URL: https://issues.jboss.org/browse/WFLY-9745 > Project: WildFly > Issue Type: Task > Components: Clustering, Documentation > Reporter: Radoslav Husar > Assignee: Paul Ferraro > > e.g. https://github.com/wildfly/wildfly-capabilities/tree/master/org/wildfly/c... linked from wildscribe -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9744) Improve Infinispan subsystem model descriptions

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9744: ------------------------------------ Summary: Improve Infinispan subsystem model descriptions Key: WFLY-9744 URL: https://issues.jboss.org/browse/WFLY-9744 Project: WildFly Issue Type: Task Components: Clustering Reporter: Radoslav Husar Assignee: Paul Ferraro In order not to duplicate documentation in docs/ and wildscribe, we can link from documentation to wildscribe. * the descriptions should avoid using domain model terminology (e.g. attributes, child) * should describe behavior * take out the redundant verb (unless appropriate, e.g. in operation desc.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9743) wildscribe: Consider using strikethrough for deprecated model attribute/operation/children names

by Radoslav Husar (JIRA)

Radoslav Husar created WFLY-9743: ------------------------------------ Summary: wildscribe: Consider using strikethrough for deprecated model attribute/operation/children names Key: WFLY-9743 URL: https://issues.jboss.org/browse/WFLY-9743 Project: WildFly Issue Type: Component Upgrade Components: Documentation Reporter: Radoslav Husar -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3564) Bad CLI complementation server groups

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3564?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-3564: ---------------------------------------------- [~vmarek], FYI, I found an issue related to completion in domain mode: https://issues.jboss.org/browse/WFCORE-3567 Just in case you ran into it yourself. > Bad CLI complementation server groups > ------------------------------------- > > Key: WFCORE-3564 > URL: https://issues.jboss.org/browse/WFCORE-3564 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Vratislav Marek > Assignee: Jean-Francois Denise > > *Cli complementation insert the whole word without delete writed letters* > * --server-groups={color:#d04437}m{color}main-server-group > * --server-groups={color:#d04437}o{color}other-server-group > * --server-groups={color:#d04437}othe{color}other-server-group > {noformat} > [domain@localhost:9990 /] deployment disable * --server-groups= > main-server-group other-server-group > [domain@localhost:9990 /] deployment disable * --server-groups=mmain-server-group > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0216: Management resource '[(\"server-group\" => \"mmain-server-group\")]' not found"}} > [domain@localhost:9990 /] deployment disable * --server-groups=oother-server-group > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0216: Management resource '[(\"server-group\" => \"oother-server-group\")]' not found"}} > [domain@localhost:9990 /] > [domain@localhost:9990 /] deployment disable * --server-groups=otheother-server-group > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0216: Management resource '[(\"server-group\" => \"otheother-server-group\")]' not found"}} > [domain@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3567) CLI, deployment enable-all/disable-all doesn't propose domain specific options

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-3567: -------------------------------------------- Summary: CLI, deployment enable-all/disable-all doesn't propose domain specific options Key: WFCORE-3567 URL: https://issues.jboss.org/browse/WFCORE-3567 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise The activators attached to these options are expecting an argument value, but there is no such argument. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9742) ClassLoader leak in JBoss Threads caused by MDBs

by Markus Dlugi (JIRA)

[ https://issues.jboss.org/browse/WFLY-9742?page=com.atlassian.jira.plugin.... ] Markus Dlugi updated WFLY-9742: ------------------------------- Git Pull Request: https://github.com/jbossas/jboss-threads/pull/24 > ClassLoader leak in JBoss Threads caused by MDBs > ------------------------------------------------ > > Key: WFLY-9742 > URL: https://issues.jboss.org/browse/WFLY-9742 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Final > Reporter: Markus Dlugi > Assignee: David Lloyd > Attachments: default-threads-tccl.png, jboss-threads-tccl-example.zip > > > There is a classloader leak in JBoss Threads which is most noticable when deploying MDBs. When a new MDB is created and a new thread for the MDB is started in the JCA thread pool ("default-threads - x"), the thread will be created using the context classloader of the MDB's deployment unit. This is because [MessageDrivenComponent.activate()|https://github.com/wildfly/wildfly/blob...] sets the context classloader of the ServerService thread in order to create the MDB, and this classloader will then also be used by the child thread. > In the default configuration, the threads in the default thread pool will not be terminated and therefore the thread will keep the reference to the classloader even when the deployment unit is undeployed. This in turn can lead to "OutOfMemoryError: Metaspace" after a couple of redeployments. > As a workaround, we changed [JBossThreadFactory.createThread()|https://github.com/jbossas/jboss-thread...] to set the context classloader to null after a new thread has been created. While this fixes the issue for us, I am not sure whether this is a good solution for all consumers of the thread factory, or if this should be fixed in the JCA subsystem instead. That's also the reason why I opened this issue against the WildFly project instead of JBoss Threads. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 January 2018