[JBoss JIRA] Created: (JBOSGI-457) ConcurrentModificationException in UserBundleState.hasActiveWires
by Stuart Douglas (JIRA)
ConcurrentModificationException in UserBundleState.hasActiveWires
-----------------------------------------------------------------
Key: JBOSGI-457
URL: https://issues.jboss.org/browse/JBOSGI-457
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Stuart Douglas
Assignee: Thomas Diesler
10:36:30,347 WARN [org.jboss.msc.service.fail] MSC00004: Failure during stop of service jbosgi.bundle.9."org.apache.aries.jmx"."0.3.0".INSTALLED: java.util.ConcurrentModificationException
at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:373) [:1.6.0_22]
at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:384) [:1.6.0_22]
at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1010) [:1.6.0_22]
at org.jboss.osgi.framework.internal.UserBundleState.hasActiveWires(UserBundleState.java:237)
at org.jboss.osgi.framework.internal.BundleManager.uninstallBundle(BundleManager.java:462)
at org.jboss.osgi.framework.internal.UserBundleInstalledService.stop(UserBundleInstalledService.java:88)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1779)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_22]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[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
[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
[JBoss JIRA] Created: (JBOSGI-447) Dynamic-ImportPackage=* fails for org/osgi/framework
by David Bosschaert (JIRA)
Dynamic-ImportPackage=* fails for org/osgi/framework
----------------------------------------------------
Key: JBOSGI-447
URL: https://issues.jboss.org/browse/JBOSGI-447
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.0.x
Reporter: David Bosschaert
I came across a bundle that has a Dynamic-ImportPackage: * but deploying this in AS7 causes a NoClassDefFoundError on org.osgi.framework.BundleActivator.
I would argue that the design of this bundle could be improved to at least explicitly import org.osgi.framework, but it should work. This bundle works fine in Apache Felix.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (JBOSGI-385) IllegalStateException when deploying & starting a bundle through web console
by David Bosschaert (JIRA)
IllegalStateException when deploying & starting a bundle through web console
----------------------------------------------------------------------------
Key: JBOSGI-385
URL: https://jira.jboss.org/browse/JBOSGI-385
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core Framework, jboss-osgi-webconsole
Affects Versions: JBossOSGi 1.0.0 Beta8
Reporter: David Bosschaert
When installing a bundle through the web console and ticking the start tickbox as well, it often generates an exception (see below). It is probably related to the fact that if you don't select the start tickbox, the bundle gets started anyway. With the tickbox enabled it seems like the system is trying to start the bundle twice concurrently.
org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot start bundle: exporting-bundle:0.0.0
at org.jboss.osgi.container.bundle.HostBundle.startInternal(HostBundle.java:239)
at org.jboss.osgi.container.bundle.AbstractBundle.start(AbstractBundle.java:478)
at org.jboss.osgi.container.plugin.internal.StartLevelPluginImpl$3.run(StartLevelPluginImpl.java:162)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: BundleContext already available
at org.jboss.osgi.container.bundle.AbstractBundle.createBundleContext(AbstractBundle.java:170)
at org.jboss.osgi.container.bundle.HostBundle.startInternal(HostBundle.java:179)
... 5 more
--
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, 10 months