September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5543) [7.1] Intermittent failure due to missing OSGi service

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5543: ----------------------------------- Summary: [7.1] Intermittent failure due to missing OSGi service Key: AS7-5543 URL: https://issues.jboss.org/browse/AS7-5543 Project: Application Server 7 Issue Type: Bug Components: OSGi, Server Reporter: Thomas Diesler Assignee: David Lloyd Priority: Critical Fix For: 7.2.0.Alpha1 For the first OSGi related deployments we intermittently see {code} Services with missing/unavailable dependencies" => ["jbosgi.integration.PersistentBundles.INSTALL Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.unit.\"webapp.war\".REGISTER {code} which is due to a race condition at subsystem startup. h4. Background At startup the framework goes through various phases # Framework.CREATE # Framework.INIT # Framework.ACTIVE During framework INIT persistent bundles (i.e. from a former run) are installed/started according to their persistent settings. In terms of services it means that the Framework.INIT service may depend on a number of Bundle.INSTALLED or Bundle.ACTIVE services. This however cannot be modelled as service dependencies because it must be possible to uninstall a persistent bundle (i.e. remove the Bundle.INSTALL) service without taking the framework down. Currently, we use a ServiceListener for the persistent Bundle services and install a PersistentBundles.COMPLETE service that Framework.INIT can actually depend on. There is currently no guarantee that the PersistentBundles.COMPLETE service gets installed (and as a consequence that the Framework.INIT starts up) before the OSGi deployment does its phase checking for missing services. AFAICS, there is currently no way to model this type of dependency properly without having this race condition. A possible solution may be a notion of DependencyType.WEAK. The semantic would be a required dependency that can go away once the target service has reached its target state (or has failed) h4. Example * serviceA depends on serviceB with DependencyType.WEAK * serviceA starts when serviceB has started * serviceA stays UP when serviceB gets removed -- 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

11 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-4746) DuplicateServiceException: Service jbosgi.integration.PersistentBundlesHandler is already registered

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4746: ----------------------------------- Summary: DuplicateServiceException: Service jbosgi.integration.PersistentBundlesHandler is already registered Key: AS7-4746 URL: https://issues.jboss.org/browse/AS7-4746 Project: Application Server 7 Issue Type: Bug Reporter: Thomas Diesler Fix For: 7.1.2.Final (EAP) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

4
15
0 / 0

[JBoss JIRA] (REMJMX-54) Release 1.1.0.Beta1

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-54: -------------------------------------- Summary: Release 1.1.0.Beta1 Key: REMJMX-54 URL: https://issues.jboss.org/browse/REMJMX-54 Project: Remoting JMX Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta1 -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-53) Release 1.0.5.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-53: -------------------------------------- Summary: Release 1.0.5.Final Key: REMJMX-53 URL: https://issues.jboss.org/browse/REMJMX-53 Project: Remoting JMX Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.5.Final -- 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

11 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5542) Upgrade to Remoting JMX 1.0.5.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5542: ------------------------------------- Summary: Upgrade to Remoting JMX 1.0.5.Final Key: AS7-5542 URL: https://issues.jboss.org/browse/AS7-5542 Project: Application Server 7 Issue Type: Task Components: JMX, Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.4.Final (EAP) -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-8) Connection state notification suppport

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-8?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated REMJMX-8: ---------------------------------- Fix Version/s: 1.1.0.CR1 (was: 1.1.0.Beta1) > Connection state notification suppport > -------------------------------------- > > Key: REMJMX-8 > URL: https://issues.jboss.org/browse/REMJMX-8 > Project: Remoting JMX > Issue Type: Task > Components: Connection, Notifications > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.CR1 > > -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-44) Allow a connection to be established where there is an existing Remoting Connection

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-44: -------------------------------------- Summary: Allow a connection to be established where there is an existing Remoting Connection Key: REMJMX-44 URL: https://issues.jboss.org/browse/REMJMX-44 Project: Remoting JMX Issue Type: Task Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 1.1.0.Beta1 This is closely related to REMJMX-43 - one motivation for that task is re-use of existing Remoting connections so Remoting JMX needs to be able to use the connection without interfering with it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
4
0 / 0

[JBoss JIRA] (REMJMX-43) Add support for an MBeanServer / MBeanServerConnection locator

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-43: -------------------------------------- Summary: Add support for an MBeanServer / MBeanServerConnection locator Key: REMJMX-43 URL: https://issues.jboss.org/browse/REMJMX-43 Project: Remoting JMX Issue Type: Task Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta1 The idea of adding a 'locator' is so that we can add a query string to the request URL and this can contain additional information to call out to a locator to find either the referenced MBeanServer or MBeanServerConnection. The Remoting JMX side of the implementation is just to add the locator API and to make use of it including the addition of support for query string. One place to consider using this is within AS7 where a connection will be made to the master domain controller and the query string will identify a process to manage - the locator will then either return the MBeanServer or MBeanServerConnection - the end result will be that the master process becomes a proxy to the other processes providing a shared entry point and shared connections to other processes to be managed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
4
0 / 0

[JBoss JIRA] (REMJMX-12) Allow for protocol versions to be excluded client and server side

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-12?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved REMJMX-12. ------------------------------------ Resolution: Done > Allow for protocol versions to be excluded client and server side > ----------------------------------------------------------------- > > Key: REMJMX-12 > URL: https://issues.jboss.org/browse/REMJMX-12 > Project: Remoting JMX > Issue Type: Task > Components: Connection > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta1 > > > Once we start supporting multiple versions of the protocols we should also allow version to be excluded client and server side. > This will mean if a version is identified as being problematic is can be excluded to force the use of a previous version. -- 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

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-50) Client must eliminate unsupported versions from the list.

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-50: -------------------------------------- Summary: Client must eliminate unsupported versions from the list. Key: REMJMX-50 URL: https://issues.jboss.org/browse/REMJMX-50 Project: Remoting JMX Issue Type: Bug Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 1.0.5.CR1 At the moment the client just iterates to find the highest version - however unsupported versions should have been dropped from the list (so should banned versions) This means when we add version 0x02 existing clients break. Need to find a way to add the versions without breaking the existing clients. One option may be to add version 0x00 existing clients will not use this as 0x01 is higher - if a client selects 0x00 then begin negotiating the version again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2012