May 2012 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-547) ClassNotFoundException: org.osgi.service.log.LogService in org.apache.felix.eventadmin:1.2.6

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-547: ------------------------------------- Summary: ClassNotFoundException: org.osgi.service.log.LogService in org.apache.felix.eventadmin:1.2.6 Key: JBOSGI-547 URL: https://issues.jboss.org/browse/JBOSGI-547 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 {code} 10:10:42,640 WARN [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011018: Error while firing service event REGISTERED for: ServiceState{service.id=46, objectClass=[org.osgi.service.log.LogReaderService]}: java.lang.NoClassDefFoundError: org/osgi/service/log/LogReaderService at org.apache.felix.eventadmin.impl.adapter.LogEventAdapter.serviceChanged(LogEventAdapter.java:120) at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireServiceEvent(FrameworkEventsPlugin.java:512) at org.jboss.osgi.framework.internal.ServiceManagerPlugin.registerService(ServiceManagerPlugin.java:198) at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:309) at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:297) at org.apache.felix.log.Activator.start(Activator.java:119) at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:321) at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:245) at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:491) at org.jboss.osgi.framework.internal.StartLevelPlugin.increaseStartLevel(StartLevelPlugin.java:250) at org.jboss.osgi.framework.internal.FrameworkActive.start(FrameworkActive.java:131) {code} -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] (JBOSGI-530) No logging messages from org.jboss.modules

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-530: ------------------------------------- Summary: No logging messages from org.jboss.modules Key: JBOSGI-530 URL: https://issues.jboss.org/browse/JBOSGI-530 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.1.2 jboss-modules requires the client to explicitly set the ModuleLogger, otherwise there are no logging messages. Currently the framework does not do that -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-543) Bundle start level not persistently recorded

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-543: ------------------------------------- Summary: Bundle start level not persistently recorded Key: JBOSGI-543 URL: https://issues.jboss.org/browse/JBOSGI-543 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.1.0 Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-533) OSGiMetaData returns non-stable value from toString()

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-533: ------------------------------------- Summary: OSGiMetaData returns non-stable value from toString() Key: JBOSGI-533 URL: https://issues.jboss.org/browse/JBOSGI-533 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 Currently {code} @Override public String toString() { return cachedAttributes.toString(); } {code} -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-558) Provide repository dependencies as part of the bundle

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-558: ------------------------------------- Summary: Provide repository dependencies as part of the bundle Key: JBOSGI-558 URL: https://issues.jboss.org/browse/JBOSGI-558 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Repository Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 David says {quote} In preparation for being able to run the JBOSGi repository in the OSGi TCK I need to be able to deploy it outside of the JBoss OSGi framework - the TCK uses Equinox. When I was trying this there were a number of dependencies that I could not find OSGi bundles for: org.jboss.osgi.metadata;version="[2.0,3.0)" org.jboss.osgi.resolver;version="[2.0,3.0)" org.jboss.osgi.resolver.spi;version="[2.0,3.0)" Are these available as OSGi bundles somewhere? {quote} -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] (JBOSGI-532) Externalize notion of OSGi Environment

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-532: ------------------------------------- Summary: Externalize notion of OSGi Environment Key: JBOSGI-532 URL: https://issues.jboss.org/browse/JBOSGI-532 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Currently, the BundleManager is the maintainer of all bundles. This should be generalized/externalized to the Environment, which should maintain a set of Resources. The Framework would be a client of the Environment. Other clients to the Environment (i.e. AS7) can also register Resources with the Environment, which would then be available to the Resolver. -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] (JBOSGI-522) Update felix/equinox modules for meaningful performance data

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-522: ------------------------------------- Summary: Update felix/equinox modules for meaningful performance data Key: JBOSGI-522 URL: https://issues.jboss.org/browse/JBOSGI-522 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.1 -- 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, 4 months

1
6
0 / 0

[JBoss JIRA] (JBOSGI-541) Document how bundle configurations can be edited

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-541: ------------------------------------- Summary: Document how bundle configurations can be edited Key: JBOSGI-541 URL: https://issues.jboss.org/browse/JBOSGI-541 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] (JBOSGI-563) ClassCastException - AbstractResource cannot be cast to AbstractBundleRevision

by Rico Neubauer (JIRA)

Rico Neubauer created JBOSGI-563: ------------------------------------ Summary: ClassCastException - AbstractResource cannot be cast to AbstractBundleRevision Key: JBOSGI-563 URL: https://issues.jboss.org/browse/JBOSGI-563 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 Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final Unfortunately not sure about the conditions - a vanilla JBoss does not show the symptom, I assume it depends on how bundle dependencies are defined, or on capability usages. Will try to find out more, but the following presents an issue anyway: Accessing bundles may throw a ClassCastException in: - org.jboss.osgi.framework.internal.HostBundleState#getDependentBundles() - org.jboss.osgi.framework.internal.PackageAdminPlugin.ExportedPackageImpl#getImportingBundles() - There are other places of unchecked casts to AbstractBundleRevision, but they may be OK. The following occurs when accessing the problematic bundles via felix web-console: {noformat} org.apache.felix.http.jetty WARN /system/console/bundles/0: java.lang.ClassCastException: org.jboss.osgi.resolver.spi.AbstractResource cannot be cast to org.jboss.osgi.framework.internal.AbstractBundleRevision at org.jboss.osgi.framework.internal.PackageAdminPlugin$ExportedPackageImpl.getImportingBundles(PackageAdminPlugin.java:536) at org.apache.felix.webconsole.internal.core.BundlesServlet.listImportExport(BundlesServlet.java:813) at org.apache.felix.webconsole.internal.core.BundlesServlet.bundleDetails(BundlesServlet.java:750) at org.apache.felix.webconsole.internal.core.BundlesServlet.bundleInfo(BundlesServlet.java:673) at org.apache.felix.webconsole.internal.core.BundlesServlet.writeJSON(BundlesServlet.java:568) at org.apache.felix.webconsole.internal.core.BundlesServlet.writeJSON(BundlesServlet.java:500) at org.apache.felix.webconsole.internal.core.BundlesServlet.renderContent(BundlesServlet.java:474) at org.apache.felix.webconsole.AbstractWebConsolePlugin.doGet(AbstractWebConsolePlugin.java:147) at org.apache.felix.webconsole.internal.core.BundlesServlet.doGet(BundlesServlet.java:246) at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:437) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:384) at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96) at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79) at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42) at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49) at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33) at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48) at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39) at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) {noformat} Will attach a fix for those two locations. -- 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
6
0 / 0

[JBoss JIRA] (JBOSGI-555) Cannot activate OSGi subsystem with fragment bundle deployments

by Rico Neubauer (JIRA)

Rico Neubauer created JBOSGI-555: ------------------------------------ Summary: Cannot activate OSGi subsystem with fragment bundle deployments Key: JBOSGI-555 URL: https://issues.jboss.org/browse/JBOSGI-555 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 Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final See https://issues.jboss.org/browse/AS7-4814 for an issue in the same area. This bug here happens independently of the other. Having OSGi bundles, that are fragments leads to {noformat} INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report JBAS014775: Neue fehlende/unbefriedigte Abhängigkeiten: (this is German, in English. sth. like Missing/unresolved dependencies) service jbosgi.integration.PersistentBundlesHandler.COMPLETE (missing) dependents: [service jbosgi.framework.INIT] {noformat} This is because when bundle is installed via {noformat}org.jboss.osgi.framework.internal.BundleManagerPlugin.installBundle(Deployment, ServiceListener<Bundle>){noformat} in case of a fragment, the listener is not passed to the FragmentBundleInstalledService (BundleManagerPlugin, line 364). In consequence, there is no notification for this bundle in {noformat}org.jboss.osgi.framework.util.ServiceTracker.listenerAdded(ServiceController<? extends S>){noformat} which leads to org.jboss.osgi.framework.util.ServiceTracker.addedNames not containing the bundle and then when org.jboss.osgi.framework.util.ServiceTracker.checkAndComplete() is invoked the check for completeness in {noformat}org.jboss.as.osgi.service.PersistentBundlesIntegration.InitialDeploymentTracker.InitialDeploymentTracker(...).new PersistentBundlesComplete() {...}.allServicesAdded(Set<ServiceName>){noformat} fails due to different sizes of bundleInstallServices and trackedServices. I will attach a proposed patch, which resolves the issue by adding the listener also to FragmentBundleInstalledService. -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues May 2012