January 2013 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-581) Update Aries Blueprint to 1.0.0

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-581?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-581: ---------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > Update Aries Blueprint to 1.0.0 > ------------------------------- > > Key: JBOSGI-581 > URL: https://issues.jboss.org/browse/JBOSGI-581 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Blueprint > Reporter: David Bosschaert > Fix For: JBossOSGi 2.0.0 Alpha1 > > > Update the Blueprint integration to use Aries Blueprint 1.0.0. -- 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] (JBOSGI-519) InitialContextFactoryBuilder already registered in AS

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-519?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-519: ---------------------------------- Assignee: (was: David Bosschaert) Available for reassignment > InitialContextFactoryBuilder already registered in AS > ----------------------------------------------------- > > Key: JBOSGI-519 > URL: https://issues.jboss.org/browse/JBOSGI-519 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JNDI > Reporter: Thomas Diesler > Fix For: JBossOSGi 2.0.0 Alpha1 > > > In AS we see > {code} > 09:59:52,782 INFO [org.apache.aries.jndi.startup.Activator] (pool-4-thread-1) It was not possible to register an InitialContextFactoryBuilder with the NamingManager because another builder called org.jboss.as.naming.InitialContextFactoryBuilder was already registered. Support for calling new InitialContext() will not be enabled.: java.lang.IllegalStateException: InitialContextFactoryBuilder already set > at javax.naming.spi.NamingManager.setInitialContextFactoryBuilder(NamingManager.java:692) [rt.jar:1.6.0_29] > at org.apache.aries.jndi.startup.Activator.start(Activator.java:76) > at org.apache.aries.jndi.priv.Activator.start(Activator.java:38) > at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488) > at org.jboss.test.osgi.NamingSupport.provideJNDIIntegration(NamingSupport.java:44) > at org.jboss.test.osgi.example.jndi.JNDITestCase.testOSGiNamingContext(JNDITestCase.java:91) > {code} -- 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] (JBOSGI-625) Improve log message when bundle start level not valid for start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-625. ----------------------------------- Resolution: Done Done in jbosgi-framework-2.1.0.CR12 > Improve log message when bundle start level not valid for start > --------------------------------------------------------------- > > Key: JBOSGI-625 > URL: https://issues.jboss.org/browse/JBOSGI-625 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Environment: Jboss as 7.1.2.Final > JDK6 > EAP 6.0.0 > Reporter: Daniel Chapman > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 > I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. > What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. > So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? > Thanks! -- 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] (JBOSGI-625) Improve log message when bundle start level not valid for start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-625: ---------------------------------- Summary: Improve log message when bundle start level not valid for start (was: Start level not valid message) > Improve log message when bundle start level not valid for start > --------------------------------------------------------------- > > Key: JBOSGI-625 > URL: https://issues.jboss.org/browse/JBOSGI-625 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Environment: Jboss as 7.1.2.Final > JDK6 > EAP 6.0.0 > Reporter: Daniel Chapman > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 > I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. > What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. > So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? > Thanks! -- 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] (JBOSGI-625) Start level not valid message

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ] Thomas Diesler edited comment on JBOSGI-625 at 1/25/13 4:44 AM: ---------------------------------------------------------------- Daniel, could you perhaps work with me to reproduce this with the latest master? We now have server restart test functionality that should allow us to isolate the issue (outside the the context of infinispan) {code} // If the Framework's current start level is less than this bundle's start level if (startLevelValidForStart() == false) { LOGGER.debugf("Start level [%d] not valid for: %s", getBundleStartLevel(), this); return; } {code} I can promote this to info and also say what the current framework start level is. If you want to achieve autostart for your capabilities you can assign a start-level attribute was (Author: thomas.diesler): Daniel, could you perhaps work with me to reproduce this with the latest master? We now have server restart test functionality that should allow us to isolate the issue (outside the the context of infinispan) > Start level not valid message > ----------------------------- > > Key: JBOSGI-625 > URL: https://issues.jboss.org/browse/JBOSGI-625 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Environment: Jboss as 7.1.2.Final > JDK6 > EAP 6.0.0 > Reporter: Daniel Chapman > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 > I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. > What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. > So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? > Thanks! -- 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] (JBOSGI-625) Start level not valid message

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ] Thomas Diesler edited comment on JBOSGI-625 at 1/25/13 4:44 AM: ---------------------------------------------------------------- Daniel, could you perhaps work with me to reproduce this with the latest master? We now have server restart test functionality that should allow us to isolate the issue (outside the the context of infinispan) {code} // If the Framework's current start level is less than this bundle's start level if (startLevelValidForStart() == false) { LOGGER.debugf("Start level [%d] not valid for: %s", getBundleStartLevel(), this); return; } {code} I can promote this to info and also say what the current framework start level is. If you want to achieve autostart for your capabilities you can assign a start-level attribute was (Author: thomas.diesler): Daniel, could you perhaps work with me to reproduce this with the latest master? We now have server restart test functionality that should allow us to isolate the issue (outside the the context of infinispan) {code} // If the Framework's current start level is less than this bundle's start level if (startLevelValidForStart() == false) { LOGGER.debugf("Start level [%d] not valid for: %s", getBundleStartLevel(), this); return; } {code} I can promote this to info and also say what the current framework start level is. If you want to achieve autostart for your capabilities you can assign a start-level attribute > Start level not valid message > ----------------------------- > > Key: JBOSGI-625 > URL: https://issues.jboss.org/browse/JBOSGI-625 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Environment: Jboss as 7.1.2.Final > JDK6 > EAP 6.0.0 > Reporter: Daniel Chapman > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 > I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. > What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. > So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? > Thanks! -- 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] (JBOSGI-625) Start level not valid message

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ] Thomas Diesler commented on JBOSGI-625: --------------------------------------- Daniel, could you perhaps work with me to reproduce this with the latest master? We now have server restart test functionality that should allow us to isolate the issue (outside the the context of infinispan) > Start level not valid message > ----------------------------- > > Key: JBOSGI-625 > URL: https://issues.jboss.org/browse/JBOSGI-625 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Environment: Jboss as 7.1.2.Final > JDK6 > EAP 6.0.0 > Reporter: Daniel Chapman > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 > I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. > What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. > So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? > Thanks! -- 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] (JBOSGI-625) Start level not valid message

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-625?page=com.atlassian.jira.plugin... ] Work on JBOSGI-625 started by Thomas Diesler. > Start level not valid message > ----------------------------- > > Key: JBOSGI-625 > URL: https://issues.jboss.org/browse/JBOSGI-625 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Affects Versions: JBossOSGi 1.1.1 > Environment: Jboss as 7.1.2.Final > JDK6 > EAP 6.0.0 > Reporter: Daniel Chapman > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > When I set org.jboss.osgi.framework to DEBUG, I get messages like the following: > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Starting bundle: org.apache.aries.blueprint:1.0.0 > 11:48:32,694 DEBUG [org.jboss.osgi.framework] (HttpManagementService-threads - 10) Start level [2] not valid for: org.apache.aries.blueprint:1.0.0 > I'd like more information on this message. I've seen it during various startup configurations in messing with my capabilities and it seems to matter little when fixing real issue. > What I'm doing above is clicking the Start Bundle button in the osgi console. It prints these two messages as DEBUG, nothing else is printed, and net result is console refreshes and no changes have been made to the status of the bundle. > So is this message really relevant, if so - then why DEBUG only. Second - what do I do when I got to start a module, nothing is printed to logs (except above) and the bundle doesn't actually start? > Thanks! -- 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] (JBOSGI-627) Misspelled system property FRAMEWORK_VENDOR

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-627?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-627: ---------------------------------- Summary: Misspelled system property FRAMEWORK_VENDOR (was: Misspelled system property FRAMEWORK_VENDOR "org.osgi.vendor.framework") > Misspelled system property FRAMEWORK_VENDOR > ------------------------------------------- > > Key: JBOSGI-627 > URL: https://issues.jboss.org/browse/JBOSGI-627 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Andreas Weise > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > JBoss AS 7 uses misspelled system property for OSGi constant FRAMEWORK_VENDOR which is not defined by OSGi spec. > Reference http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/Constants.html defines for constant FRAMEWORK_VENDOR: > "org.osgi.framework.vendor" > Jboss uses: > "org.osgi.vendor.framework" -- 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] (JBOSGI-627) Misspelled system property FRAMEWORK_VENDOR

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-627?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-627. ----------------------------------- Resolution: Done Done in jbosgi-framework-2.1.0.CR12 > Misspelled system property FRAMEWORK_VENDOR > ------------------------------------------- > > Key: JBOSGI-627 > URL: https://issues.jboss.org/browse/JBOSGI-627 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Andreas Weise > Assignee: Thomas Diesler > Priority: Minor > Fix For: JBossOSGi 1.2.0 > > > JBoss AS 7 uses misspelled system property for OSGi constant FRAMEWORK_VENDOR which is not defined by OSGi spec. > Reference http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/Constants.html defines for constant FRAMEWORK_VENDOR: > "org.osgi.framework.vendor" > Jboss uses: > "org.osgi.vendor.framework" -- 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

jboss-osgi-issues January 2013