December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment

by Philippe Marschall (JIRA)

[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ] Philippe Marschall commented on AS7-5584: ----------------------------------------- Guy, You need the latest 7.x (actually 7.2) builds from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/ the patch hasn't been merged into the 7.0 line. > Naming context read-only during SAR deployment > ---------------------------------------------- > > Key: AS7-5584 > URL: https://issues.jboss.org/browse/AS7-5584 > Project: Application Server 7 > Issue Type: Bug > Components: POJO > Affects Versions: 7.1.1.Final > Reporter: Philippe Marschall > Assignee: Philippe Marschall > Fix For: 7.2.0.Alpha1 > > > During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that {{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}} > http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi... -- 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-6134) Problem reassigning server to different group

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6134?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6134: ---------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > Problem reassigning server to different group > --------------------------------------------- > > Key: AS7-6134 > URL: https://issues.jboss.org/browse/AS7-6134 > Project: Application Server 7 > Issue Type: Feature Request > 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

13 years, 7 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: ---------------------------------- Assignee: (was: Brian Stansberry) > 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: 7.3.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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-5763) timeout handling waiting for future

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5763?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5763: ---------------------------------- Fix Version/s: 7.2.0.CR1 > timeout handling waiting for future > ----------------------------------- > > Key: AS7-5763 > URL: https://issues.jboss.org/browse/AS7-5763 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Alexey Loubyansky > Assignee: Brian Stansberry > Fix For: 7.2.0.CR1 > > > The issue was reported in AS7-5350 which points to a CLI testcase that fails on windows. > The test starts a CLI process and deliberately specifies a wrong port for the controller expecting a failure during connection. The CLI sends a read-attribute operation request on connect to make sure the connection is working. The test is waiting for a response from the controller for 10 sec and then times out. The time out of the ModelControllerClient is 5 sec. The test still fails after 10 sec time out but the error output stream of the CLI process does contain the stack trace of the expected exception, i.e. that the controller was not available at the specified address. > When the testcase times out, it destroys the CLI process, perhaps, this triggers some actions and the exception is finally thrown and the stack trace gets logged but it's too late. -- 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: ---------------------------------- Assignee: (was: Brian Stansberry) > 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: 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-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: ---------------------------------- Assignee: (was: Brian Stansberry) > 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: 7.3.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, 7 months

1
0
0 / 0

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-4088?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-4088: ------------------------------------- So, all in all according to Brian's spreadsheet we won’t be allowing expressions for 'advertise-socket' and 'connector', as for load metric, 'type' won't either. This is reasonable since there is not much use case in changing these with expressions per host or so. Otherwise everything will be allowing for expressions. > 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: Radoslav Husar > 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] (JBJCA-917) @ConfigProperty annotation does not hand the superclass's value over to the subclass

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-917?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated JBJCA-917: ---------------------------------- Component/s: Common (was: Deployer) > @ConfigProperty annotation does not hand the superclass's value over to the subclass > ------------------------------------------------------------------------------------ > > Key: JBJCA-917 > URL: https://issues.jboss.org/browse/JBJCA-917 > Project: IronJacamar > Issue Type: Bug > Components: Common > Affects Versions: 1.0.13.Final, 1.1.0.Beta2 > Reporter: Vladimir Rastseluev > Assignee: Jesper Pedersen > Fix For: 1.0.14.Final, 1.1.0.Beta4 > > > See @Ignored test in case: > org.jboss.jca.test.deployers.spec.rars.testcases.Ra16inoutijmultiannoTestCase -- 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] (JBJCA-917) @ConfigProperty annotation does not hand the superclass's value over to the subclass

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-917?page=com.atlassian.jira.plugin.... ] Jesper Pedersen resolved JBJCA-917. ----------------------------------- Resolution: Done > @ConfigProperty annotation does not hand the superclass's value over to the subclass > ------------------------------------------------------------------------------------ > > Key: JBJCA-917 > URL: https://issues.jboss.org/browse/JBJCA-917 > Project: IronJacamar > Issue Type: Bug > Components: Common > Affects Versions: 1.0.13.Final, 1.1.0.Beta2 > Reporter: Vladimir Rastseluev > Assignee: Jesper Pedersen > Fix For: 1.0.14.Final, 1.1.0.Beta4 > > > See @Ignored test in case: > org.jboss.jca.test.deployers.spec.rars.testcases.Ra16inoutijmultiannoTestCase -- 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-6147) Compatibility check of runtime model versions

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-6147?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved AS7-6147. ------------------------------ Resolution: Done the console ships a compat file, indicating the version that have been used at the time it was released. The file is used to compare the model version at runtime against the ones that have been used at build time. (See Runtime > Overview > Extensions) > Compatibility check of runtime model versions > --------------------------------------------- > > Key: AS7-6147 > URL: https://issues.jboss.org/browse/AS7-6147 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 7.2.0.CR1 > > > Nail down the model version that have been used when the console was released (core & subsystem versions) and compare to runtime versions during bootstrap. -- 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