[jira] Closed: (NANO-49) [pool] testClearPool fails with CurrentModificationException

jira-yCVjj/[email protected] Mon, 26 Apr 2004 17:24:03 -0400 (EDT)
Newsgroups gmane.comp.java.nanocontainer.devel
Message-ID <[email protected]>
Message:

   The following issue has been closed.

   Resolver: Joerg Schaible
       Date: Mon, 26 Apr 2004 5:22 PM

Applied.
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=NANO-49

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: NANO-49
    Summary: [pool] testClearPool fails with CurrentModificationException
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: NanoContainer
 Components: 
             pool
   Versions:
             1.0-beta-1

   Assignee: 
   Reporter: Joerg Schaible

    Created: Mon, 9 Feb 2004 7:48 PM
    Updated: Mon, 26 Apr 2004 5:22 PM
Environment: Gentoo Linux, Blackdown JDK 1.4.1

Description:
The fixture testClearPool of pool 1 fails with CurrentModificationException. I did not look further into it, so I can't say if it is a problem of the test or any side effect. So for now, just the report:

=== snip ===
Testsuite: org.nanocontainer.pool.PicoPoolTestCase
Tests run: 9, Failures: 0, Errors: 1, Time elapsed: 2,125 sec

Testcase: testCreatePoolWithPico took 0,044 sec
Testcase: testFailOnExhaust took 0,001 sec
Testcase: testBlockExpiryOnExhaust took 1,033 sec
Testcase: testBlockOnExhaust took 1,004 sec
Testcase: testGrowOnExhaust took 0,001 sec
Testcase: testDependantPoolObject took 0,001 sec
Testcase: testPoolObjectVisibility took 0,001 sec
Testcase: testClearPool took 0,005 sec
	Caused an ERROR
null
java.util.ConcurrentModificationException
	at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:448)
	at java.util.AbstractList$Itr.next(AbstractList.java:419)
	at java.util.Collections$1.next(Collections.java:996)
	at org.nanocontainer.pool.DefaultPicoPool.clearPool(DefaultPicoPool.java:294)
	at org.nanocontainer.pool.PicoPoolTestCase.testClearPool(PicoPoolTestCase.java:226)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:232)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
	at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
	at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
	at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
	at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:128)
	at com.werken.werkz.Goal.fire(Goal.java:639)
	at com.werken.werkz.Goal.attain(Goal.java:575)
	at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
	at com.werken.werkz.Goal.attain(Goal.java:573)
	at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:448)
	at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348)
	at org.apache.maven.cli.App.doMain(App.java:543)
	at org.apache.maven.cli.App.main(App.java:1109)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at com.werken.forehead.Forehead.run(Forehead.java:551)
	at com.werken.forehead.Forehead.main(Forehead.java:581)

Testcase: testClearPoolTestcase: testPoolComponentAdapter took 0,011 sec
=== snap ===


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira