March 2013 - jboss-jira - Jboss List Archives

[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: 8.0.0.Alpha1 (was: 7.3.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: 8.0.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, 3 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: 8.0.0.Alpha1 (was: 7.3.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: 8.0.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, 3 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: 8.0.0.Alpha1 (was: 7.3.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: 8.0.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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2967) Remove workaround for shutting down the ModelControllerClientOperationHandlers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-2967?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2967: ---------------------------------- Fix Version/s: (was: 7.3.0.Alpha1) > Remove workaround for shutting down the ModelControllerClientOperationHandlers > ------------------------------------------------------------------------------ > > Key: AS7-2967 > URL: https://issues.jboss.org/browse/AS7-2967 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Affects Versions: 7.1.0.CR1 > Reporter: Emanuel Muckenhuber > > Once the graceful shutdown API is in place we need to cleanup the way the ModelControllerClientOperationHandler channels are closed. Currently we are waiting for all current operations to complete, in order that the response for :reload / :shutdown operations are sent. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3463) Provide Unit for JVM configuration elements

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3463?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3463: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Provide Unit for JVM configuration elements > ------------------------------------------- > > Key: AS7-3463 > URL: https://issues.jboss.org/browse/AS7-3463 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Fix For: 8.0.0.Alpha1 > > > Like with any other config element, units for the JVM parameters would be nice. > I.e. instead of encoding it into the string value ("64m") it would be better to split the actual value from unit (value=64, unit=<kb|mb|gb>). See the thread subsystem for a reference how this is done in other places -- 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, 3 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5772?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5772: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > ServerInventory#reconnectServer should take auto-start into account > ------------------------------------------------------------------- > > Key: AS7-5772 > URL: https://issues.jboss.org/browse/AS7-5772 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha1 > > > 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3611) Find better solution to AS7-2815 than using EnumValidator to store the allowed value

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3611?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3611: ---------------------------------- Fix Version/s: (was: 7.3.0.Alpha1) > Find better solution to AS7-2815 than using EnumValidator to store the allowed value > ------------------------------------------------------------------------------------ > > Key: AS7-3611 > URL: https://issues.jboss.org/browse/AS7-3611 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > > AS7-2815 solution uses a hack in EnumValidator to store the allowed value instead of the user provided value. That goes beyond the contract of a "validate" method. See if something better can be found. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-762) Provide an operation to request service status report after server has been started

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-762?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-762: --------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Provide an operation to request service status report after server has been started > ------------------------------------------------------------------------------------- > > Key: AS7-762 > URL: https://issues.jboss.org/browse/AS7-762 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Labels: console_prio > Fix For: 8.0.0.Alpha1 > > > For proper healthcare it would beneficial if I could verify the server status after it has been started. I.e. to catch these, which currently only appear in the server log: > [Server:server-three] 17:48:26,636 INFO [org.jboss.as.server] (MSC service thread 1-2) Service status report > [Server:server-three] New missing/unsatisfied dependencies: > [Server:server-three] service jboss.binding.http2 (missing) > [Server:server-three] > [Server:server-three] 17:48:26,636 ERROR [org.jboss.as] (MSC service thread 1-4) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 3893ms - Started 101 of 149 services (1 services failed or missing dependencies, 47 services are passive or on-demand) -- 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, 3 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: 8.0.0.Alpha1 (was: 7.3.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 > Fix For: 8.0.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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5580) Introduce "version" to all operations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5580?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5580: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Introduce "version" to all operations > ------------------------------------- > > Key: AS7-5580 > URL: https://issues.jboss.org/browse/AS7-5580 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI, Console, Domain Management > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.0.0.Alpha1 > > > To better support backward compatibility for upcoming version of AS/mgmt api > For start we should probably just send mgmt version of subsystem/core > in future we could use this info to route operations properly -- 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, 3 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 2013