[
https://issues.apache.org/jira/browse/OPENJPA-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014187#comment-13014187
]
Rick Curtis commented on OPENJPA-1970:
--------------------------------------
Ravi -
If the test fails and causes the build to hang... don't we want that to happen?
A test that isn't run doesn't really test much.
I see that this problem was only observed on 1.1.x, but did you try to recreate
this problem on trunk?
Thanks,
Rick
> CPU spinning forever at TreeMap.get in Schema.java
> ---------------------------------------------------
>
> Key: OPENJPA-1970
> URL: https://issues.apache.org/jira/browse/OPENJPA-1970
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.1.1
> Environment: openJPA 1.1.x
> Reporter: Ravi P Palacherla
> Assignee: Ravi P Palacherla
> Fix For: 1.1.1
>
> Attachments: OPENJPA-1970.diff
>
>
> CPU is spinning forever at TreeMap.get in schema.java.
> The reason found to be because of structural modification of treemap outside
> a synchronized block.
> Synchronizing the treemap is fixing the issue.
> The issue can be reproduced with an openJPA test case but due to the nature
> of the problem, it is replicable intermittently on dual core machine.
> Attached patch has the test case and also the test case is ignored in default
> runs because it will cause the tests to stuck at TreeMap.get.
> This is seen in 1.1.x version of openJPA and hence uploading the patch only
> for that version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
