jboss-osgi-issues May 2012

jboss-osgi-issues@lists.jboss.org

1 participants
45 discussions

[JBoss JIRA] (JBOSGI-556) OSGi subsystem does not call BundleActivator

by Rico Neubauer (JIRA)

Rico Neubauer created JBOSGI-556: ------------------------------------ Summary: OSGi subsystem does not call BundleActivator Key: JBOSGI-556 URL: https://issues.jboss.org/browse/JBOSGI-556 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.3.0 Reporter: Rico Neubauer Assignee: Thomas Diesler Attachments: SimpleOSGi_1.0.0.201205181614.jar Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final OSGi activators do not get called after bundle starts. Instead nothing happens. Test bundle attached, but happens with any activator bundle. -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] (JBOSGI-553) Start Level change does not report intermediate levels

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-553?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-553. ----------------------------------- Fix Version/s: JBossOSGi 1.2.0 Resolution: Done Fixed in jbosgi-framework-1.3.1.CR2 > Start Level change does not report intermediate levels > ------------------------------------------------------ > > Key: JBOSGI-553 > URL: https://issues.jboss.org/browse/JBOSGI-553 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: David Bosschaert > Assignee: Thomas Diesler > Fix For: JBossOSGi 1.2.0 > > > When changing the OSGi start level using the management API, the framework doesn't appear to go through the intermediate start levels. > When the following command is issued from the console: > {code}/subsystem=osgi:write-attribute(name=startlevel,value=3){code} > it seems like start level 2 is skipped in the framework from looking at the log: > {noformat}16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011007: Increasing start level from 1 to 3 > 16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011011: Starting bundles for start level: 3 > 16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011011: Starting bundles for start level: 3 > 16:13:33,333 INFO [system.bundle] (Thread-80) FrameworkEvent STARTLEVEL CHANGED{noformat} > The same happens when moving down in start level. > I haven't checked whether this is only a reporting issue or whether the intermediate start level are really skipped. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-553) Start Level change does not report intermediate levels

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-553?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-553: ---------------------------------- Summary: Start Level change does not report intermediate levels (was: OSGi Start Level change doesn't iterate through intermediate levels) > Start Level change does not report intermediate levels > ------------------------------------------------------ > > Key: JBOSGI-553 > URL: https://issues.jboss.org/browse/JBOSGI-553 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: David Bosschaert > Assignee: Thomas Diesler > > When changing the OSGi start level using the management API, the framework doesn't appear to go through the intermediate start levels. > When the following command is issued from the console: > {code}/subsystem=osgi:write-attribute(name=startlevel,value=3){code} > it seems like start level 2 is skipped in the framework from looking at the log: > {noformat}16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011007: Increasing start level from 1 to 3 > 16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011011: Starting bundles for start level: 3 > 16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011011: Starting bundles for start level: 3 > 16:13:33,333 INFO [system.bundle] (Thread-80) FrameworkEvent STARTLEVEL CHANGED{noformat} > The same happens when moving down in start level. > I haven't checked whether this is only a reporting issue or whether the intermediate start level are really skipped. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-553) OSGi Start Level change doesn't iterate through intermediate levels

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-553?page=com.atlassian.jira.plugin... ] Thomas Diesler moved AS7-4820 to JBOSGI-553: -------------------------------------------- Project: JBoss OSGi (was: Application Server 7) Key: JBOSGI-553 (was: AS7-4820) Workflow: jira (was: GIT Pull Request workflow ) Affects Version/s: (was: 7.1.2.Final (EAP)) Component/s: Core Framework (was: OSGi) Security: Public > OSGi Start Level change doesn't iterate through intermediate levels > ------------------------------------------------------------------- > > Key: JBOSGI-553 > URL: https://issues.jboss.org/browse/JBOSGI-553 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: David Bosschaert > Assignee: Thomas Diesler > > When changing the OSGi start level using the management API, the framework doesn't appear to go through the intermediate start levels. > When the following command is issued from the console: > {code}/subsystem=osgi:write-attribute(name=startlevel,value=3){code} > it seems like start level 2 is skipped in the framework from looking at the log: > {noformat}16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011007: Increasing start level from 1 to 3 > 16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011011: Starting bundles for start level: 3 > 16:13:33,332 INFO [org.jboss.osgi.framework] (OSGi StartLevel Thread) > JBOSGI011011: Starting bundles for start level: 3 > 16:13:33,333 INFO [system.bundle] (Thread-80) FrameworkEvent STARTLEVEL CHANGED{noformat} > The same happens when moving down in start level. > I haven't checked whether this is only a reporting issue or whether the intermediate start level are really skipped. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-548) ConfigurationAdminMBean registered twice

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-548: ------------------------------------- Summary: ConfigurationAdminMBean registered twice Key: JBOSGI-548 URL: https://issues.jboss.org/browse/JBOSGI-548 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Reporter: Thomas Diesler Assignee: Thomas Diesler https://issues.apache.org/jira/browse/ARIES-663 -- 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

13 years, 6 months

1
1
0 / 0

← Newer
1
2
3
4
5
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues May 2012