February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-205) AttributeDefinition validateOperation should convert all expression strings to ModelType.EXPRESSION

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-205?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-205: ---------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) (was: 8.0.0.Final) > AttributeDefinition validateOperation should convert all expression strings to ModelType.EXPRESSION > --------------------------------------------------------------------------------------------------- > > Key: WFLY-205 > URL: https://issues.jboss.org/browse/WFLY-205 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > AttributeDefinition.validateOperation currently only converts a string to an expression if the attribute supports expressions. It should convert any time it sees the syntax. This way if a STRING attribute that doesn't support expressions finds one, it will reject it instead of accepting it as a raw string. > Scheduling for 7.3 out of concern this may break things in 7.2 without time to notice/adapt. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-122) Clean unreferenced deployments from the content repository

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-122?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-122: ---------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) (was: 8.0.0.Final) > Clean unreferenced deployments from the content repository > ---------------------------------------------------------- > > Key: WFLY-122 > URL: https://issues.jboss.org/browse/WFLY-122 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-262?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-262: ---------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) (was: 8.0.0.Final) > Update the DC's IgnoredTransformationRegistry when changes are made to a slave's <ignored-resources> > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-262 > URL: https://issues.jboss.org/browse/WFLY-262 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 9.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-231) HostControllerConnectionService connection timeout is not configurable

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-231?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-231: ---------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) (was: 8.0.0.Final) > HostControllerConnectionService connection timeout is not configurable > ---------------------------------------------------------------------- > > Key: WFLY-231 > URL: https://issues.jboss.org/browse/WFLY-231 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Dominik Pospisil > Assignee: Bartosz Baranowski > Fix For: 9.0.0.CR1 > > > I am seeing intermittent failures when starting AS7 in domain mode. It seems that this is due to HostControllerConnectionService has hardcoded 15s timeout when trying to connect to DC. I think that this value should be configurable. > HostControllerConnectionService.java: > ... > ProtocolChannelClient.Configuration configuration = new ProtocolChannelClient.Configuration(); > configuration.setEndpoint(endpointInjector.getValue()); > configuration.setConnectionTimeout(15000); > configuration.setUri(new URI("remote://" + hcAddressInjector.getValue().getHostName() + ":" + hcAddressInjector.getValue().getPort())); > client = ProtocolChannelClient.create(configuration); > ... > Exception I am getting: > [Server:server-two] 13:52:54,766 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out > [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:103) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] > [Server:server-two] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] > [Server:server-two] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://localhost.localdomain:9999. The connection timed out > [Server:server-two] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:166) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-229) Expose mgmt client socket binding config through ModelControllerClient Factory

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-229?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-229: ---------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) (was: 8.0.0.Final) > Expose mgmt client socket binding config through ModelControllerClient Factory > ------------------------------------------------------------------------------ > > Key: WFLY-229 > URL: https://issues.jboss.org/browse/WFLY-229 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 9.0.0.CR1 > > > Parent task used a secret system property to configure this to support Open Shift's immediate need, but proper configuration is needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-315) Avoid running out of threads when connecting to the DC from a slave to pull down missing data

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-315?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-315: ---------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) (was: 8.0.0.Final) > Avoid running out of threads when connecting to the DC from a slave to pull down missing data > --------------------------------------------------------------------------------------------- > > Key: WFLY-315 > URL: https://issues.jboss.org/browse/WFLY-315 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Emanuel Muckenhuber > Fix For: 9.0.0.CR1 > > > For WFLY-259 when a slave connects to the DC to pull down missing data, it does this by either getting a lock for the DC, or by joining the permit of the existing DC lock if the request to update a slave's server-config was executed as part of a composite obtaining a lock on the DC. > The way it works at present there is a thread per slave which is blocked until the transaction completes. The DC threads are a finite resource, so a large number of slaves trying to pull down dats will cause deadlock -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-458) ServerInventory#reconnectServer should take auto-start into account

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-458?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-458: ---------------------------------- Fix Version/s: 8.0.1.Final (was: 8.0.0.Final) Scheduling for 8.0.1 as this is a bug fix. But moving to 9 is ok. > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: WFLY-458 > URL: https://issues.jboss.org/browse/WFLY-458 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Emanuel Muckenhuber > Fix For: 8.0.1.Final > > > When reconnecting to stopped (but not removed) servers, the ServerInventory should take the auto-start property into account. Otherwise the process will just get removed, however started with the next :reload of the HC. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-224) Add allowed values for attribute "cache-type" in "/subsystem=security/security-domain=*"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-224?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-224: ---------------------------------- Fix Version/s: 8.0.1.Final (was: 8.0.0.CR1) (was: 8.0.0.Final) > Add allowed values for attribute "cache-type" in "/subsystem=security/security-domain=*" > ---------------------------------------------------------------------------------------- > > Key: WFLY-224 > URL: https://issues.jboss.org/browse/WFLY-224 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Affects Versions: 8.0.0.Alpha1 > Reporter: Harald Pehl > Priority: Minor > Fix For: 8.0.1.Final > > > The attribute "cache-type" in "/subsystem=security/security-domain=*" can either be "default" or "infinispan". Please add the allowed value to the resource description. > In order to generate the UI based on the management model, it is essential that information like this is present. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2820) Support for Properties File in wildfly-arquillian-container-managed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2820?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2820: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/5790 (was: https://github.com/wildfly/wildfly/pull/5787) > Support for Properties File in wildfly-arquillian-container-managed > ------------------------------------------------------------------- > > Key: WFLY-2820 > URL: https://issues.jboss.org/browse/WFLY-2820 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Ralf Battenfeld > Assignee: Ralf Battenfeld > Fix For: 8.0.0.Final > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Wildfly supports properties files set as a program argument. For managed arquillian test, this option is currently not supported in the arquillian.xml. If your app is using system properties, then arquillian can not be used as the manager of a wildfly instance. > I originally asked for this feature, and we need it:-) > I will send a PR soon that allows to set properties file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2820) Support for Properties File in wildfly-arquillian-container-managed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2820?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2820: ----------------------------------- Assignee: Ralf Battenfeld (was: Ondrej Zizka) > Support for Properties File in wildfly-arquillian-container-managed > ------------------------------------------------------------------- > > Key: WFLY-2820 > URL: https://issues.jboss.org/browse/WFLY-2820 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Ralf Battenfeld > Assignee: Ralf Battenfeld > Fix For: 8.0.0.Final > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > Wildfly supports properties files set as a program argument. For managed arquillian test, this option is currently not supported in the arquillian.xml. If your app is using system properties, then arquillian can not be used as the manager of a wildfly instance. > I originally asked for this feature, and we need it:-) > I will send a PR soon that allows to set properties file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 February 2014