March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1316) patch apply command not working as expected in non-interactive mode in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1316?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1316: ------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1290290|https://bugzilla.redhat.com/show_bug.cgi?id=1290290] from MODIFIED to POST > patch apply command not working as expected in non-interactive mode in domain mode > ----------------------------------------------------------------------------------- > > Key: WFCORE-1316 > URL: https://issues.jboss.org/browse/WFCORE-1316 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 2.0.8.Final > > > CLI patch apply command is misleading when the --host option is used. In non-interactive mode applies the patch to the local installation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-562) Wrong order of elements in jboss-cli.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-562?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-562: ------------------------------------------------ Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1195132|https://bugzilla.redhat.com/show_bug.cgi?id=1195132] from MODIFIED to POST > Wrong order of elements in jboss-cli.xml > ---------------------------------------- > > Key: WFCORE-562 > URL: https://issues.jboss.org/browse/WFCORE-562 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha19 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > Fix For: 1.0.0.Beta1 > > > File bin/jboss-cli.xml has an incorrect order of elements. <history> tag should be before <resolve-parameter-values> tag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4590) l1-lifespan attribute in distributed cache configuration does not enable l1 cache

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4590?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4590: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1218148|https://bugzilla.redhat.com/show_bug.cgi?id=1218148] from MODIFIED to POST > l1-lifespan attribute in distributed cache configuration does not enable l1 cache > --------------------------------------------------------------------------------- > > Key: WFLY-4590 > URL: https://issues.jboss.org/browse/WFLY-4590 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > > l1-lifespan attribute in distributed cache configuration is not honored. If set to a non-zero value it just sets the underlying cache config parameter, but does not explicitly enable l1 which is by default disabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5381) Fix pom.xml jpda profile and add ability to specify additional surefire forked JVM args via command line

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5381?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5381: ----------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1265229|https://bugzilla.redhat.com/show_bug.cgi?id=1265229] from MODIFIED to POST > Fix pom.xml jpda profile and add ability to specify additional surefire forked JVM args via command line > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-5381 > URL: https://issues.jboss.org/browse/WFLY-5381 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 10.0.0.CR1 > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > Fix For: 10.0.0.CR4 > > > mvn install -Pjpda should run the tests with debugging enabled but it does not as the surefire.jpda.args property is ignored. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-670?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-670: ------------------------------------------------ Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1277320|https://bugzilla.redhat.com/show_bug.cgi?id=1277320] from MODIFIED to POST > Node type is not complete at index 0 after tab completion on an empty resource > ------------------------------------------------------------------------------ > > Key: WFCORE-670 > URL: https://issues.jboss.org/browse/WFCORE-670 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: James Perkins > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 1.0.0.CR2 > > > Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working. > {code:title=Example Output} > [standalone@localhost:9990 /] /system-property= > The operation name is missing or the format of the operation request is wrong. > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] exit > Node type is not complete at index 0 > [standalone@localhost:9990 /] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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: ------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1280262|https://bugzilla.redhat.com/show_bug.cgi?id=1280262] from MODIFIED to POST > 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 (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1209) jboss-cli.sh ignoring invalid attribute when used in batch mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1209?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1209: ------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1289467|https://bugzilla.redhat.com/show_bug.cgi?id=1289467] from MODIFIED to POST > jboss-cli.sh ignoring invalid attribute when used in batch mode > --------------------------------------------------------------- > > Key: WFCORE-1209 > URL: https://issues.jboss.org/browse/WFCORE-1209 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.4.Final > Reporter: Abhijit Humbe > Assignee: Chao Wang > Fix For: 2.0.5.Final > > > CLI did not throw any error message and just ignored the invalid attribute while using in batch mode.If we use same CLI command in non-batch mode it throws exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1198) CLI does not resolve multiple properties if one property is undefined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1198?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1198: ------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1289316|https://bugzilla.redhat.com/show_bug.cgi?id=1289316] from MODIFIED to POST > CLI does not resolve multiple properties if one property is undefined > --------------------------------------------------------------------- > > Key: WFCORE-1198 > URL: https://issues.jboss.org/browse/WFCORE-1198 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.4.Final > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 2.0.5.Final > > > https://bugzilla.redhat.com/show_bug.cgi?id=1289316 description: > {noformat} > Multiple property substitution is working with EAP 6.4.3+, however, if a variable amongst the multiple variables is empty or has no value, then the subsequent property in the CLI command is not substituted. > For example : > cat props.properties > ----------------------------------------- > PROFILE-NAME=TestProfile > SERVER-INSTANCE-NUMBER=TestInstance > APP-VERSION= > VAR=test > ----------------------------------------- > cat test.cli : > --------------------------------------- > /host=master/server-config=${PROFILE-NAME}${APP-VERSION}${SERVER-INSTANCE-NUMBER}${VAR}:add(auto-start=true, group="${PROFILE-NAME}${APP-VERSION}-server-group") > --------------------------------------- > and if I execute "./jboss-cli.sh --connect --file=test.cli --properties=props.properties" then I have the following in the host.xml ": > ---------- > ... > <server name="TestProfile${SERVER-INSTANCE-NUMBER}test" group="TestProfile-server-group" auto-start="true"/> > ... > ----------- > Note APP-VERSION had no value, and so the subsequent SERVER-INSTANCE-NUMBER was not properly resolved > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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: ------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1294010|https://bugzilla.redhat.com/show_bug.cgi?id=1294010] from MODIFIED to POST > 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 (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1304) WFLYCTL0013: Operation ("clean-obsolete-content") failed .. StringIndexOutOfBoundsException when OS puts metadata files in content repo

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1304?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1304: ------------------------------------------------- Mike McCune <mmccune(a)redhat.com> changed the Status of [bug 1299189|https://bugzilla.redhat.com/show_bug.cgi?id=1299189] from MODIFIED to POST > WFLYCTL0013: Operation ("clean-obsolete-content") failed .. StringIndexOutOfBoundsException when OS puts metadata files in content repo > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1304 > URL: https://issues.jboss.org/browse/WFCORE-1304 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brad Maxwell > Assignee: Chao Wang > Fix For: 2.0.8.Final > > > Mac OS can put .DS_Store files into the content repo directory. This can also be reproduced on Linux by creating a file under the content dir and when clean-obsolete-content() runs it will log this error. It seems it runs every 10 minutes. > {code} > 22:59:48,289 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 1) WFLYDR0009: Content /Users/bradley/Desktop/wildfly-10.0.0.CR5/standalone/data/content/9b/.DS_Store is obsolete and will be removed > 22:59:48,290 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 1) WFLYCTL0013: Operation ("clean-obsolete-content") failed - address: ([]): java.lang.StringIndexOutOfBoundsException: String index out of range: 11 > at java.lang.String.charAt(String.java:658) > at org.jboss.as.repository.HashUtil.hexStringToByteArray(HashUtil.java:62) > at org.jboss.as.repository.ContentReference.getHash(ContentReference.java:68) > at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.removeContent(ContentRepository.java:365) > at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.markAsObsolete(ContentRepository.java:427) > at org.jboss.as.repository.ContentRepository$Factory$ContentRepositoryImpl.cleanObsoleteContent(ContentRepository.java:403) > at org.jboss.as.server.operations.CleanObsoleteContentHandler.execute(CleanObsoleteContentHandler.java:76) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204) > at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:659) > at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:649) > at org.jboss.as.server.deployment.ContentRepositoryCleaner.cleanObsoleteContent(ContentRepositoryCleaner.java:132) > at org.jboss.as.server.deployment.ContentRepositoryCleaner$ContentRepositoryCleanerTask.run(ContentRepositoryCleaner.java:67) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > 22:59:48,292 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 1) WFLYSRV0216: Error cleaning obsolete content WFLYCTL0158: Operation handler failed: java.lang.StringIndexOutOfBoundsException: String index out of range: 11 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 March 2016