March 2013 - jboss-jira - Jboss List Archives

[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 commented on AS7-5580: --------------------------------------- We'd better get started on this one. > 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

[JBoss JIRA] (AS7-6138) "Cast" model nodes in AttributeDefinition validateOperation()

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6138?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6138: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > "Cast" model nodes in AttributeDefinition validateOperation() > ------------------------------------------------------------- > > Key: AS7-6138 > URL: https://issues.jboss.org/browse/AS7-6138 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Affects Versions: 7.1.3.Final (EAP) > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > If the ModelType of a node in an operation does not match the defined type for the model, but is properly convertible, convert it so we store the expected type in the model. > For example, if someone passed in ModelType.LONG or ModelType.BIG_INTEGER but the model stores INT, store an INT. > This can be done after the validator for the AD has been invoked. The validator will have ensured that the "cast" is correct. -- 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-5472) unavailable datasource statistics

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5472?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5472: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > unavailable datasource statistics > --------------------------------- > > Key: AS7-5472 > URL: https://issues.jboss.org/browse/AS7-5472 > Project: Application Server 7 > Issue Type: Bug > Components: JCA, JMX > Affects Versions: 7.1.2.Final (EAP) > Reporter: Mathieu Lachance > Assignee: Brian Stansberry > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > In the java visual vm, in the mbean tab, under the "jboss.as:subsystem=datasources,data-source=MyDataSource" mbean, attribute "statistics" is marked as "Unavailable" > When using the spy="true" attribute in the datasource subsystem in conjunction with the "org.jboss.jca" logger set as TRACE level in the logging subsystem, statistics are outputted as follow : > Statistics: > ActiveCount: 1 > AvailableCount: 99 > AverageBlockingTime: 0 > AverageCreationTime: 248 > CreatedCount: 1 > DestroyedCount: 0 > MaxCreationTime: 248 > MaxUsedCount: 1 > MaxWaitCount: 0 > MaxWaitTime: 0 > TimedOut: 0 > TotalBlockingTime: 0 > TotalCreationTime: 248 > I would except to find those statistics available through separates jmx attributes when using the spy="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, 3 months

1
0
0 / 0

[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: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > 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: 8.0.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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5573) Track "uncleanly unregistered" hosts on the master HC; expose via management API

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5573?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5573: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Track "uncleanly unregistered" hosts on the master HC; expose via management API > -------------------------------------------------------------------------------- > > Key: AS7-5573 > URL: https://issues.jboss.org/browse/AS7-5573 > Project: Application Server 7 > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > When the master HC detects that a slave HC is no longer available but hasn't properly unregistered, the slave should still be visible in the management API but with some sort of status indicator. > The slave should probably not remaining in the regular management tree, since that will encourage clients to invoke operations that will just fail, but it's existence and "unknown" status should be reflected in some manner accessible to management clients who wish to obtain a more complete view of the domain topology. -- 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-6126) Check ModelTypes in jacorb subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6126?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6126: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Check ModelTypes in jacorb subsystem > ------------------------------------ > > Key: AS7-6126 > URL: https://issues.jboss.org/browse/AS7-6126 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management, IIOP > Affects Versions: 7.1.3.Final (EAP) > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > There are a number of attributes in the Jacorb subsystem that use ModelType.STRING for things that look like booleans. Check through the attributes and change to ModelType.BOOLEAN where appropriate. > This shouldn't raise a compatibility issue, since ModelType.BOOLEAN is freely convertible to ModelType.STRING, and vice-versa so long as the string represents as boolean (which it would have to do for the attribute to work anyway.) If anything is changed though, a Console subtask should be created to look into any UI implications. -- 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-5935) Add support for cross-site replication of Infinispan caches via RELAY2

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5935?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5935: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Add support for cross-site replication of Infinispan caches via RELAY2 > ---------------------------------------------------------------------- > > Key: AS7-5935 > URL: https://issues.jboss.org/browse/AS7-5935 > Project: Application Server 7 > Issue Type: Feature Request > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha1 > > > Proposed AS7 configuration of $SUBJECT was discussed in Palma clustering meeting. > https://community.jboss.org/wiki/DesignForCrossSiteReplication > https://docs.jboss.org/author/display/ISPN/Cross+site+replication -- 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-6205) Remove WriteAttributeHandlers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6205?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6205: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Remove WriteAttributeHandlers > ----------------------------- > > Key: AS7-6205 > URL: https://issues.jboss.org/browse/AS7-6205 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Parent task deprecates in 7.2; this task is to remove. -- 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-6203) WebSSLDefinition NAME attribute is read-write

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6203?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6203: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > WebSSLDefinition NAME attribute is read-write > --------------------------------------------- > > Key: AS7-6203 > URL: https://issues.jboss.org/browse/AS7-6203 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Brian Stansberry > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > WebSSLDefinition has a read-write attribute NAME that AFAICT merely stores the name of an xml element. If the attribute represents part of a resource address it should be read-only. If it's just some cruft (which appears to be the case), it should be deprecated and removed in some later release. -- 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-5047) Allow more control over authentication for server to server communication through remote-outbound-connection

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5047?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5047: ---------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.3.0.Alpha1) > Allow more control over authentication for server to server communication through remote-outbound-connection > ------------------------------------------------------------------------------------------------------------ > > Key: AS7-5047 > URL: https://issues.jboss.org/browse/AS7-5047 > Project: Application Server 7 > Issue Type: Sub-task > Components: Remoting, Security > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP) > Reporter: jaikiran pai > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > > Right now for server to server communication via a remote-outbound-connection, we expect a static username to be specified (along with the security realm). User applications which use this remote-outbound-connection, for example an EJB application, do not have much control over the user/pass information, since the username is static. This further acts a drawback since the username that's used to connect to the remote server will be used as the (application) user who invoked the EJB. > It would be good to allow more control over the authentication for the remote-outbound-connection. -- 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