May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-109) Update syslog handler attributes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-109?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-109: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Update syslog handler attributes > -------------------------------- > > Key: WFCORE-109 > URL: https://issues.jboss.org/browse/WFCORE-109 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Minor > Fix For: 2.0.0.Alpha1 > > > The syslog handler does not currently expose the formatter for formatting messages. There will also be changes in a future logmanager release for TCP support and various other properties based on the new TCP support. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-602) Ability to view an objects index of it's position in a list.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-602?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-602: ------------------------------------ Fix Version/s: (was: 1.0.0.CR1) > Ability to view an objects index of it's position in a list. > ------------------------------------------------------------ > > Key: WFCORE-602 > URL: https://issues.jboss.org/browse/WFCORE-602 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > > General improvements are being made to the management model for more fine grained manipulation of complex attributes, amongst these changes will be the ability to insert items at a specific position in a list. > This feature request is to ask for the ability to see an items index to identify it's position. > i.e. an end user can call :read-recource and see an items position without needing to count how many items there are in order to identify the position of the next insert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-602) Ability to view an objects index of it's position in a list.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-602?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFCORE-602: ----------------------------------------- This sounds like a structural change to the output format. > Ability to view an objects index of it's position in a list. > ------------------------------------------------------------ > > Key: WFCORE-602 > URL: https://issues.jboss.org/browse/WFCORE-602 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > Fix For: 1.0.0.CR1 > > > General improvements are being made to the management model for more fine grained manipulation of complex attributes, amongst these changes will be the ability to insert items at a specific position in a list. > This feature request is to ask for the ability to see an items index to identify it's position. > i.e. an end user can call :read-recource and see an items position without needing to count how many items there are in order to identify the position of the next insert. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-651) Port jboss-as-remoting_1_2.xsd to WildFly Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-651?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-651: ------------------------------------ Fix Version/s: 1.0.0.CR2 (was: 1.0.0.CR1) Moving to 1.0.0.CR2, although it's possible we'll defer to 2.0. > Port jboss-as-remoting_1_2.xsd to WildFly Core > ---------------------------------------------- > > Key: WFCORE-651 > URL: https://issues.jboss.org/browse/WFCORE-651 > Project: WildFly Core > Issue Type: Sub-task > Components: Remoting > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-646) Product to Project Schema and Model Sync

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-646?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-646: ------------------------------------ Fix Version/s: 1.0.0.CR2 (was: 1.0.0.CR1) Moving to 1.0.0.CR2, although it's possible we'll defer to 2.0. > Product to Project Schema and Model Sync > ---------------------------------------- > > Key: WFCORE-646 > URL: https://issues.jboss.org/browse/WFCORE-646 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.CR2 > > > Periodic sync of EAP schemas with WildFly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-603) Simplify working with complex attributes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-603?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-603: ------------------------------------ Fix Version/s: 2.0.0.Beta1 (was: 1.0.0.CR1) > Simplify working with complex attributes > ---------------------------------------- > > Key: WFCORE-603 > URL: https://issues.jboss.org/browse/WFCORE-603 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 2.0.0.Beta1 > > > This is umbrella issue for all complex attributes related enhancements and simplifications. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-668) Make the INFO logging from deprecated attributes configurable, also improve the message

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-668?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-668: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Make the INFO logging from deprecated attributes configurable, also improve the message > --------------------------------------------------------------------------------------- > > Key: WFCORE-668 > URL: https://issues.jboss.org/browse/WFCORE-668 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha1 > > > The INFO logging that AttributeDefinition generates when a deprecated attribute is used needs to be configurable, i.e. with a boolean flag so a dev can turn it off for attributes where it serves no purpose. > The logging only serves a purpose if an admin can take action to use some alternative config. If an attribute is deprecated only because in some future release it will go away, but there's no replacement now, the logging is just noise. > The log message itself should be improved: > 1) Get rid of the ! at the end. It's not that exciting. ;) > 2) Include the address of the resource > 3) Point the user at the read-resource-description output from which they can learn more about the deprecation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-669) Make it possible to propagate attachments from the operation context to the transformer context

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-669?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-669: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Make it possible to propagate attachments from the operation context to the transformer context > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-669 > URL: https://issues.jboss.org/browse/WFCORE-669 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha1 > > > The transformation context needs attachments, and the operation context attachments should be propagable to the transformation context so that the write attribute handlers can give signals to the transformers. We don't want to propagate everything, so I have created TransformerOperationAttachment which in turn contains attach() methods. Only attachments added there get propagated. > One use case is if the old model used child resources, so it has child=1, child=2. If the new model was refactored to use this as a map attribute on the parent resource, when the attribute is overwritten, the transformer needs to create a composite to add what is new, remove what is missing, and update things which were changed. However, this is not known to the transformer. So the idea is that the write attribute handler can use these attachments to signal the transformer about what has been added and removed by comparing the new and old values. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-649) Port jboss-as-logging_1_5.xsd to WildFly Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-649?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-649: ------------------------------------ Fix Version/s: 1.0.0.CR2 (was: 1.0.0.CR1) > Port jboss-as-logging_1_5.xsd to WildFly Core > --------------------------------------------- > > Key: WFCORE-649 > URL: https://issues.jboss.org/browse/WFCORE-649 > Project: WildFly Core > Issue Type: Sub-task > Components: Logging > Reporter: Darran Lofthouse > Assignee: James Perkins > Fix For: 1.0.0.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-657) CLI embedded server does not always clean up properly

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-657?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-657: ------------------------------------ Fix Version/s: 1.0.0.CR2 (was: 1.0.0.CR1) > CLI embedded server does not always clean up properly > ----------------------------------------------------- > > Key: WFCORE-657 > URL: https://issues.jboss.org/browse/WFCORE-657 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Beta1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 1.0.0.CR2 > > > While looking at some other test issues I noticed test logging that indicates that the server embedded in the CLI seems to not always be cleaning up properly, resulting in MSC leaving mbeans installed and subsequent mbean registration errors when the next attempt to launch happens. > Here's an example from a server.log; my impression is one test method attempts to create a server with an invalid --empty-config param, and when that fails the appropriate cleanup doesn't happen. > {code} > 2015-04-20 11:27:44,020 ERROR [org.jboss.msc.service.fail] (MSC service thread 17-1) MSC000001: Failed to start service jboss.as.server-controller: org.jboss.msc.service.StartException in service jboss.as.server-controller: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.IllegalStateException: WFLYCTL0389: Could not create an empty configuration at file /Users/bstansberry/dev/wildfly/wildfly-core/testsuite/manualmode/target/wildfly-core/standalone/configuration/standalone-cli.xml as there is an existing non-empty configuration there > at org.jboss.as.controller.persistence.ConfigurationFile.getBootFile(ConfigurationFile.java:242) > at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.<init>(BackupXmlConfigurationPersister.java:70) > at org.jboss.as.server.Bootstrap$Configuration$1.createConfigurationPersister(Bootstrap.java:178) > at org.jboss.as.server.ServerService.start(ServerService.java:241) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... 3 more > 2015-04-20 11:27:44,031 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.2.Final > 2015-04-20 11:27:44,032 ERROR [org.jboss.msc] (main) MSC000010: Failed to register MBean with MBeanServer: javax.management.InstanceAlreadyExistsException: jboss.msc:type=container,name=jboss-as > at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) > at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) > at org.jboss.msc.service.ServiceContainerImpl.<init>(ServiceContainerImpl.java:372) > at org.jboss.msc.service.ServiceContainer$Factory.create(ServiceContainer.java:266) > at org.jboss.as.server.BootstrapImpl$ShutdownHook.register(BootstrapImpl.java:198) > at org.jboss.as.server.BootstrapImpl$ShutdownHook.access$100(BootstrapImpl.java:188) > at org.jboss.as.server.BootstrapImpl.<init>(BootstrapImpl.java:62) > at org.jboss.as.server.Bootstrap$Factory.newInstance(Bootstrap.java:243) > at org.wildfly.core.embedded.EmbeddedStandAloneServerFactory$StandaloneServerImpl.start(EmbeddedStandAloneServerFactory.java:280) > at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.wildfly.core.embedded.StandaloneServerIndirection.invokeOnServer(StandaloneServerIndirection.java:70) > at org.wildfly.core.embedded.StandaloneServerIndirection.start(StandaloneServerIndirection.java:55) > at org.jboss.as.cli.embedded.EmbedServerHandler.doHandle(EmbedServerHandler.java:201) > at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:88) > at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:676) > at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:163) > at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:177) > at org.jboss.as.test.manualmode.management.cli.CLIEmbedServerTestCase.stdoutTest(CLIEmbedServerTestCase.java:219) > at org.jboss.as.test.manualmode.management.cli.CLIEmbedServerTestCase.testStdOutEcho(CLIEmbedServerTestCase.java:199) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2015