You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2010/02/16 07:06:27 UTC
[jira] Commented: (FELIX-2080) Updating bundles when debugging
switched on might result in a deadlock with 100% CPU usage
[ https://issues.apache.org/jira/browse/FELIX-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834093#action_12834093 ]
Richard S. Hall commented on FELIX-2080:
----------------------------------------
I was excited to see this bug because we need such "simple" problematic use cases to help us debug the current resolver and/or test our coming new resolver. Unfortunately, I seem to be missing something or perhaps there is a step you are forgetting:
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (2.0.3)
[ 1] [Active ] [ 1] Apache Felix Bundle Repository (1.4.3)
[ 2] [Active ] [ 1] Apache Felix Shell Service (1.4.2)
[ 3] [Active ] [ 1] Apache Felix Shell TUI (1.4.1)
[ 4] [Active ] [ 1] Java Servlet API (2.4.0)
[ 5] [Active ] [ 1] AOP Alliance API (1.0.0)
[ 6] [Active ] [ 1] Apache Commons Logging (1.1.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.xml.sax -> 0
DEBUG: WIRE: 10.1 -> javax.xml.namespace -> 0
DEBUG: WIRE: 10.1 -> org.w3c.dom -> 0
DEBUG: WIRE: 10.1 -> org.apache.commons.logging -> 6.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.ext -> 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.io from [10.1] and org.springframework.core.io from [10.0]
DEBUG: Constraint violation for 11.0 detected; module can see org.springframework.core.io from [10.0] and org.springframework.core.io from [10.1]
...SNIP...
DEBUG: WIRE: 11.0 -> javax.servlet.http -> 4.0
DEBUG: WIRE: 11.0 -> javax.xml.namespace -> 0
DEBUG: WIRE: 11.0 -> javax.xml.transform -> 0
DEBUG: WIRE: 11.0 -> javax.servlet -> 4.0
...SNIP...
-> ps
START LEVEL 1
ID State Level Name
[ 0] [Active ] [ 0] System Bundle (2.0.3)
[ 1] [Active ] [ 1] Apache Felix Bundle Repository (1.4.3)
[ 2] [Active ] [ 1] Apache Felix Shell Service (1.4.2)
[ 3] [Active ] [ 1] Apache Felix Shell TUI (1.4.1)
[ 4] [Active ] [ 1] Java Servlet API (2.4.0)
[ 5] [Active ] [ 1] AOP Alliance API (1.0.0)
[ 6] [Active ] [ 1] Apache Commons Logging (1.1.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)
->
Notice that I did get constraint violations, but it still finished quickly. One difference I can see is that when I do "update 10", I don't get as many resulting wires as you, not sure why that'd be the case.
Any help to reproduce this would be greatly appreciated. Thanks!
> 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.