January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1018) PeriodicSizeRotatingFileHandler's are always replaced during boot

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1018?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1018: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1266360|https://bugzilla.redhat.com/show_bug.cgi?id=1266360] from VERIFIED to CLOSED > PeriodicSizeRotatingFileHandler's are always replaced during boot > ----------------------------------------------------------------- > > Key: WFCORE-1018 > URL: https://issues.jboss.org/browse/WFCORE-1018 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.0.0.CR6 > > > A {{periodic-size-rotating-file-handler}} will be replaced during the subsystem add operation. This could be an issue with {{async-handler}}'s where the handler may see the old handler that was closed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7034) JDR is not collecting the file .overlays, layer.conf, version.txt config files

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-7034?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-7034: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1372781|https://bugzilla.redhat.com/show_bug.cgi?id=1372781] from VERIFIED to CLOSED > JDR is not collecting the file .overlays, layer.conf, version.txt config files > ------------------------------------------------------------------------------ > > Key: WFLY-7034 > URL: https://issues.jboss.org/browse/WFLY-7034 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 10.1.0.Final > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > The JDR report when collecting files should be collecting > $JBOSS_HOME/modules/system/layers/base/.overlays/.overlays > $JBOSS_HOME/.installation/identity.conf > $JBOSS_HOME/.installation/layers/base/layer.conf > $JBOSS_HOME/.installation/patches/*/misc/version.txt > This file is needed to confirm overlay priority and other layer configurations to make sure the installation is not corrupted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-499) System properties are broken in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-499?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-499: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1257301|https://bugzilla.redhat.com/show_bug.cgi?id=1257301] from VERIFIED to CLOSED > System properties are broken in domain mode > ------------------------------------------- > > Key: WFCORE-499 > URL: https://issues.jboss.org/browse/WFCORE-499 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha15 > Reporter: Stuart Douglas > Assignee: ehsavoie Hugonnet > Fix For: 1.0.0.Alpha17 > > > There seems to be some weirdness in how system properties are being propagated to domain mode servers, and in many cases they are not being applied. > This appears to be an issue with the boot time handling of system properties. > The only way I could get the property to be applied was to start the server first, then add the property using boot-time=false, although even in this case the property will disappear if the domain is restarted or the server is reloaded. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6680) :read-proxies-configuration and :read-proxies-info fail when at least one of the proxies is unreachable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6680?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6680: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1343633|https://bugzilla.redhat.com/show_bug.cgi?id=1343633] from VERIFIED to CLOSED > :read-proxies-configuration and :read-proxies-info fail when at least one of the proxies is unreachable > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-6680 > URL: https://issues.jboss.org/browse/WFLY-6680 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.0.0.Final > Environment: RHEL 6, EAP 6.1.0, mod_cluster-1.2.4-1.Final_redhat_1.ep6.el6.noarch, > Reporter: Kristina Clair > Assignee: Radoslav Husar > Labels: downstream_dependency > Fix For: 10.1.0.CR1, 10.1.0.Final > > > When the modcluster subsystem is unable to connect to a proxy, the jboss-cli commands :read-proxies-configuration and :read-proxies-info fail with an unhelpful error. > On both the domain controller and application host, :read-proxies-info and :read-proxies-configuration fail with the same error. This is the output from the application host: > {noformat} > [domain@localhost:9999 subsystem=modcluster] pwd > /host=localhost/server=cluster2/subsystem=modcluster > [domain@localhost:9999 subsystem=modcluster] :list-proxies > { > "outcome" => "success", > "result" => [ > "web02:8009", > "web01:8009" > ] > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-configuration > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > [domain@localhost:9999 subsystem=modcluster] :read-proxies-info > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS014749: Operation handler failed: newValue is null", > "rolled-back" => true > } > {noformat} > In the above example, modcluster was not able to connect to the proxies due to an ssl misconfiguration in the modcluster subsystem in domain.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-102) Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-102?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-102: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1299102|https://bugzilla.redhat.com/show_bug.cgi?id=1299102] from VERIFIED to CLOSED > Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-102 > URL: https://issues.jboss.org/browse/WFCORE-102 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.Alpha9 > > > The various base classes OSH authors use to create handlers force the author to deal with ServiceVerificationHandler and, during rollback, with removing any services the OSH added. This task is to have the OperationContext handle these things transparently, removing the need for authors to do so. > To preserve compatibility, the various API methods authors may have overridden that expose the SVH and the list of added ServiceControllers will be retained (but deprecated), but the SVH and the list of handlers won't be used. The API javadoc will encourage use of method variants that don't use these parameters. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3578) jboss-cli.bat always exits with return code 0 even after a cli failure

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3578?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3578: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1223877|https://bugzilla.redhat.com/show_bug.cgi?id=1223877] from VERIFIED to CLOSED > jboss-cli.bat always exits with return code 0 even after a cli failure > ---------------------------------------------------------------------- > > Key: WFLY-3578 > URL: https://issues.jboss.org/browse/WFLY-3578 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.1.0.Final > Environment: Windows > Reporter: Gabriele Garuglieri > Assignee: Alexey Loubyansky > Fix For: 9.0.0.Alpha1 > > > jboss-cli.bat cannot be reliably controlled by other scripts because it does not report return code from cli execution and always exits with 0 even after a failure. > It can be solved with the following patch: > {noformat} > --- C:/home/JBoss/wildfly-8.1.0.Final/bin/jboss-cli-orig.bat Sat May 31 04:54:25 2014 > +++ C:/home/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.bat Thu Jul 03 10:19:09 2014 > @@ -1,4 +1,5 @@ > @echo off > +setlocal ENABLEEXTENSIONS > rem ------------------------------------------------------------------------- > rem JBoss Admin CLI Script for Windows > rem ------------------------------------------------------------------------- > @@ -48,6 +49,7 @@ > if not exist "%JBOSS_RUNJAR%" ( > echo Could not locate "%JBOSS_RUNJAR%". > echo Please check that you are in the bin directory when running this script. > + set /A RC=1 > goto END > ) > > @@ -71,5 +73,11 @@ > org.jboss.as.cli ^ > %* > > +set /A RC=%errorlevel% > :END > if "x%NOPAUSE%" == "x" pause > + > +if "x%RC%" == "x" ( > + set /A RC=0 > +) > +exit /B %RC% > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1226) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1226?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1226: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1280262|https://bugzilla.redhat.com/show_bug.cgi?id=1280262] from VERIFIED to CLOSED > undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-1226 > URL: https://issues.jboss.org/browse/WFCORE-1226 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.4.Final > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 2.0.6.Final > > Attachments: WFCORE-1226-wildflytest.patch, WFCORE-1226.patch > > > {noformat} > 1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command: > ~~ > [domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war > ~~~ > 2. Deploy next version of application in "disabled" state with same "runtime-name" > ~~~ > [domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war > ~~~ > 3. Now use replace-deployment command to access latest version of application: > ~~~ > [domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war) > ~~~ > its working fine,laest version of application is accessable. > 4. Now try to undeploy old version of application > ~~~ > /server-group=main-server-group/deployment=WebApp-1.war:undeploy() > ~~~ > After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it. > Same steps are working fine in Standalone mode. > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4942) KeyAffinityService race condition on view change

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4942?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4942: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1233968|https://bugzilla.redhat.com/show_bug.cgi?id=1233968] from VERIFIED to CLOSED > KeyAffinityService race condition on view change > ------------------------------------------------ > > Key: WFLY-4942 > URL: https://issues.jboss.org/browse/WFLY-4942 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Bartosz Baranowski > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1257) support query filter implementation in MBeanServerConnection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1257?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1257: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1294010|https://bugzilla.redhat.com/show_bug.cgi?id=1294010] from VERIFIED to CLOSED > support query filter implementation in MBeanServerConnection > ------------------------------------------------------------ > > Key: WFCORE-1257 > URL: https://issues.jboss.org/browse/WFCORE-1257 > Project: WildFly Core > Issue Type: Bug > Components: JMX > Affects Versions: 2.0.5.Final > Reporter: Chao Wang > Assignee: Brian Stansberry > Fix For: 2.0.8.Final > > > There is no implementation for query filter in MBeanServerConnection, marked as TODO > {code:title=ModelControllerMBeanHelper.java|borderStyle=solid} > Set<ObjectName> queryNames(final ObjectName name, final QueryExp query) { > return new RootResourceIterator<Set<ObjectName>>(accessControlUtil, getRootResourceAndRegistration().getResource(), > new ObjectNameMatchResourceAction<Set<ObjectName>>(name) { > Set<ObjectName> set = new HashSet<ObjectName>(); > @Override > public boolean onResource(ObjectName resourceName) { > if (name == null || name.apply(resourceName)) { > //TODO check query > set.add(resourceName); > } > return true; > } > @Override > public Set<ObjectName> getResult() { > if (set.size() == 1 && set.contains(ModelControllerMBeanHelper.createRootObjectName(domain))) { > return Collections.emptySet(); > } > return set; > } > }).iterate(); > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-127) Module naming does does not support slots

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-127?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on LOGMGR-127: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1283482|https://bugzilla.redhat.com/show_bug.cgi?id=1283482] from VERIFIED to CLOSED > Module naming does does not support slots > ----------------------------------------- > > Key: LOGMGR-127 > URL: https://issues.jboss.org/browse/LOGMGR-127 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Livingston > Assignee: James Livingston > Fix For: 1.5.6.Final, 2.0.4.Final, 2.1.0.Beta1 > > > AbstractPropertyConfiguration$ModuleFinder uses ModuleIdentifier.create() rather than fromString(), which means it does not support specifying the slot via "module:slot" and can only use the main slot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 2017