December 2011 - jboss-osgi-issues

[JBoss JIRA] Created: (JBOSGI-460) Improve toString() for resolver objects

by Thomas Diesler (JIRA)

Improve toString() for resolver objects --------------------------------------- Key: JBOSGI-460 URL: https://issues.jboss.org/browse/JBOSGI-460 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Caused by: org.osgi.framework.BundleException: Cannot initialize XModule from: {Export-Package=[org.jboss.osgi.metadata.internal.AbstractPackageAttribute@24ebf068, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@7df44ec7, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@32602b6b, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@47c297a3, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@38717323, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@203e1bc8, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@4d91f801, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@2a313170, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@3a4c5b4, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@36afae4a, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@47db9852, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@21ed5459, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@643cb075, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@4c6504bc, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@7c19f9d2, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@d6089a5, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@3cecb67f, org.jboss.osgi.metadata.internal.AbstractPackageAttribute@58c16b18], Bundle-SymbolicName=[org.jboss.osgi.metadata.internal.AbstractParameterizedAttribute@25e222e], Bundle-Activator=org.jboss.arquillian.osgi.ArquillianBundleActivator, Bundle-Version=1.0.0.CR1-as734-SNAPSHOT} at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.load(AbstractModuleBuilder.java:202) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.createModule(AbstractModuleBuilder.java:56) at org.jboss.osgi.framework.internal.UserBundleState.createResolverModule(UserBundleState.java:152) at org.jboss.osgi.framework.internal.UserBundleInstalledService.start(UserBundleInstalledService.java:62) ... 4 more Caused by: java.lang.NumberFormatException: For input string: "${version" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:449) at java.lang.Integer.parseInt(Integer.java:499) at org.osgi.framework.Version.<init>(Version.java:125) at org.osgi.framework.Version.parseVersion(Version.java:218) at org.jboss.osgi.resolver.spi.AbstractPackageCapability.<init>(AbstractPackageCapability.java:48) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.addPackageCapability(AbstractModuleBuilder.java:100) at org.jboss.osgi.resolver.spi.AbstractModuleBuilder.load(AbstractModuleBuilder.java:163) ... 7 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-413) Xerces bundle defines invalid dependency on wutka.dtdparser

by Thomas Diesler (JIRA)

Xerces bundle defines invalid dependency on wutka.dtdparser ----------------------------------------------------------- Key: JBOSGI-413 URL: https://jira.jboss.org/browse/JBOSGI-413 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Currently we need to exclude the dependency on wutka.dtdparser because it is not in the public jboss repository Builds with a clea mvn repo fail. Try a build after rm -rf ~/.m2/repository/wutka-dtdparser https://repository.jboss.org/nexus/content/groups/public-jboss/wutka-dtdp... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-504) DOMWebXmlParser fails if jsp-file is used

by Rico Neubauer (Created) (JIRA)

DOMWebXmlParser fails if jsp-file is used ----------------------------------------- Key: JBOSGI-504 URL: https://issues.jboss.org/browse/JBOSGI-504 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webapp Affects Versions: JBossOSGi 1.0.0 Reporter: Rico Neubauer Assignee: Thomas Diesler OSGi-deployment fails if web.xml defines a jsp-file entry. This is actually a bug in the used pax-web component. Opened up here: http://team.ops4j.org/browse/PAXWEB-328 This is for information, maybe thinking about a workaround and to upgrade, once it is fixed. Stacktrace including JBoss classes as well: [org.jboss.msc.service] (MSC service thread 1-7) MSC00002: Invocation of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@6d5535b7" failed: org.ops4j.lang.NullArgumentException: Servlet class is null. at org.ops4j.lang.NullArgumentException.validateNotNull(NullArgumentException.java:75) at org.ops4j.pax.web.extender.war.internal.model.WebAppServlet.setServletClass(WebAppServlet.java:115) at org.ops4j.pax.web.extender.war.internal.parser.dom.DOMWebXmlParser.parseServlets(DOMWebXmlParser.java:284) at org.ops4j.pax.web.extender.war.internal.parser.dom.DOMWebXmlParser.parse(DOMWebXmlParser.java:76) at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.createWebAppMetadata(WebXMLParserInterceptor.java:82) at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.invoke(WebXMLParserInterceptor.java:66) at org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:281) [jbosgi-deployment-1.0.10.jar:] at org.jboss.osgi.framework.internal.LifecycleInterceptorPlugin.handleStateChange(LifecycleInterceptorPlugin.java:125) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:183) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:172) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:282) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:494) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:144) [jboss-as-osgi-service-7.1.0.Beta1.jar:] at org.jboss.as.osgi.deployment.BundleStartTracker$1.transition(BundleStartTracker.java:119) [jboss-as-osgi-service-7.1.0.Beta1.jar:] at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1429) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:49) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1952) [jboss-msc-1.0.1.GA.jar:] -- 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

12 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-285) Add PaxWeb JSP support

by Thomas Diesler (JIRA)

Add PaxWeb JSP support ---------------------- Key: JBOSGI-285 URL: https://jira.jboss.org/jira/browse/JBOSGI-285 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 It seems that another jar is missing from distribution, the Pax Web Extender JSP, as the log message says: WARN [RegisterWebAppVisitorWC] Jsp support is not enabled. Is org.ops4j.pax.web.jsp bundle installed? Obviously not! So I downloaded the latest version (0.7.1) of Pax Web Extender JSP and successfully deployed it: INFO [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-extender-war [16] INFO [Activator] Pax Web started INFO [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-jetty-bundle [17] INFO [JettyServerImpl] Pax Web available at [0.0.0.0]:[8090] INFO [HttpServiceFactoryImpl] Binding bundle: [jboss-osgi-webconsole [12]] to http service INFO [BundleStartStopDeployer] Started: org.ops4j.pax.web.pax-web-jsp [18] But it doesn't seems to work because I always get the same WARN message above... suggestions? -- 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, 4 months

2
14
0 / 0

[JBoss JIRA] Created: (JBOSGI-480) Resolver Exception sometimes gets hidden by a subsequent NPE

by David Bosschaert (JIRA)

Resolver Exception sometimes gets hidden by a subsequent NPE ------------------------------------------------------------ Key: JBOSGI-480 URL: https://issues.jboss.org/browse/JBOSGI-480 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Bosschaert Assignee: David Bosschaert In some cases a resolver exception gets shadowed by a NPE that happens during the processing of the resolver exception, this means that the end user has no way of knowing why the resolution failed, he only sees the NPE. The offending code can be found in the FelixResolver class, line 117: XResolverException resex = new XResolverException(msg, exmod.getModule(), exreq); In some cases exmod is null which means that an NPE gets thrown and the resolution exception is lost. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
6
0 / 0

[JBoss JIRA] (JBOSGI-505) OSGi-WAR fails to deploy

by Rico Neubauer (Created) (JIRA)

OSGi-WAR fails to deploy ------------------------ Key: JBOSGI-505 URL: https://issues.jboss.org/browse/JBOSGI-505 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Rico Neubauer Assignee: Thomas Diesler Attachments: server.log Trying to deploy a very simple WAR, containing one Servlet as OSGi-bundle on jboss-as-7.1.0.Beta1 fails with error on ClassLoading the servlet. osgi-subsystem activation is set to "eager", startlevel to "3". Will attach full log and test-WAR, here is an extract from the stacktrace: ERROR [org.ops4j.pax.web.extender.war.internal.RegisterWebAppVisitorWC] (MSC service thread 1-12) Registration exception. Skipping.: java.lang.ClassNotFoundException: jboss.osgi.webapp.test.JNDIViewServlet from [Module "deployment.jboss.osgi.webapp.test.OSGiWebApp:0.0.1.SNAPSHOT" from Service Module Loader] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.0.CR4] at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:485) [jboss-modules.jar:1.1.0.CR4] at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:421) [jboss-modules.jar:1.1.0.CR4] at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:155) [jboss-modules.jar:1.1.0.CR4] at org.jboss.osgi.framework.internal.HostBundleRevision.loadClass(HostBundleRevision.java:114) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:415) [jbosgi-framework-core-1.1.0.jar:] at org.jboss.osgi.framework.internal.HostBundleState.loadClass(HostBundleState.java:151) [jbosgi-framework-core-1.1.0.jar:] -- 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

12 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-466) Felix web console depends on start order

by David Bosschaert (JIRA)

Felix web console depends on start order ---------------------------------------- Key: JBOSGI-466 URL: https://issues.jboss.org/browse/JBOSGI-466 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webconsole Affects Versions: JBossOSGi 1.0.0 Beta10 Reporter: David Bosschaert Assignee: Thomas Diesler The Felix web console only works when started after the webcontainer. See JBOSGI-464 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
7
0 / 0

[JBoss JIRA] (JBOSGI-506) Restore AS7 remote testing

by Thomas Diesler (Moved) (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-506?page=com.atlassian.jira.plugin... ] Thomas Diesler moved AS7-3037 to JBOSGI-506: -------------------------------------------- Project: JBoss OSGi (was: Application Server 7) Key: JBOSGI-506 (was: AS7-3037) Workflow: jira (was: GIT Pull Request workflow ) Component/s: (was: OSGi) Security: Public Fix Version/s: JBossOSGi 1.0.1 (was: 7.1.0.Final) > Restore AS7 remote testing > -------------------------- > > Key: JBOSGI-506 > URL: https://issues.jboss.org/browse/JBOSGI-506 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 1.0.1 > > > Currently we have: > * Webconsole, provided by Felix (requires HttpService) > * HttpService, provided by PaxWeb (runs on Jetty) > * Webapp support, provided by PaxWeb (runs on Jetty) > * LogService, provided by Felix > * ConfigAdmin service, provided by Felix > * JMX services, provided by Aries > * EventAdmin, provided by Felix > * DeclarativServices, provided by Felix > * STOMP endpoints (Stilts), provided by JBoss > * Blueprint, provided by Aries > * XML parsing, provided by JBoss > * JNDI support, provided by JBoss > * JTA support, provided by JBoss -- 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

12 years, 5 months

1
0
0 / 0

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

by Thomas Diesler (Commented) (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-453?page=com.atlassian.jira.plugin... ] Thomas Diesler commented on JBOSGI-453: --------------------------------------- No progress in https://issues.apache.org/jira/browse/ARIES-663 You could set the logger level to FATAL for this package if it really bugs you. This could of course also hide other potential errors > 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: Thomas Diesler > Fix For: JBossOSGi 1.0.2 > > > 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. 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

12 years, 5 months

1
0
0 / 0

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

by Rafael Soares (Commented) (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-453?page=com.atlassian.jira.plugin... ] Rafael Soares commented on JBOSGI-453: -------------------------------------- I would like to test the JBoss OSGi 1.0 standalone implementation. Is there any workaround for this issue? Thanks. > 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: Thomas Diesler > Fix For: JBossOSGi 1.0.2 > > > 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. 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

12 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues December 2011