[JBoss JIRA] (JBOSGI-624) Bundle importing the package of multiple versions isn't supported
by Hari Ohm Prasath (JIRA)
Hari Ohm Prasath created JBOSGI-624:
---------------------------------------
Summary: Bundle importing the package of multiple versions isn't supported
Key: JBOSGI-624
URL: https://issues.jboss.org/browse/JBOSGI-624
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Hari Ohm Prasath
Assignee: Thomas Diesler
I have a OSGI service bundle with Bundle-Version as "1.0.0" in which i have exported this particular package "com.example.test" and I have a OSGI web client where i am importing this package with version as "[1.0.0,2.0.0]" (i.e)
Import-Package:com.example.test;version:[1.0.0,3.0.0]. Now when i start the client bundle after the service bundle I am getting this exception:
13:21:36,952 WARN [org.jboss.as.osgi] (MSC service thread 1-10) JBAS011910: Can
not resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=com.example.test, version=[1.0.0,2.0.0]},[TestServlet:0.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
11 years, 4 months
[JBoss JIRA] (JBOSGI-623) Deadlock in Module FallbackClassLoader
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-623?page=com.atlassian.jira.plugin... ]
Thomas Diesler moved AS7-6063 to JBOSGI-623:
--------------------------------------------
Project: JBoss OSGi (was: Application Server 7)
Key: JBOSGI-623 (was: AS7-6063)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: Core Framework
(was: OSGi)
Security: Public
Fix Version/s: JBossOSGi 1.2.0
(was: 7.2.0.CR1)
> Deadlock in Module FallbackClassLoader
> --------------------------------------
>
> Key: JBOSGI-623
> URL: https://issues.jboss.org/browse/JBOSGI-623
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core Framework
> Reporter: Steve Reed
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: JBossOSGi 1.2.0
>
> Attachments: jboss-dead-lock.txt, ThreadDump-2.txt
>
>
> Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar
> Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8...
> During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started.
> The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible.
> I will attach the thread dump to this issue as supporting evidence.
--
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
11 years, 4 months
[JBoss JIRA] (JBOSGI-623) Deadlock in Module FallbackClassLoader
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/JBOSGI-623?page=com.atlassian.jira.plugin... ]
Work on JBOSGI-623 started by Thomas Diesler.
> Deadlock in Module FallbackClassLoader
> --------------------------------------
>
> Key: JBOSGI-623
> URL: https://issues.jboss.org/browse/JBOSGI-623
> Project: JBoss OSGi
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core Framework
> Reporter: Steve Reed
> Assignee: Thomas Diesler
> Priority: Critical
> Fix For: JBossOSGi 1.2.0
>
> Attachments: jboss-dead-lock.txt, ThreadDump-2.txt
>
>
> Actually the version is 2.0.1.final - jbosgi-framework-core-2.0.1.Final.jar
> Commit reference for JBOSS AS :- https://github.com/jbossas/jboss-as/commit/ed2bc551a55ec6a8167a8657cbb5d8...
> During start up of JBOSS AS7.0 two GeminiBlueprintExtender Threads deadlock, and services in the JBOSS OSGI container are not started.
> The deadlock appears to be concerned with a Module FallbackLoader, which acquires a lock during a call to loadClassLocal() and then proceeds to use an alternate Module to load the class, if this results in the alternate Module using it's FallbackLoader to load a class or resource, then it must also acquire a lock first. Obviously if two or more threads are attempting this, then a dead lock is possible.
> I will attach the thread dump to this issue as supporting evidence.
--
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
11 years, 4 months