December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5128) The management API should provide a command to restart only all servers that are in state 'reload-required'

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5128?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5128: ---------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > The management API should provide a command to restart only all servers that are in state 'reload-required' > ----------------------------------------------------------------------------------------------------------- > > Key: AS7-5128 > URL: https://issues.jboss.org/browse/AS7-5128 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Emanuel Muckenhuber > Labels: cli, domain, management > Fix For: 7.3.0.Alpha1 > > > After configuration changes via CLI batch it might be that different processes needs to be restarted. > It is possible to iterate over all servers and check it. > But I think it would be easier to have a command that restart all controllers and servers conditional to the 'relod required' state > - at domain level > - at host level > - at server level > command example : > :restart(ifRequired=true) > :reload(ifRequired=true) -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4999) Alllow non persistent configuration(runtime) changes for server groups and domain using CLI

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4999?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4999: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Alllow non persistent configuration(runtime) changes for server groups and domain using CLI > ------------------------------------------------------------------------------------------- > > Key: AS7-4999 > URL: https://issues.jboss.org/browse/AS7-4999 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Shay Matasaro > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > Using the CLI , It is currently not possible to make runtime config changes to multiple servers , unless you are using a roll-out plan > One example is the ability to disable a mod-cluster context on multiple servers at once. > Since this operation does not affect the persistent server config it is currently not supported. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5197) 128.3.1 WAB Definition

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-5197?page=com.atlassian.jira.plugin.s... ] Thomas Diesler reassigned AS7-5197: ----------------------------------- Assignee: Thomas Diesler (was: David Bosschaert) > 128.3.1 WAB Definition > ---------------------- > > Key: AS7-5197 > URL: https://issues.jboss.org/browse/AS7-5197 > Project: Application Server 7 > Issue Type: Sub-task > Components: OSGi > Reporter: David Bosschaert > Assignee: Thomas Diesler > Fix For: 7.2.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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5428) Server does wrongly reference a list of socket binding groups

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5428?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5428: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Server does wrongly reference a list of socket binding groups > ------------------------------------------------------------- > > Key: AS7-5428 > URL: https://issues.jboss.org/browse/AS7-5428 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 7.3.0.Alpha1 > > > hbraun: i see that a server (host=foo/server=bar) can have a list of socket-binding-groups > [10:59am] hbraun: shouldn't that be a a single socket binding instead? > [11:00am] emuckenhuber: oh... yeah > [11:00am] hbraun: maybe it's just the description that's wrong > [11:00am] emuckenhuber: that sounds similar to the jvm thing we had -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-1371) Domain Management - Support for database connection pool in non AS process.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-1371?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-1371: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.CR1) > Domain Management - Support for database connection pool in non AS process. > --------------------------------------------------------------------------- > > Key: AS7-1371 > URL: https://issues.jboss.org/browse/AS7-1371 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Flemming Harms > Fix For: 7.3.0.Alpha1 > > > We need to support authentication for users stored in database, the domain management is in a non-AS process so we also need a pool of database connections. > These connections will be used to read only from the database, other than the isolation offered by the driver we should not require any advanced transaction support. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4597) Slave host error handling in a managed domain should not assume the context failure description node can be converted to ModelType.OBJECT

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4597?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4597: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Slave host error handling in a managed domain should not assume the context failure description node can be converted to ModelType.OBJECT > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-4597 > URL: https://issues.jboss.org/browse/AS7-4597 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final > Reporter: Brian Stansberry > Assignee: Tom Fonteyne > Fix For: 7.3.0.Alpha1 > > > This failure was reported following a failed op: > Host Controller] 12:11:33,014 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 1) JBAS014612: Operation ("composite") failed - address: ([]): java.lang.IllegalArgumentException > [Host Controller] at org.jboss.dmr.ModelValue.getChild(ModelValue.java:108) [jboss-dmr-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1] > [Host Controller] at org.jboss.dmr.ModelNode.get(ModelNode.java:798) [jboss-dmr-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.DomainFinalResultHandler.collectHostFailures(DomainFinalResultHandler.java:158) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.DomainFinalResultHandler.execute(DomainFinalResultHandler.java:80) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.executeTwoPhaseOperation(OperationCoordinatorStepHandler.java:225) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.execute(OperationCoordinatorStepHandler.java:118) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:85) [jboss-as-host-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:309) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:299) [jboss-as-controller-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > [Host Controller] at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69) > [Host Controller] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > [Host Controller] at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710) > [Host Controller] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > [Host Controller] at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54) [jboss-as-domain-http-interface-7.1.0.Final-redhat-1.jar:7.1.0.Final-redhat-1] > [Host Controller] at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > [Host Controller] at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682) > [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0] > [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0] > [Host Controller] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0] > [Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-1.jar:2.0.0.GA-redhat-1] > The relevant logic at DomainFinalResultHandler.collectHostFailures(DomainFinalResultHandler.java:158) does this: > context.getFailureDescription().get(HOST_FAILURE_DESCRIPTIONS).set(hostFailureResults); > The IAE indicates the ModelNode returned by context.getFailureDescription() has already been initialized to some other ModelType (probably ModelType.STRING) and thus can't be used to store a failure description with a ModelType.OBJECT structure. > We need to figure out why the failure description was already initialized in order to decide how best to deal with this. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4699) Use OperationBuilder.addFileAsAttachment in the ServerDeploymentManager and DomainDeploymentManager impls

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4699?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4699: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Use OperationBuilder.addFileAsAttachment in the ServerDeploymentManager and DomainDeploymentManager impls > --------------------------------------------------------------------------------------------------------- > > Key: AS7-4699 > URL: https://issues.jboss.org/browse/AS7-4699 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > The ServerDeploymentManager and DomainDeploymentManager interfaces allow users to pass in a File. Currently we immediate convert that File to a FileInputStream and use that IS in the resulting operation. That will force an in-memory copy. Instead, use the OperationBuilder.addFileAsAttachment method introduced in the parent task. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4088) Add system properties for commonly parameterized mod_cluster configuration.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4088?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-4088: --------------------------------------- See spreadsheet attached to parent issue for my analysis of missing expression support across the AS, including the mod_cluster subsystem. We should correct the highlighted items by Jan 8 unless you disagree with some of them. > Add system properties for commonly parameterized mod_cluster configuration. > --------------------------------------------------------------------------- > > Key: AS7-4088 > URL: https://issues.jboss.org/browse/AS7-4088 > Project: Application Server 7 > Issue Type: Sub-task > Components: Clustering, Domain Management > Affects Versions: 7.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 7.2.0.Alpha1 > > > Add properties for: > jboss.mod_cluster.advertise.address > jboss.mod_cluster.advertise.port > jboss.mod_cluster.balancer > jboss.mod_cluster.load-balancing-group > jboss.mod_cluster.proxy-list -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-4541) Overall 'server-state' flag on the Host Controller

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4541?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4541: ---------------------------------- Fix Version/s: 7.3.0.Alpha1 (was: 7.2.0.Alpha1) > Overall 'server-state' flag on the Host Controller > -------------------------------------------------- > > Key: AS7-4541 > URL: https://issues.jboss.org/browse/AS7-4541 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.3.0.Alpha1 > > > This is for consideration; we need to see if it makes sense. > Request is for an attribute on the HC that indicates aggregate 'server-state'. The desire is to know when all servers are available, and thus it is safe to invoke management ops knowing all servers will receive them. > The only reason a server wouldn't receive an op is if it is started in a non-blocking mode, so the server gets its config but then hasn't connected with the HC and therefore won't get update operations. Starting the server in blocking mode will avoid this situation (as could changes to how we start servers, to make it more like how a slave HC registers with the master HC). So, before doing this let's first look at how to reduce/eliminate the use case for it. > Also to consider when looking at this is how to represent servers in things like "restart-required" state in this overall aggregate 'server-state'. -- 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

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-3772) Regularize expression handling in the interface resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3772?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3772: ---------------------------------- Parent: AS7-6120 Issue Type: Sub-task (was: Task) > Regularize expression handling in the interface resources > --------------------------------------------------------- > > Key: AS7-3772 > URL: https://issues.jboss.org/browse/AS7-3772 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Affects Versions: 7.1.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.2.0.Alpha1 > > > The interface resource code predates the evolution of the AttributeDefinition classes. Convert it over to that and make sure the xml parsers, operation step handlers and ParsedInterfaceCriteria follow the standard practices. Basically, > 1) Use AD.parseAndSet() in the parsers. This will ensure parsing any criteria type that supports expressions will result in values of type EXPRESSION if appropriate. > 2) Use AD.validateAndSet() in the MODEL stage of the OSH. This will ensure reading in input values from the CLI/console etc for any criteria type that supports expressions will result in values of type EXPRESSION if appropriate. > 3) Pass the OperationContext into ParsedInterfaceCriteria and use AD.resolveModelAttribute() for resolution. > 4) Get the calls to ModelNode.resolve() out of the InterfaceCriteria implementations. By the time those classes see a value it should already be resolved. > This may not be entirely possible, as interface criteria as a bit unusual types of attributes. But the general intent here should be followed. -- 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

13 years, 7 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 December 2012