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

[JBoss JIRA] Moved: (JBOSGI-453) JMX related exception when starting OSGi subsystem

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-453?page=com.atlassian.jira.plugin... ] Thomas Diesler moved AS7-857 to JBOSGI-453: ------------------------------------------- Project: JBoss OSGi (was: Application Server 7) Key: JBOSGI-453 (was: AS7-857) Workflow: jira (was: GIT Pull Request workflow ) Affects Version/s: (was: 7.0.0.CR1) Component/s: jboss-osgi-jmx (was: OSGi) Security: Public > JMX related exception when starting OSGi subsystem > -------------------------------------------------- > > Key: JBOSGI-453 > URL: https://issues.jboss.org/browse/JBOSGI-453 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-osgi-jmx > Reporter: David Bosschaert > Assignee: Jason Greene > > Very often when the OSGi subsystem comes up, I'm seeing the following exception: > 08:32:43,709 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-1) Bundle started: org.apache.aries.jmx:0.1.0.incubating > 08:32:43,710 INFO [org.apache.aries.jmx] (Thread-14) Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer@7d093a with name osgi.compendium:service=cm,version=1.3 > 08:32:43,711 INFO [org.apache.aries.jmx] (Thread-14) Registering org.osgi.jmx.framework.BundleStateMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer@7d093a with name osgi.core:type=bundleState,version=1.5 > 08:32:43,724 INFO [org.apache.aries.jmx] (Thread-14) Registering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer@7d093a with name osgi.core:type=serviceState,version=1.5 > 08:32:43,725 INFO [org.apache.aries.jmx] (Thread-14) Registering org.osgi.jmx.service.cm.ConfigurationAdminMBean to MBeanServer org.jboss.as.jmx.tcl.TcclMBeanServer@7d093a with name osgi.compendium:service=cm,version=1.3 > 08:32:43,726 ERROR [org.apache.aries.jmx] (Thread-14) MBean is already registered: org.apache.felix.log.LogException: javax.management.InstanceAlreadyExistsException: osgi.compendium:service=cm,version=1.3 > at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) [:1.6.0_23] > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) [:1.6.0_23] > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) [:1.6.0_23] > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) [:1.6.0_23] > at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) [:1.6.0_23] > at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) [:1.6.0_23] > at org.jboss.as.jmx.tcl.TcclMBeanServer.registerMBean(TcclMBeanServer.java:238) > at org.apache.aries.jmx.agent.JMXAgentImpl.registerMBeans(JMXAgentImpl.java:129) > at org.apache.aries.jmx.agent.JMXAgentContext.registerMBeans(JMXAgentContext.java:58) > at org.apache.aries.jmx.MBeanServiceTracker$1.run(MBeanServiceTracker.java:61) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_23] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_23] > at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_23] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-192) Access an OSGi service from EJB3

by Thomas Diesler (JIRA)

Access an OSGi service from EJB3 -------------------------------- Key: JBOSGI-192 URL: https://jira.jboss.org/jira/browse/JBOSGI-192 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Allow access of OSGi services from a SLSB and possibly others. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-313) OSGi service invocation from EE6 WebApp

by Thomas Diesler (JIRA)

OSGi service invocation from EE6 WebApp --------------------------------------- Key: JBOSGI-313 URL: https://jira.jboss.org/jira/browse/JBOSGI-313 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 Please investigate how we access an OSGi service from an existing EE6 webapp. This will eventually boil down to class space consistency at a layer common to both programming models. For the Native Framework this is related to the idea of ServiceMix. Please also investigate if this can be done with existing 3rd party frameworks (i.e. Felix or Equinox) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-443) Intermittent WebAppNegativeTestCase failure

by Thomas Diesler (JIRA)

Intermittent WebAppNegativeTestCase failure ------------------------------------------- Key: JBOSGI-443 URL: https://issues.jboss.org/browse/JBOSGI-443 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta11 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-448) Run OSGi integration tests as part of the AS7 Hudson job

by Thomas Diesler (JIRA)

Run OSGi integration tests as part of the AS7 Hudson job -------------------------------------------------------- Key: JBOSGI-448 URL: https://issues.jboss.org/browse/JBOSGI-448 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
1
0 / 0

[JBoss JIRA] Deleted: (JBOSGI-426) Use AS7 Arquillian subsystem instead of the arquillian-osgi-bundle

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-426?page=com.atlassian.jira.plugin... ] Thomas Diesler deleted JBOSGI-426: ---------------------------------- > Use AS7 Arquillian subsystem instead of the arquillian-osgi-bundle > ------------------------------------------------------------------ > > Key: JBOSGI-426 > URL: https://issues.jboss.org/browse/JBOSGI-426 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > > There needs to be a unique entry point for ARQ tests in AS7. \ > Currently it is not possible to run ARQ OSGi bundle tests on the Arquillian subsystem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Resolved: (JBOSGI-441) Allow for OSGi style Class Filtering

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-441?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-441. ----------------------------------- Fix Version/s: JBossOSGi 1.0.0 Beta11 (was: JBossOSGi 1.0.x) (was: JBossOSGi 1.0.0) Resolution: Done Done > Allow for OSGi style Class Filtering > ------------------------------------ > > Key: JBOSGI-441 > URL: https://issues.jboss.org/browse/JBOSGI-441 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 1.0.0 Beta11 > > > 3.6.7 Class Filtering > An exporter can limit the visibility of the classes in a package with the > include and exclude directives on the export definition. The value of each of > these directives is a comma-separated list of class names. > The following example shows an export statement, and a list of files with > their visibility status. > Export-Package: com.acme.foo; include:="Qux*,BarImpl";exclude:=QuxImpl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Work started: (JBOSGI-441) Allow for OSGi style Class Filtering

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-441?page=com.atlassian.jira.plugin... ] Work on JBOSGI-441 started by Thomas Diesler. > Allow for OSGi style Class Filtering > ------------------------------------ > > Key: JBOSGI-441 > URL: https://issues.jboss.org/browse/JBOSGI-441 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 1.0.0, JBossOSGi 1.0.x > > > 3.6.7 Class Filtering > An exporter can limit the visibility of the classes in a package with the > include and exclude directives on the export definition. The value of each of > these directives is a comma-separated list of class names. > The following example shows an export statement, and a list of files with > their visibility status. > Export-Package: com.acme.foo; include:="Qux*,BarImpl";exclude:=QuxImpl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] Assigned: (JBOSGI-441) Allow for OSGi style Class Filtering

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-441?page=com.atlassian.jira.plugin... ] Thomas Diesler reassigned JBOSGI-441: ------------------------------------- Assignee: Thomas Diesler (was: David Lloyd) > Allow for OSGi style Class Filtering > ------------------------------------ > > Key: JBOSGI-441 > URL: https://issues.jboss.org/browse/JBOSGI-441 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 1.0.0, JBossOSGi 1.0.x > > > 3.6.7 Class Filtering > An exporter can limit the visibility of the classes in a package with the > include and exclude directives on the export definition. The value of each of > these directives is a comma-separated list of class names. > The following example shows an export statement, and a list of files with > their visibility status. > Export-Package: com.acme.foo; include:="Qux*,BarImpl";exclude:=QuxImpl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues May 2011