January 2018 - jboss-jira - Jboss List Archives

[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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3563) Could not enable application deployment on two server groups in domain

by Vratislav Marek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3563?page=com.atlassian.jira.plugi... ] Vratislav Marek commented on WFCORE-3563: ----------------------------------------- *I found it in version Jboss EAP7 to* {noformat} [domain@localhost:9990 /] version JBoss Admin Command-line Interface JBOSS_HOME: /media/Data/TestArea/Install/EAP Release: 3.0.10.Final-redhat-1 "Kenny" Product: JBoss EAP 7.1.0.GA JAVA_HOME: /var/jdk-stable/ java.version: 1.8.0_151 java.vm.vendor: Oracle Corporation java.vm.version: 25.151-b12 os.name: Linux os.version: 4.13.16-100.fc25.x86_64 [domain@localhost:9990 /] {noformat} {noformat} [domain@localhost:9990 /] deploy --server-groups=main-server-group,other-server-group /media/Data/Repos/Remote/Public/tmp/Resource/Part000.war [domain@localhost:9990 /] deployment-info --server-group=main-server-group NAME RUNTIME-NAME STATE Part000.war Part000.war enabled [domain@localhost:9990 /] deployment-info --server-group=other-server-group NAME RUNTIME-NAME STATE Part000.war Part000.war enabled [domain@localhost:9990 /] [domain@localhost:9990 /] undeploy Part000.war --keep-content --server-groups=main-server-group,other-server-group [domain@localhost:9990 /] deployment-info --server-group=main-server-group NAME RUNTIME-NAME STATE Part000.war Part000.war added [domain@localhost:9990 /] deployment-info --server-group=other-server-group NAME RUNTIME-NAME STATE Part000.war Part000.war added [domain@localhost:9990 /] undeploy Part000.war --keep-content --server-groups=main-server-group,other-server-group [domain@localhost:9990 /] deploy --name=Part000.war --server-groups=main-server-group,other-server-group {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ (\"server-group\" => \"main-server-group\"), (\"deployment\" => \"Part000.war\") [domain@localhost:9990 /] {noformat} > Could not enable application deployment on two server groups in domain > ---------------------------------------------------------------------- > > Key: WFCORE-3563 > URL: https://issues.jboss.org/browse/WFCORE-3563 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Vratislav Marek > Assignee: Jean-Francois Denise > > {noformat} > [domain@localhost:9990 /] deployment enable --server-groups=other-server-group,main-server-group cli-test-app-deploy-all.ear > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ > (\"server-group\" => \"other-server-group\"), > (\"deployment\" => \"cli-test-app-deploy-all.ear\") > ]"}} > [domain@localhost:9990 /] > {noformat} > {noformat} > [domain@localhost:9990 /] deploy --name=cli-test-app-deploy-all.ear --server-groups=other-server-group,main-server-group > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0212: Duplicate resource [ > (\"server-group\" => \"other-server-group\"), > (\"deployment\" => \"cli-test-app-deploy-all.ear\") > ]"}} > [domain@localhost:9990 /] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3273) sharedState is passed null by PluginAuthenticationCallbackHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3273?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-3273: ------------------------------------------------- Lukas Svaty <lsvaty(a)redhat.com> changed the Status of [bug 1490383|https://bugzilla.redhat.com/show_bug.cgi?id=1490383] from ON_QA to VERIFIED > sharedState is passed null by PluginAuthenticationCallbackHandler > ----------------------------------------------------------------- > > Key: WFCORE-3273 > URL: https://issues.jboss.org/browse/WFCORE-3273 > Project: WildFly Core > Issue Type: Bug > Components: Security > Environment: Fedora 26, using ovirt-engine-wildfly package > Reporter: Roy Golan > Assignee: Darran Lofthouse > Fix For: 3.0.2.Final, 4.0.0.Alpha1 > > > oVirt's ovirt-engine uses an authentication plugin [1] for management interface that recently after upgrading to Wildfly 11 stopped working. The reason is the sharedState passed to the plugin's init method is now null. > A current workaround this would be to avoid adding the plugin into the shareState, but that means any delegating plugin would fail to find this plugin and possibly other bad stuff I'm not aware of. > [1] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=backend/manag... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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], thank-you for reporting the issue, if you plan to add a unit test to cover the problem, we have a CliCompletionTestCase class in testsuite/domain that is perfect to deal with this kind of issues. You could add a new test in it. Thanks. > 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2280) Resolving rule unit classnames depends on File.separator character

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2280?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2280: ---------------------------------- Description: When running testNamingConventionOnDrlFile test on Windows, it fails on NPE, because the engine cannot find the rule unit "org/kie/test/MyRuleUnit" defined in the test, because it contains "/" separator character. The method that resolves the classname searches for File.separator character in the mentioned string, which is "\" on Windows [1]. This is a bug, because e.g. MemoryFileSystem uses "/" also when running on Windows. The classname resolution should be OS independent. [1] https://github.com/kiegroup/drools/blob/5fad04919f255933bdd34afdb8da10b94... was: When running testNamingConventionOnDrlFile test on Windows, it fails on NPE, because the engine cannot find the rule unit "org/kie/test/MyRuleUnit" defined in the test, because it contains "/" separator character. I will provide a fix to the test. For resolving the rule unit class, the engine uses OS independent character correctly here [1]. [1] https://github.com/kiegroup/drools/blob/5fad04919f255933bdd34afdb8da10b94... > Resolving rule unit classnames depends on File.separator character > ------------------------------------------------------------------ > > Key: DROOLS-2280 > URL: https://issues.jboss.org/browse/DROOLS-2280 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > Priority: Minor > > When running testNamingConventionOnDrlFile test on Windows, it fails on NPE, because the engine cannot find the rule unit "org/kie/test/MyRuleUnit" defined in the test, because it contains "/" separator character. The method that resolves the classname searches for File.separator character in the mentioned string, which is "\" on Windows [1]. > This is a bug, because e.g. MemoryFileSystem uses "/" also when running on Windows. The classname resolution should be OS independent. > [1] https://github.com/kiegroup/drools/blob/5fad04919f255933bdd34afdb8da10b94... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2280) Resolving rule unit classnames depends on File.separator character

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2280?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2280: ---------------------------------- Summary: Resolving rule unit classnames depends on File.separator character (was: Test RuleUnitTest.testNamingConventionOnDrlFile() uses OS specific separator character) > Resolving rule unit classnames depends on File.separator character > ------------------------------------------------------------------ > > Key: DROOLS-2280 > URL: https://issues.jboss.org/browse/DROOLS-2280 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.5.0.Final > Reporter: Tibor Zimányi > Assignee: Tibor Zimányi > Priority: Minor > > When running testNamingConventionOnDrlFile test on Windows, it fails on NPE, because the engine cannot find the rule unit "org/kie/test/MyRuleUnit" defined in the test, because it contains "/" separator character. > I will provide a fix to the test. > For resolving the rule unit class, the engine uses OS independent character correctly here [1]. > [1] https://github.com/kiegroup/drools/blob/5fad04919f255933bdd34afdb8da10b94... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

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

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9742?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-9742: ----------------------------------- I'm in a conference this week, so I won't get to it until next week. If you want to work up a PR that would be great. > 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)

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