[jira] Updated: (FELIX-1032) NPE on URL#openStream()
[
https://issues.apache.org/jira/browse/FELIX-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-1032:
---
Affects Version/s: felix-1.6.0
> NPE on URL#openStream()
> ---
>
> Key: FELIX-1032
> URL: https://issues.apache.org/jira/browse/FELIX-1032
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: felix-1.4.1, felix-1.6.0
> Environment: Linux bono 2.6.28-6-generic #17-Ubuntu SMP Fri Jan 30
> 15:34:36 UTC 2009 i686 GNU/Linux
> java version "1.6.0_13"
> Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
> Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
>Reporter: Martin Zdila
>Priority: Critical
>
> Note that also affected is felix-1.6.0 (it is not in the list).
> I am often getting NPE with the following code:
> new URL("bundle://66.0:0/somewhere/my.resource" /* or any other bundle:// URL
> */).openStream();
> java.lang.NullPointerException
> at java.util.zip.Inflater.ensureOpen(Inflater.java:336)
> at java.util.zip.Inflater.getBytesWritten(Inflater.java:296)
> at java.util.zip.ZipFile$1.available(ZipFile.java:243)
> at
> org.apache.felix.framework.URLHandlersBundleURLConnection.connect(URLHandlersBundleURLConnection.java:125)
> at
> org.apache.felix.framework.URLHandlersBundleURLConnection.getInputStream(URLHandlersBundleURLConnection.java:134)
> at java.net.URL.openStream(URL.java:1009)
> It is not allways reproducible. The first call causes the NPE and the second
> call with the same URL string goes without problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1032) NPE on URL#openStream()
[
https://issues.apache.org/jira/browse/FELIX-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697379#action_12697379
]
Richard S. Hall commented on FELIX-1032:
I think we need more information on this. What is the context of the situation?
Seems odd. I would think this would only happen if the bundle was refreshed and
the JAR was deleted.
How repeatable is this? Can you create a simple example that will eventually
demonstrate the issue?
> NPE on URL#openStream()
> ---
>
> Key: FELIX-1032
> URL: https://issues.apache.org/jira/browse/FELIX-1032
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: felix-1.4.1
> Environment: Linux bono 2.6.28-6-generic #17-Ubuntu SMP Fri Jan 30
> 15:34:36 UTC 2009 i686 GNU/Linux
> java version "1.6.0_13"
> Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
> Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
>Reporter: Martin Zdila
>Priority: Critical
>
> Note that also affected is felix-1.6.0 (it is not in the list).
> I am often getting NPE with the following code:
> new URL("bundle://66.0:0/somewhere/my.resource" /* or any other bundle:// URL
> */).openStream();
> java.lang.NullPointerException
> at java.util.zip.Inflater.ensureOpen(Inflater.java:336)
> at java.util.zip.Inflater.getBytesWritten(Inflater.java:296)
> at java.util.zip.ZipFile$1.available(ZipFile.java:243)
> at
> org.apache.felix.framework.URLHandlersBundleURLConnection.connect(URLHandlersBundleURLConnection.java:125)
> at
> org.apache.felix.framework.URLHandlersBundleURLConnection.getInputStream(URLHandlersBundleURLConnection.java:134)
> at java.net.URL.openStream(URL.java:1009)
> It is not allways reproducible. The first call causes the NPE and the second
> call with the same URL string goes without problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1012) Transactions in OSGi (RFC 98)
[ https://issues.apache.org/jira/browse/FELIX-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Clement Escoffier closed FELIX-1012. Resolution: Fixed I committed the contribution in the trunk. I just changed the version number to be 0.9.0-SNAPSHOT instead of 1.0.0-SNAPSHOT to release a 1.0.0 (sometimes). Thanks for the contribution ! Clement > Transactions in OSGi (RFC 98) > - > > Key: FELIX-1012 > URL: https://issues.apache.org/jira/browse/FELIX-1012 > Project: Felix > Issue Type: New Feature >Reporter: Guillaume Nodet > Attachments: FELIX-1012.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1010) add java annotation support to felix-scr-plugin
[
https://issues.apache.org/jira/browse/FELIX-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697069#action_12697069
]
David Jencks commented on FELIX-1010:
-
the xbean-reflect library might make reading the annotations very easy. (it
uses asm under the covers) It's used in (at least) openejb and geronimo for
this.
> add java annotation support to felix-scr-plugin
> ---
>
> Key: FELIX-1010
> URL: https://issues.apache.org/jira/browse/FELIX-1010
> Project: Felix
> Issue Type: New Feature
> Components: Maven SCR Plugin
>Affects Versions: maven-scr-plugin-1.0.10
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
> Fix For: maven-scr-plugin-1.0.11
>
> Attachments: 090329_felix_scrplugin_annotationsupport.patch,
> 090406_component_patch.patch
>
>
> goals of this proposal:
> - allow definition of SCR components with java annotations instead of QDox
> tags
> - advantages: strong typing, auto-completion and jump to source documentation
> in modern IDEs
> - support built-in annotations with 1:1 matching the old scr.* tags, and
> allow definition of custom annotations for other felix/scr-based projects to
> minimalize syntax overhead
> - the QDox tags are still supported, but cannot be mixed with annotations
> whithing the same source file
> attached to this ticket is a full implemented and tested patch, that supports
> all feates supported by the scr.* QDox tags today. some of the more "exotic"
> features are not tested in detail, only the generated descriptors where
> compared.
> i created a new project "scrplugin-annotations", that contains only the
> annotations for easy referencing without unwanted transitive dependencies.
> i'm not sure if the package and artifact name are well chosen.
> Example 1
> -
> QDox version:
> /**
> * Service class with QDox annotations.
> *
> * @scr.component
> * @scr.property name="testProperty" value="testValue"
> * @scr.service
> */
> public class MinimalServiceQDox implements {
> ...
> Annotation version:
> /**
> * Service class with java annotations.
> */
> @Component
> @Property(name = "testProperty", value = "testValue")
> @Service
> public class MinimalServiceAnnotations {
> ...
> Example 2
> -
> QDox version:
> /**
> * Service class with QDox annotations.
> *
> * @scr.component name="QDoxName" label="theLabel"
> description="theDescription"
> *immediate="false" enabled="false" factory="xx.yy.zz"
> * @scr.service interface="org.osgi.service.component.ComponentInstance"
> * servicefactory="true"
> * @scr.service interface="java.lang.Readable"
> * @scr.property name="stringProp" value="theValue" label="thePropLabel"
> * description="thePropDesc" options 0="option0" 1="option1"
> * 2="option2"
> * @scr.property name="intProp" value="5" type="Integer"
> * @scr.property name="multiProp" values.0="multiValue1"
> values.1="multiValue2"
> */
> public class ServiceQDox implements ComponentInstance, Readable {
> /**
> * @scr.reference cardinality=0..1, dynamic=true
> */
> MinimalServiceQDox reference;
> ...
> Annotation version:
> /**
> * Service class with java annotations.
> */
> @Component(name = "AnnotName", label = "theLabel", description =
> "theDescription", immediate = false, enabled = false, factory = "xx.yy.zz")
> @Services( { @Service(value = ComponentInstance.class, serviceFactory =
> true), @Service(Readable.class) })
> @Properties( {
> @Property(name = "stringProp", value = "theValue", label =
> "thePropLabel", description = "thePropDesc", options = {
> @PropertyOption(name = "0", value = "option0"),
> @PropertyOption(name = "1", value = "option1"),
> @PropertyOption(name = "2", value = "option2") }),
> @Property(name = "intProp", value = "5", type = Integer.class),
> @Property(name = "multiProp", value = { "multiValue1", "multiValue2"
> }) })
> public class ServiceAnnotations implements ComponentInstance, Readable {
> @Reference(cardinality = ReferenceCardinality.ZERO_TO_ONE, policy =
> ReferencePolicy.DYNAMIC)
> MinimalServiceAnnotations reference;
> ...
> Example 3 - using Custom Annotation from other project
> --
> QDox version:
> /**
> * Sample servlet with sling mappings.
> *
> * @scr.component immediate="true"
> * @scr.service interface="javax.servlet.Servlet"
> * @scr.property name="sling.servlet.methods" value="GET"
> * @scr.property name="sling.servlet.resourceTypes"
> * value="/apps/test/components/samplecomponent"
> * @scr.property name="sling.servlet.extensions" values.0="html"
> values.1="json"
> */
> public class SlingServletQDox impleme
[jira] Commented: (FELIX-1010) add java annotation support to felix-scr-plugin
[
https://issues.apache.org/jira/browse/FELIX-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697007#action_12697007
]
Carsten Ziegeler commented on FELIX-1010:
-
I think it would be possible to use ASM to read the annotations from the class
files (retention policy compile); I don't have enough time to implement this
atm, but it seems that this is the way to go.
> add java annotation support to felix-scr-plugin
> ---
>
> Key: FELIX-1010
> URL: https://issues.apache.org/jira/browse/FELIX-1010
> Project: Felix
> Issue Type: New Feature
> Components: Maven SCR Plugin
>Affects Versions: maven-scr-plugin-1.0.10
>Reporter: Stefan Seifert
>Assignee: Carsten Ziegeler
> Fix For: maven-scr-plugin-1.0.11
>
> Attachments: 090329_felix_scrplugin_annotationsupport.patch,
> 090406_component_patch.patch
>
>
> goals of this proposal:
> - allow definition of SCR components with java annotations instead of QDox
> tags
> - advantages: strong typing, auto-completion and jump to source documentation
> in modern IDEs
> - support built-in annotations with 1:1 matching the old scr.* tags, and
> allow definition of custom annotations for other felix/scr-based projects to
> minimalize syntax overhead
> - the QDox tags are still supported, but cannot be mixed with annotations
> whithing the same source file
> attached to this ticket is a full implemented and tested patch, that supports
> all feates supported by the scr.* QDox tags today. some of the more "exotic"
> features are not tested in detail, only the generated descriptors where
> compared.
> i created a new project "scrplugin-annotations", that contains only the
> annotations for easy referencing without unwanted transitive dependencies.
> i'm not sure if the package and artifact name are well chosen.
> Example 1
> -
> QDox version:
> /**
> * Service class with QDox annotations.
> *
> * @scr.component
> * @scr.property name="testProperty" value="testValue"
> * @scr.service
> */
> public class MinimalServiceQDox implements {
> ...
> Annotation version:
> /**
> * Service class with java annotations.
> */
> @Component
> @Property(name = "testProperty", value = "testValue")
> @Service
> public class MinimalServiceAnnotations {
> ...
> Example 2
> -
> QDox version:
> /**
> * Service class with QDox annotations.
> *
> * @scr.component name="QDoxName" label="theLabel"
> description="theDescription"
> *immediate="false" enabled="false" factory="xx.yy.zz"
> * @scr.service interface="org.osgi.service.component.ComponentInstance"
> * servicefactory="true"
> * @scr.service interface="java.lang.Readable"
> * @scr.property name="stringProp" value="theValue" label="thePropLabel"
> * description="thePropDesc" options 0="option0" 1="option1"
> * 2="option2"
> * @scr.property name="intProp" value="5" type="Integer"
> * @scr.property name="multiProp" values.0="multiValue1"
> values.1="multiValue2"
> */
> public class ServiceQDox implements ComponentInstance, Readable {
> /**
> * @scr.reference cardinality=0..1, dynamic=true
> */
> MinimalServiceQDox reference;
> ...
> Annotation version:
> /**
> * Service class with java annotations.
> */
> @Component(name = "AnnotName", label = "theLabel", description =
> "theDescription", immediate = false, enabled = false, factory = "xx.yy.zz")
> @Services( { @Service(value = ComponentInstance.class, serviceFactory =
> true), @Service(Readable.class) })
> @Properties( {
> @Property(name = "stringProp", value = "theValue", label =
> "thePropLabel", description = "thePropDesc", options = {
> @PropertyOption(name = "0", value = "option0"),
> @PropertyOption(name = "1", value = "option1"),
> @PropertyOption(name = "2", value = "option2") }),
> @Property(name = "intProp", value = "5", type = Integer.class),
> @Property(name = "multiProp", value = { "multiValue1", "multiValue2"
> }) })
> public class ServiceAnnotations implements ComponentInstance, Readable {
> @Reference(cardinality = ReferenceCardinality.ZERO_TO_ONE, policy =
> ReferencePolicy.DYNAMIC)
> MinimalServiceAnnotations reference;
> ...
> Example 3 - using Custom Annotation from other project
> --
> QDox version:
> /**
> * Sample servlet with sling mappings.
> *
> * @scr.component immediate="true"
> * @scr.service interface="javax.servlet.Servlet"
> * @scr.property name="sling.servlet.methods" value="GET"
> * @scr.property name="sling.servlet.resourceTypes"
> * value="/apps/test/components/samplecomponent"
> * @scr.property name="sling.servlet.extensions" values.0="html"
> values.1="j
[jira] Created: (FELIX-1032) NPE on URL#openStream()
NPE on URL#openStream()
---
Key: FELIX-1032
URL: https://issues.apache.org/jira/browse/FELIX-1032
Project: Felix
Issue Type: Bug
Components: Framework
Affects Versions: felix-1.4.1
Environment: Linux bono 2.6.28-6-generic #17-Ubuntu SMP Fri Jan 30
15:34:36 UTC 2009 i686 GNU/Linux
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
Reporter: Martin Zdila
Priority: Critical
Note that also affected is felix-1.6.0 (it is not in the list).
I am often getting NPE with the following code:
new URL("bundle://66.0:0/somewhere/my.resource" /* or any other bundle:// URL
*/).openStream();
java.lang.NullPointerException
at java.util.zip.Inflater.ensureOpen(Inflater.java:336)
at java.util.zip.Inflater.getBytesWritten(Inflater.java:296)
at java.util.zip.ZipFile$1.available(ZipFile.java:243)
at
org.apache.felix.framework.URLHandlersBundleURLConnection.connect(URLHandlersBundleURLConnection.java:125)
at
org.apache.felix.framework.URLHandlersBundleURLConnection.getInputStream(URLHandlersBundleURLConnection.java:134)
at java.net.URL.openStream(URL.java:1009)
It is not allways reproducible. The first call causes the NPE and the second
call with the same URL string goes without problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Used license in the notice file when the import is added on packaging
2009/4/8 Clement Escoffier > Hello, > > I have a strange case in my notice files. > > Imagine that you have a project. The code does not depends on the > org.osgi.* packages. > However, the binary of such project depends on these packages. the import > was added during the packaging process. > > Do I need to include the OSGi license as a used license ? > if the final artifact requires OSGi then I would say yes - then it's clear to end-users Regards, > > Clement > -- Cheers, Stuart
[jira] Closed: (FELIX-1028) NPE in configuration view when running webconsole with Equinox
[ https://issues.apache.org/jira/browse/FELIX-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Per Kristian Söreide closed FELIX-1028. --- > NPE in configuration view when running webconsole with Equinox > -- > > Key: FELIX-1028 > URL: https://issues.apache.org/jira/browse/FELIX-1028 > Project: Felix > Issue Type: Bug > Components: Framework, Web Console >Affects Versions: felix-1.4.1, webconsole-1.2.8 >Reporter: Per Kristian Söreide >Assignee: Carsten Ziegeler > Fix For: webconsole-1.2.10 > > > When using webconsole with Equinox, a NullPointerException is correctly > thrown from BundleContext.createFilter(String filter) when filer is null > (core spec 4.1 - 6.1.6.5). Felix throws an InvalidSyntaxException when filter > is null. > This causes an uncaught NullPointerException in the call to createFilter in > org.apache.felix.webconsole.internal.compendium.ConfigManager. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1028) NPE in configuration view when running webconsole with Equinox
[ https://issues.apache.org/jira/browse/FELIX-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696974#action_12696974 ] Per Kristian Söreide commented on FELIX-1028: - This works fine now! Thanks for the quick response! > NPE in configuration view when running webconsole with Equinox > -- > > Key: FELIX-1028 > URL: https://issues.apache.org/jira/browse/FELIX-1028 > Project: Felix > Issue Type: Bug > Components: Framework, Web Console >Affects Versions: felix-1.4.1, webconsole-1.2.8 >Reporter: Per Kristian Söreide >Assignee: Carsten Ziegeler > Fix For: webconsole-1.2.10 > > > When using webconsole with Equinox, a NullPointerException is correctly > thrown from BundleContext.createFilter(String filter) when filer is null > (core spec 4.1 - 6.1.6.5). Felix throws an InvalidSyntaxException when filter > is null. > This causes an uncaught NullPointerException in the call to createFilter in > org.apache.felix.webconsole.internal.compendium.ConfigManager. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT] [VOTE] Release of the dependency manager 2.0.1
Summarizing the votes: +1 Richard S. Hall, Felix Meschberger, Pierre de Rop (non binding), Karl Pauls, Arjun Panday (non binding), Stuart McCulloch, Carsten Ziegeler, Clement Escoffier no 0 or -1 votes. That means the release passes. I will proceed to upload the artifacts asap. Greetings, Marcel
Re: [VOTE] Move ServiceMix Kernel as Karaf subproject in Felix
On Mon, Apr 6, 2009 at 1:25 PM, Guillaume Nodet wrote: > This is a formal vote to move ServiceMix Kernel codebase into Felix as > Karaf subproject. > > [X ] +1 : move ServiceMix Kernel as Karaf subproject in Felix > [ ] -1 (not binding) i'm very keen to use karaf in james - robert
Re: [vote] Use Nexus repository infrastructure for snapshots/releases deployment
0 -> richard On 4/7/09 7:42 AM, Stuart McCulloch wrote: Hi everyone, I'd like to call a vote on using the Nexus repository infrastructure for deploying snapshots/releases of Apache Felix The proposed changes to the Felix parent pom can be found here: https://issues.apache.org/jira/browse/FELIX-1029 We'll also need to update our release docs to match (based on http://maven.apache.org/developers/release/releasing.html) So, WYDT? [ ] +1 Yes, use Nexus infrastructure for deploying snapshots/releases of Apache Felix [ ] -1 No, keep with the current release process (please provide specific comments)
Used license in the notice file when the import is added on packaging
Hello, I have a strange case in my notice files. Imagine that you have a project. The code does not depends on the org.osgi.* packages. However, the binary of such project depends on these packages. the import was added during the packaging process. Do I need to include the OSGi license as a used license ? Regards, Clement
[jira] Commented: (FELIX-1027) deadlock with felix 1.6.0 ?
[ https://issues.apache.org/jira/browse/FELIX-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696956#action_12696956 ] Richard S. Hall commented on FELIX-1027: Pierre, that sounds reasonable. I guess we will have to look into your example. > deadlock with felix 1.6.0 ? > --- > > Key: FELIX-1027 > URL: https://issues.apache.org/jira/browse/FELIX-1027 > Project: Felix > Issue Type: Bug > Components: Framework > Environment: jdk1.5, linux >Reporter: Pierre De Rop >Priority: Critical > Attachments: deadlock.txt, > deadlock_after_patch_FELIX_1027_20090406.log, FELIX_1027_20090406.txt, > test-deadlock.tgz > > > I just came across a deadlock with the felix 1.6.0 candidate version for the > next fwk version. > I have attached to this post the corresponding "kill -QUIT" output. > Richard, is it really an framework deadlock ? This is strange because I am > testing the trunk since one month and never noticed the problem ... > /pierre -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1027) deadlock with felix 1.6.0 ?
[ https://issues.apache.org/jira/browse/FELIX-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696954#action_12696954 ] Pierre De Rop commented on FELIX-1027: -- Yes Richard, I remember, and in the sample code, I think I don't have such race condition (though, I am now doubting ...) because: 1) the Updater always stops the bundle B, before upadting/refreshing it. 2) In B.stop(), I ensure all started threads to be properly joined, before returning from B.stop() method. 3) Morover, when I refresh, I always wait for the PACKAGES_REFRESHED event, before restarting B ... Did I miss something ? > deadlock with felix 1.6.0 ? > --- > > Key: FELIX-1027 > URL: https://issues.apache.org/jira/browse/FELIX-1027 > Project: Felix > Issue Type: Bug > Components: Framework > Environment: jdk1.5, linux >Reporter: Pierre De Rop >Priority: Critical > Attachments: deadlock.txt, > deadlock_after_patch_FELIX_1027_20090406.log, FELIX_1027_20090406.txt, > test-deadlock.tgz > > > I just came across a deadlock with the felix 1.6.0 candidate version for the > next fwk version. > I have attached to this post the corresponding "kill -QUIT" output. > Richard, is it really an framework deadlock ? This is strange because I am > testing the trunk since one month and never noticed the problem ... > /pierre -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Move ServiceMix Kernel as Karaf subproject in Felix
+1 -> richard On 4/6/09 8:25 AM, Guillaume Nodet wrote: This is a formal vote to move ServiceMix Kernel codebase into Felix as Karaf subproject. [ ] +1 : move ServiceMix Kernel as Karaf subproject in Felix [ ] -1 This vote will be closed on Friday morning. Here's my +1 (non binding)
[jira] Commented: (FELIX-1027) deadlock with felix 1.6.0 ?
[ https://issues.apache.org/jira/browse/FELIX-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696936#action_12696936 ] Richard S. Hall commented on FELIX-1027: Pierre, it seems that constantly updating/refreshing your bundles is always going to lead to such situations since you have a race condition between servicing the class load request and the JAR file being deleted from the file system due to a refresh. Remember that we do not try to perform any locking on a class load to hold a bundle JAR file in place because a) it would be too costly, b) the potential for deadlock would be great, and c) what's the point since if the bundle you depend on is being refreshed, then you are likely being refreshed too. You concern here seems to be based on the fact that you do not see these errors with the JVM option enabled, but perhaps that makes some sense since it leads to more concurrency, which then exposes this race condition. Just a thought. > deadlock with felix 1.6.0 ? > --- > > Key: FELIX-1027 > URL: https://issues.apache.org/jira/browse/FELIX-1027 > Project: Felix > Issue Type: Bug > Components: Framework > Environment: jdk1.5, linux >Reporter: Pierre De Rop >Priority: Critical > Attachments: deadlock.txt, > deadlock_after_patch_FELIX_1027_20090406.log, FELIX_1027_20090406.txt, > test-deadlock.tgz > > > I just came across a deadlock with the felix 1.6.0 candidate version for the > next fwk version. > I have attached to this post the corresponding "kill -QUIT" output. > Richard, is it really an framework deadlock ? This is strange because I am > testing the trunk since one month and never noticed the problem ... > /pierre -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (FELIX-1027) deadlock with felix 1.6.0 ?
[ https://issues.apache.org/jira/browse/FELIX-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart McCulloch reopened FELIX-1027: - Re-opening so we (ie. either me/Karl/Richard) can do further investigation > deadlock with felix 1.6.0 ? > --- > > Key: FELIX-1027 > URL: https://issues.apache.org/jira/browse/FELIX-1027 > Project: Felix > Issue Type: Bug > Components: Framework > Environment: jdk1.5, linux >Reporter: Pierre De Rop >Priority: Critical > Attachments: deadlock.txt, > deadlock_after_patch_FELIX_1027_20090406.log, FELIX_1027_20090406.txt, > test-deadlock.tgz > > > I just came across a deadlock with the felix 1.6.0 candidate version for the > next fwk version. > I have attached to this post the corresponding "kill -QUIT" output. > Richard, is it really an framework deadlock ? This is strange because I am > testing the trunk since one month and never noticed the problem ... > /pierre -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
