July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1430) Create clustering subsystem

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1430?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on WFLY-1430: ------------------------------------------- An update on progress. I have now done the following: - implemented resource /subsystem=cluster/name=<channel> - implemented resource /subsystem=cluster/name=<channel>/deployment=<deployment-name> - removed any use of the management interface ; channel and cache information is obtained directly from services The interface is limited at present to a couple of attributes, but it looks like this: {noformat} [standalone@127.0.0.1:10090 /] /subsystem=cluster/name=web:read-attribute(name=view) { "outcome" => "success", "result" => [ ("lenovo/web" => "[fred/web|3] [fred/web, lenovo/web]"), ("fred/web" => "[fred/web|3] [fred/web, lenovo/web]") ] } [standalone@127.0.0.1:10090 /] /subsystem=cluster/name=web/deployment=default-host\/distributable:read-attribute(name=cache-view) { "outcome" => "success", "result" => [ ("lenovo/web" => "[fred/web, lenovo/web]"), ("fred/web" => "[fred/web, lenovo/web]") ] } {noformat} This interface will be added to and improved over time. I had a bit of trouble ensuring that the RPC mechanism which is used by the interface: - gets installed without introducing circular dependencies with other modules (i.e. Infinispan) - gets started on all nodes whenever a channel gets started What I did was this: - reworked the installation of the RPC mechanism ManagementAPIClusterSupport as a ChannelDependentServiceProvider, which allows it to be installed by the Infinispan subsystem's CacheContainerAdd method, without introducing a circular dependeency - defined a dummy service ManagementAPIClusterSupportTrigger which is dependent on ChannelService and started in PASSIVE mode, so that whenever a channel starts, it starts. This dummy service is what starts the ManagementAPICLusterSupport service on each node. The PR I have listed above still needs cleaning up, but it incorporates what is described above. > Create clustering subsystem > --------------------------- > > Key: WFLY-1430 > URL: https://issues.jboss.org/browse/WFLY-1430 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 8.0.0.Alpha2 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > > Create a clustering subsystem which collects together clustering-related functionality as described in WFLY-1236. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1329) 'whoami' operation unexpectedly requires the domain wide configuration lock

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1329?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1329: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 960497|https://bugzilla.redhat.com/show_bug.cgi?id=960497] from MODIFIED to ON_QA > 'whoami' operation unexpectedly requires the domain wide configuration lock > --------------------------------------------------------------------------- > > Key: WFLY-1329 > URL: https://issues.jboss.org/browse/WFLY-1329 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Environment: 7.2.0.Final (EAP 6.1.0.Beta1) > Reporter: Osamu Nagano > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.Alpha2 > > Attachments: slowdeployweb.war > > > 'whoami' operation in domain mode seems to require the domain wide configuration lock. This is problematic when there is an editing operation of domain.xml like a long running undeployment because all 'whoami' requests are blocked by the existing task. The number of blocked thread increases indefinitely and it will cause an OutOfMemoryError. > It doesn't happen in standalone mode. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1439) ServerSetupObserver leaks changes if exception is thrown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1439?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1439: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 969346|https://bugzilla.redhat.com/show_bug.cgi?id=969346] from MODIFIED to ON_QA > ServerSetupObserver leaks changes if exception is thrown > -------------------------------------------------------- > > Key: WFLY-1439 > URL: https://issues.jboss.org/browse/WFLY-1439 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.0.0.Alpha2 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Labels: testsuite > Fix For: 8.0.0.Alpha2 > > > If class used as @ServerSetup throws exception from callback, ServerSetupObserver purges all tasks that already have been executed. This means that all changes that have been introduced to AS model will remain( iirc persisted as part of config used my arquillian). > Hence other tests may fail due to that. > Ive talked with Stuart and according to his statement @ServerSetup class must not throw exception from callbacks. > ServerSetupObserver should cleanup in a more graceful manner. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-256) Remove direct connections parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-256?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-256: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 908720|https://bugzilla.redhat.com/show_bug.cgi?id=908720] from MODIFIED to ON_QA > Remove direct connections parameter > ----------------------------------- > > Key: WFLY-256 > URL: https://issues.jboss.org/browse/WFLY-256 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Labels: console_1.5.3, merged > Fix For: 8.0.0.Alpha2 > > > The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) > One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-14) Remove deprecated attributes of messaging subsystem in console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-14?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-14: --------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 948900|https://bugzilla.redhat.com/show_bug.cgi?id=948900] from MODIFIED to ON_QA > Remove deprecated attributes of messaging subsystem in console > -------------------------------------------------------------- > > Key: WFLY-14 > URL: https://issues.jboss.org/browse/WFLY-14 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Minor > Labels: console_1.5.3, merged > Fix For: 8.0.0.CR1 > > > The attribute {{failover-on-server-shutdown}} in > * {{/subsystem=messaging/hornetq-server=default/connection-factory=*}} and > * {{/subsystem=messaging/hornetq-server=default/bridge=*}} > is deprecated and should be removed from the UI. The relevant classes in the UI are > * {{org.jboss.as.console.client.shared.subsys.messaging.model.ConnectionFactory}} > * {{org.jboss.as.console.client.shared.subsys.messaging.model.Bridge}} -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-1324) Add testing for slave Host Controller join to domain testsuite DefaultConfigSmokeTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1324?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1324: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 961523|https://bugzilla.redhat.com/show_bug.cgi?id=961523] from MODIFIED to ON_QA > Add testing for slave Host Controller join to domain testsuite DefaultConfigSmokeTestCase > ----------------------------------------------------------------------------------------- > > Key: WFLY-1324 > URL: https://issues.jboss.org/browse/WFLY-1324 > Project: WildFly > Issue Type: Task > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > DefaultConfigSmokeTestCase tests the "domain.xml + host.xml" config set, so a master running servers is tested. But "domain.xml + host-master.xml" is not tested nor is "host-slave.xml". These latter two can be tested in combination, and that closes the whole where we aren't testing a slave joining a domain configured to use our default configs. -- 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

1
0
0 / 0

[JBoss JIRA] (AS7-6759) Console should react properly to loss of connection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6759?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6759: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 910718|https://bugzilla.redhat.com/show_bug.cgi?id=910718] from MODIFIED to ON_QA > Console should react properly to loss of connection > --------------------------------------------------- > > Key: AS7-6759 > URL: https://issues.jboss.org/browse/AS7-6759 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Labels: console_1.5.3, merged > > Codesplit error handling leads to freeze -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-14) Remove deprecated attributes of messaging subsystem in console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-14?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-14: --------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 908664|https://bugzilla.redhat.com/show_bug.cgi?id=908664] from MODIFIED to ON_QA > Remove deprecated attributes of messaging subsystem in console > -------------------------------------------------------------- > > Key: WFLY-14 > URL: https://issues.jboss.org/browse/WFLY-14 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Minor > Labels: console_1.5.3, merged > Fix For: 8.0.0.CR1 > > > The attribute {{failover-on-server-shutdown}} in > * {{/subsystem=messaging/hornetq-server=default/connection-factory=*}} and > * {{/subsystem=messaging/hornetq-server=default/bridge=*}} > is deprecated and should be removed from the UI. The relevant classes in the UI are > * {{org.jboss.as.console.client.shared.subsys.messaging.model.ConnectionFactory}} > * {{org.jboss.as.console.client.shared.subsys.messaging.model.Bridge}} -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-65) EjbUtilities is used without regard for dependencies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-65?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration commented on WFLY-65: --------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 950864|https://bugzilla.redhat.com/show_bug.cgi?id=950864] from MODIFIED to ON_QA > EjbUtilities is used without regard for dependencies > ---------------------------------------------------- > > Key: WFLY-65 > URL: https://issues.jboss.org/browse/WFLY-65 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > > org.jboss.as.ejb3.component.EJBUtilities is used to get services in the EJB subsystem, without setting up proper dependencies (e.g. in org.jboss.as.ejb3.component.EJBComponentCreateService#getEJBUtilities). Occasionally this can cause problems at startup as EJBUtilities can end up being null for some EJB's. > We should probably just remove this class, or at the very least make sure it is injected properly and not looked up. -- 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

1
0
0 / 0

[JBoss JIRA] (WFLY-336) Wrong value of "runtime-name" property for unmanaged deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-336?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-336: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 910675|https://bugzilla.redhat.com/show_bug.cgi?id=910675] from MODIFIED to ON_QA > Wrong value of "runtime-name" property for unmanaged deployments > ----------------------------------------------------------------- > > Key: WFLY-336 > URL: https://issues.jboss.org/browse/WFLY-336 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, console_1.5.3, merged > Fix For: 8.0.0.Alpha2 > > -- 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

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 July 2013