May 2015 - jboss-jira - Jboss List Archives

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

11 years, 2 months

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)

11 years, 2 months

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)

11 years, 2 months

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)

11 years, 2 months

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)

11 years, 2 months

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)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-598) Make it possible to register a child at a certain position

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-598?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-598: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Make it possible to register a child at a certain position > ---------------------------------------------------------- > > Key: WFCORE-598 > URL: https://issues.jboss.org/browse/WFCORE-598 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha1 > > > The BasicResource stores child resources in a LinkedHashMap so it is ordered in the order of the adds. It should be possible to insert a new child somewhere in the middle, rather than just at the end. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-597) Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-597?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-597: ------------------------------------ Fix Version/s: 2.0.0.Alpha1 (was: 1.0.0.CR1) > Where an ObjectTypeAttributeDefinition is in use respect the ResourceOnly setting on contained types for add operations. > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-597 > URL: https://issues.jboss.org/browse/WFCORE-597 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Labels: affects_elytron > Fix For: 2.0.0.Alpha1 > > > If an ObjectTypeAttributeDefinition contains an attribute definition that has ResourceOnly set then it should be filtered from the automatically generated description for the add operation. > This may be more related to lists, I currently have: - > ObjectListAttributeDefinition, which contains ObjectTypeAttributeDefinition, which contains SimpleAttributeDefinition > It is this final SimpleAttributeDefinition that has ResourceOnly set but it is still showing up in the operation description for add. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-364) Hangs in mixed domain testsuite

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-364?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-364: ------------------------------------ Fix Version/s: 2.0.0.Alpha2 (was: 1.0.0.CR1) > Hangs in mixed domain testsuite > ------------------------------- > > Key: WFCORE-364 > URL: https://issues.jboss.org/browse/WFCORE-364 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha2 > > Attachments: testsuite-hang1-server.txt, testsuite-hang2-client.txt, testsuite-hang2-server.txt > > > http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/wildfly-param-pull... > https://dl.dropboxusercontent.com/u/712508/mixed-hang-debug.zip contains details. > 30805.dump is the client and shows the problem is occurring in the @After cleanup of MixedDomainDeploymentTest as it removes deployments from the domain. > "main" prio=10 tid=0xf7605c00 nid=0x7856 in Object.wait() [0xf776e000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xe50275f0> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at java.lang.Object.wait(Object.java:503) > at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192) > - locked <0xe50275f0> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266) > - locked <0xe50275f0> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:100) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.as.controller.client.helpers.domain.impl.DomainClientImpl.execute(DomainClientImpl.java:81) > at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.removeDeployment(MixedDomainDeploymentTest.java:441) > at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.cleanDeployments(MixedDomainDeploymentTest.java:343) > at org.jboss.as.test.integration.domain.mixed.MixedDomainDeploymentTest.confirmNoDeployments(MixedDomainDeploymentTest.java:163) > 31894.dump shows the master HC. management-handler-thread is blocking on the way out (after sending the commit or rollback) waiting for a final result response from the slave. > "management-handler-thread - 1" prio=10 tid=0xca0efc00 nid=0x7cdd in Object.wait() [0xc7469000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0xeb6d6558> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at java.lang.Object.wait(Object.java:503) > at org.jboss.threads.AsyncFutureTask.await(AsyncFutureTask.java:192) > - locked <0xeb6d6558> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:266) > - locked <0xeb6d6558> (a org.jboss.as.protocol.mgmt.ActiveOperationSupport$ActiveOperationImpl) > at org.jboss.as.controller.client.impl.AbstractDelegatingAsyncFuture.get(AbstractDelegatingAsyncFuture.java:100) > at org.jboss.as.domain.controller.operations.coordination.DomainSlaveHandler.finalizeOp(DomainSlaveHandler.java:215) > at org.jboss.as.domain.controller.operations.coordination.DomainSlaveHandler.access$000(DomainSlaveHandler.java:58) > at org.jboss.as.domain.controller.operations.coordination.DomainSlaveHandler$1.handleResult(DomainSlaveHandler.java:179) > at org.jboss.as.controller.AbstractOperationContext$Step.handleRollback(AbstractOperationContext.java:805) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:763) > at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:738) > (Note that the "handleRollback" method name is a red-herring -- the method should be renamed to a "handleResult" as it now is called no matter what the result.) > 31986.dump is the slave HC. It shows it is blocking in stage DONE after having sent operationPrepared to the master, waiting for commit or rollback. > "domain-connection-threads - 1" prio=10 tid=0xc91a8400 nid=0x7d1a waiting on condition [0xc87fe000] > java.lang.Thread.State: WAITING (parking) > at sun.misc.Unsafe.park(Native Method) > - parking to wait for <0xea1fd410> (a java.util.concurrent.CountDownLatch$Sync) > at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994) > at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303) > at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236) > at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ProxyOperationControlProxy.operationPrepared(TransactionalProtocolOperationHandler.java:173) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:337) > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) > at org.jboss.as.domain.controller.operations.coordination.ServerOperationsResolverHandler.execute(ServerOperationsResolverHandler.java:128) > Indication is the commit or rollback message is getting lost. There are no threads shown sending or receiving it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-383) Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources>

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-383?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-383: ------------------------------------ Fix Version/s: 2.0.0.Alpha2 (was: 1.0.0.CR1) > Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources> > ---------------------------------------------------------------------------------------------------- > > Key: WFCORE-383 > URL: https://issues.jboss.org/browse/WFCORE-383 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 2.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

11 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 May 2015