Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <677507709.292721266300747976.JavaMail.jira@brutus.apache.org>
Date: Tue, 16 Feb 2010 06:12:27 +0000 (UTC)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-2080) Updating bundles when debugging
 switched on might result in a deadlock with 100% CPU usage
In-Reply-To: <549816992.281351266250767930.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834095#action_12834095 ] 

Richard S. Hall commented on FELIX-2080:
----------------------------------------

Perhaps the issue is our bundles are not actually the same, I notice my file names are different than your. I just downloaded mine from the SpringSource bundle repository:

    http://www.springsource.com/repository/app/

Mine are called:

    org.springframework.beans-3.0.0.RELEASE.jar
    org.springframework.context-3.0.0.RELEASE.jar
    org.springframework.core-3.0.0.RELEASE.jar
    org.springframework.aop-3.0.0.RELEASE.jar	
    org.springframework.web-3.0.0.RELEASE.jar

Yours are called:

    spring-beans-3.0.0.RELEASE.jar 
    spring-context-3.0.0.RELEASE.jar
    spring-core-3.0.0.RELEASE.jar
    spring-aop-3.0.0.RELEASE.jar
    spring-web-3.0.0.RELEASE.jar

Where do I get the ones you are using?

> Updating bundles when debugging switched on might result in a deadlock with 100% CPU usage
> ------------------------------------------------------------------------------------------
>
>                 Key: FELIX-2080
>                 URL: https://issues.apache.org/jira/browse/FELIX-2080
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: felix-2.0.3
>            Reporter: Roland Huss
>
> With the following minimal scenario using Spring 3.0.0.RELEASE bundles the following happen when one update spring-core first and the spring-web:
> $ grep log conf/config.properties
> felix.log.level=4
> $ ls bundle/
> com.springsource.javax.servlet-2.4.0.jar               org.apache.felix.shell-1.4.2.jar      spring-context-3.0.0.RELEASE.jar
> com.springsource.org.aopalliance-1.0.0.jar             org.apache.felix.shell.tui-1.4.1.jar  spring-core-3.0.0.RELEASE.jar
> com.springsource.org.apache.commons.logging-1.1.1.jar  spring-aop-3.0.0.RELEASE.jar          spring-web-3.0.0.RELEASE.jar
> org.apache.felix.bundlerepository-1.4.3.jar            spring-beans-3.0.0.RELEASE.jar
> $ java -jar bin/felix.jar
> ....
> -> ps
> START LEVEL 1
>    ID   State         Level  Name
> [   0] [Active     ] [    0] System Bundle (2.0.3)
> [   1] [Active     ] [    1] Java Servlet API (2.4.0)
> [   2] [Active     ] [    1] AOP Alliance API (1.0.0)
> [   3] [Active     ] [    1] Apache Commons Logging (1.1.1)
> [   4] [Active     ] [    1] Apache Felix Bundle Repository (1.4.3)
> [   5] [Active     ] [    1] Apache Felix Shell Service (1.4.2)
> [   6] [Active     ] [    1] Apache Felix Shell TUI (1.4.1)
> [   7] [Active     ] [    1] Spring AOP (3.0.0.RELEASE)
> [   8] [Active     ] [    1] Spring Beans (3.0.0.RELEASE)
> [   9] [Active     ] [    1] Spring Context (3.0.0.RELEASE)
> [  10] [Active     ] [    1] Spring Core (3.0.0.RELEASE)
> [  11] [Active     ] [    1] Spring Web (3.0.0.RELEASE)
> -> update 10
> DEBUG: WIRE: 10.1 -> org.apache.commons.logging -> 3.0
> DEBUG: WIRE: 10.1 -> javax.xml.transform.stax -> 0
> DEBUG: WIRE: 10.1 -> javax.xml.stream.events -> 0
> DEBUG: WIRE: 10.1 -> org.w3c.dom -> 0
> DEBUG: WIRE: 10.1 -> org.xml.sax -> 0
> DEBUG: WIRE: 10.1 -> javax.xml.namespace -> 0
> DEBUG: WIRE: 10.1 -> javax.xml.stream -> 0
> DEBUG: WIRE: 10.1 -> javax.xml.stream.util -> 0
> DEBUG: WIRE: 10.1 -> org.xml.sax.ext -> 0
> DEBUG: WIRE: 10.1 -> javax.xml.transform -> 0
> DEBUG: WIRE: 10.1 -> javax.xml.transform.sax -> 0
> DEBUG: WIRE: 10.1 -> org.xml.sax.helpers -> 0
> -> update 11
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.1] and org.springframework.core from [10.0]
> DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core from [10.0] and org.springframework.core from [10.1]
> .....
> and so on ...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.