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

[JBoss JIRA] (JBOSGI-615) VFSAdaptor30 uses non-thread-safe Map, which may result in deadlock

by Rico Neubauer (JIRA)

Rico Neubauer created JBOSGI-615: ------------------------------------ Summary: VFSAdaptor30 uses non-thread-safe Map, which may result in deadlock Key: JBOSGI-615 URL: https://issues.jboss.org/browse/JBOSGI-615 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.1.1, JBossOSGi 1.2.0, JBossOSGi 2.0.0 Beta1 Environment: all Reporter: Rico Neubauer Assignee: Thomas Diesler org.jboss.osgi.vfs30.VFSAdaptor30 uses a WeakHashMap, which is unsynchronized. However concurrent access may happen, at least in method org.jboss.osgi.vfs30.VFSAdaptor30#unregister(). This may result in a complete deadlock of the application with 100% CPU load, which cannot be resolved besides killing the java-process. See attached thread-dump. Possible solutions: - Use synchronized Map. - Use concurrent, thread-safe map. - If unregister is the only potential concurrent access, synchronizing there would suffice. -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-445) Initial OSGi / CDI Integration

by Thomas Diesler (JIRA)

Initial OSGi / CDI Integration ------------------------------- Key: JBOSGI-445 URL: https://issues.jboss.org/browse/JBOSGI-445 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.x Provide an example test that shows CDI integration -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
7
0 / 0

[JBoss JIRA] (JBOSGI-614) Allow Maven URLs to be configured to resolve external bundles

by Ulrich Romahn (JIRA)

Ulrich Romahn created JBOSGI-614: ------------------------------------ Summary: Allow Maven URLs to be configured to resolve external bundles Key: JBOSGI-614 URL: https://issues.jboss.org/browse/JBOSGI-614 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Repository Affects Versions: Continuing Environment: All Reporter: Ulrich Romahn Assignee: Thomas Diesler Priority: Critical Currently, JBoss OSGi allows to provide a Maven URI for a package which will then be resolved by the deployer according to the following rules: 1. check if the artifact is present in a local Maven repo (.m2) 2. if not, download the artifact from a remote Maven repo Currently, the class MavenArtifactRepository has two Maven repository URLs hardcoded: JBOSS_NEXUS_BASE = "http://repository.jboss.org/nexus/content/groups/public"; MAVEN_CENTRAL_BASE = "http://repo1.maven.org/maven2"; It should be possible to configure those URLs using some configuration mechanism. This is especially important in a real production environment where access to external URLs may be blocked by a firewall and an internal Nexus repo should be used to proxy a "stable set" of artifacts to be used for production. The following configuration options should be possible: 1. as it is right now 2. switch off external resolution completely. Only artifacts currently present on the local filesystem (.m2) should be resolved and loaded 3. Configure Maven URLs in addition to the hardcoded ones above 4. Configure Maven URLs as complete replacements to the hardcoded ones above -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] (JBOSGI-502) Setup R5 core TCK

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-502?page=com.atlassian.jira.plugin... ] Work on JBOSGI-502 started by Thomas Diesler. > Setup R5 core TCK > ----------------- > > Key: JBOSGI-502 > URL: https://issues.jboss.org/browse/JBOSGI-502 > Project: JBoss OSGi > Issue Type: Task > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 2.0.0 Alpha1 > > > Write an internal Wiki for the TCK setup -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-550) OSGi support in OpenShift

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-550: ------------------------------------- Summary: OSGi support in OpenShift Key: JBOSGI-550 URL: https://issues.jboss.org/browse/JBOSGI-550 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Cloud/OpenShift Reporter: Thomas Diesler Assignee: Thomas Diesler As well as providing the core OSGi functionality in OpenShift, we need to provide management capabilities, documentation and working examples. -- 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

11 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-260) Initial Enterprise OSGi JPA implementation

by Thomas Diesler (JIRA)

Initial Enterprise OSGi JPA implementation ------------------------------------------ Key: JBOSGI-260 URL: https://jira.jboss.org/jira/browse/JBOSGI-260 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jboss-osgi-jpa Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x -- 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

11 years, 7 months

7
19
0 / 0

[JBoss JIRA] (JBOSGI-561) Add jBPM integration example

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-561: ------------------------------------- Summary: Add jBPM integration example Key: JBOSGI-561 URL: https://issues.jboss.org/browse/JBOSGI-561 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) 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

11 years, 7 months

1
4
0 / 0

[JBoss JIRA] (JBOSGI-613) Bundle.uninstall() may not remove it from persistent storage

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-613: ------------------------------------- Summary: Bundle.uninstall() may not remove it from persistent storage Key: JBOSGI-613 URL: https://issues.jboss.org/browse/JBOSGI-613 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 This seems to be the case when the bundle is still wired. Restarting the framework would then restore the previously uninstalled bundle -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-612) Race condition may prevent Framework startup

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-612: ------------------------------------- Summary: Race condition may prevent Framework startup Key: JBOSGI-612 URL: https://issues.jboss.org/browse/JBOSGI-612 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 BootstrapBundleResolve tracker may never complete -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] (JBOSGI-609) Timeout getting: jbosgi.framework.INIT

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-609: ------------------------------------- Summary: Timeout getting: jbosgi.framework.INIT Key: JBOSGI-609 URL: https://issues.jboss.org/browse/JBOSGI-609 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 {code} Timeout getting: jbosgi.framework.INIT at org.jboss.osgi.framework.spi.FutureServiceValue.getValue(FutureServiceValue.java:146) at org.jboss.osgi.framework.spi.FutureServiceValue.get(FutureServiceValue.java:91) at org.jboss.osgi.framework.internal.FrameworkProxy.awaitFrameworkInit(FrameworkProxy.java:409) at org.jboss.osgi.framework.internal.FrameworkProxy.init(FrameworkProxy.java:157){code} -- 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, 7 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues October 2012