December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6201) Deprecate org.jboss.as.controller.operations.global.WriteAttributeHandlers

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6201: ------------------------------------- Summary: Deprecate org.jboss.as.controller.operations.global.WriteAttributeHandlers Key: AS7-6201 URL: https://issues.jboss.org/browse/AS7-6201 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.1.3.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 Resources should use AbstractWriteAttributeHandler or a custom handler. -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6191) SimpleAttributeDefinition spams the logs with deprecation messages

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6191?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6191: ---------------------------------- Priority: Critical (was: Major) Assignee: (was: Brian Stansberry) I marked this as Critical mostly so it doesn't get dropped from 7.2. It's an easy fix so there's no reason not to get it in. > SimpleAttributeDefinition spams the logs with deprecation messages > ------------------------------------------------------------------ > > Key: AS7-6191 > URL: https://issues.jboss.org/browse/AS7-6191 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Priority: Critical > Fix For: 7.2.0.Alpha1 > > > If an attribute is deprecated, SAD writes INFO messages in the log in both parse and the marshallAs methods. The superclass does it in validateAndSet. The superclass is sufficient. -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6200) CLONE - Add 'silent' mode to CommandContext API

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-6200?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky moved JBPAPP6-1734 to AS7-6200: ------------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform 6) Key: AS7-6200 (was: JBPAPP6-1734) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP 6.1.0) Component/s: CLI (was: Consoles) Security: (was: Public) Fix Version/s: (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - Add 'silent' mode to CommandContext API > ----------------------------------------------- > > Key: AS7-6200 > URL: https://issues.jboss.org/browse/AS7-6200 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI > Reporter: Thomas Hauser > Assignee: Alexey Loubyansky > Priority: Minor > > It would be nice to have the option of running in 'silent' mode when using the CommandContext. By 'silent' I mean no output to standard output; instead, the entity calling the CommandContext would be responsible for reporting on errors and the like. -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6168) component upgrade to Hibernate 4.1.9.Final

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6168?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6168: ----------------------------------- The Hibernate issue that reports this regression is HHH-7871 (which appears to be caused by optimizations in HHH-7640). > component upgrade to Hibernate 4.1.9.Final > ------------------------------------------ > > Key: AS7-6168 > URL: https://issues.jboss.org/browse/AS7-6168 > Project: Application Server 7 > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6134) Problem reassigning server to different group

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Emanuel Muckenhuber commented on AS7-6134: ------------------------------------------ Ok, on the slave it fails for me as well. > Problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6134) Problem reassigning server to different group

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Heiko Braun edited comment on AS7-6134 at 12/17/12 9:46 AM: ------------------------------------------------------------ Maybe this one: {noformat} [Host Controller] 15:43:13,026 TRACE [org.jboss.as.host.controller] (HttpManagementService-threads - 6) coordinator succeeded: undefined {noformat} Further down it reads {noformat} "domain-results" => {"step-1" => {"outcome" => undefined}}, {noformat} Finally {noformat} "rollback-across-groups" => true {noformat} was (Author: heiko.braun): Maybe this one: {noformat} [Host Controller] 15:43:13,026 TRACE [org.jboss.as.host.controller] (HttpManagementService-threads - 6) coordinator succeeded: undefined {noformat} Further down it reads {noformat} "domain-results" => {"step-1" => {"outcome" => undefined}}, {noformat} > Problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6134) Problem reassigning server to different group

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Heiko Braun edited comment on AS7-6134 at 12/17/12 9:47 AM: ------------------------------------------------------------ Maybe this one: {noformat} [Host Controller] coordinator succeeded: undefined {noformat} Further down it reads {noformat} "domain-results" => {"step-1" => {"outcome" => undefined}}, {noformat} Finally {noformat} "rollback-across-groups" => true {noformat} was (Author: heiko.braun): Maybe this one: {noformat} [Host Controller] 15:43:13,026 TRACE [org.jboss.as.host.controller] (HttpManagementService-threads - 6) coordinator succeeded: undefined {noformat} Further down it reads {noformat} "domain-results" => {"step-1" => {"outcome" => undefined}}, {noformat} Finally {noformat} "rollback-across-groups" => true {noformat} > Problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6134) Problem reassigning server to different group

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-6134: ---------------------------------- Maybe this one: {noformat} [Host Controller] 15:43:13,026 TRACE [org.jboss.as.host.controller] (HttpManagementService-threads - 6) coordinator succeeded: undefined {noformat} Further down it reads {noformat} "domain-results" => {"step-1" => {"outcome" => undefined}}, {noformat} > Problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6134) Problem reassigning server to different group

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-6134: ---------------------------------- Still the same thing on rev 5da44e020b1d1e9de1b74b116a902bb2bf173283 {noformat} [Host Controller] 15:43:13,026 TRACE [org.jboss.as.host.controller] (HttpManagementService-threads - 6) 1st phase result from host slave is { [Host Controller] "outcome" => undefined, [Host Controller] "result" => { [Host Controller] "domain-results" => {"step-1" => {"outcome" => undefined}}, [Host Controller] "server-operations" => [{ [Host Controller] "servers" => [("stage1" => "other-server-group")], [Host Controller] "operation" => {"step-1" => { [Host Controller] "operation" => "server-set-restart-required", [Host Controller] "address" => [] [Host Controller] }} [Host Controller] }] [Host Controller] } [Host Controller] } [Host Controller] 15:43:13,026 TRACE [org.xnio.channels.framed] (Remoting "radio-86rk.fritz.box:MANAGEMENT" task-2) Fully flushed org.xnio.channels.FramedMessageChannel around TCP socket channel (NIO) <4328ea3f> [Host Controller] 15:43:13,026 TRACE [org.jboss.remoting.remote.connection] (Remoting "radio-86rk.fritz.box:MANAGEMENT" task-2) Flushed channel (direct) [Host Controller] 15:43:13,026 TRACE [org.jboss.as.host.controller] (HttpManagementService-threads - 6) Rollout plan is { [Host Controller] "in-series" => [{"concurrent-groups" => [("other-server-group" => { [Host Controller] "rolling-to-servers" => false, [Host Controller] "max-failed-servers" => 0 [Host Controller] })]}], [Host Controller] "rollback-across-groups" => true [Host Controller] } {noformat} > Problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1 > > > I cannot reassign a (stopped) server to a different group if the domain has two members -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-5170) Display subsystem information that relates to deployments

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-5170?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-5170. ------------------------------ Resolution: Done > Display subsystem information that relates to deployments > ----------------------------------------------------------- > > Key: AS7-5170 > URL: https://issues.jboss.org/browse/AS7-5170 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Jeff Mesnil > Assignee: Harald Pehl > Fix For: 7.2.0.CR1 > > Attachments: deployments.png > > > Each deployment provides subsystem relevant informations (ejb3, jpa, web, webservices). The deployment view is rebuilt to reflect this structure. Therefore a new "miller columns" widget is introduced. Each column is bound to a subdeployment / subsystem and a context aware detail view. The attached mind map shows the structure and scope of the different columns and context views. > The [GWT CellBrowser sample|http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellBrowser] shows how the miller columns could look like. -- 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

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 December 2012