The following issue has been updated:
Updater: Ben Griffiths (mailto:[EMAIL PROTECTED])
Date: Wed, 28 Jul 2004 8:51 AM
Comment:
Now subtracts the number of instances already existing. Calls to pico.getComponent()
have been synchronized to avoid CyclicDependencyException. I think this relates to
this picocontainer issue: http://jira.codehaus.org/browse/PICO-190 - it's noted that
"CyclicDependency usually only occur in testing/development" so I suspect there's no
need to synchronize access throughout the codebase.
Changes:
Attachment changed to TestInterceptorAdaptor.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JS2-60?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JS2-60
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JS2-60
Summary: TestInterceptorAdapter.testThreadLocalDelegation() sometimes fails
Type: Bug
Status: Unassigned
Priority: Major
Project: Jetspeed 2
Versions:
2.0-a1
Assignee:
Reporter: Ate Douma
Created: Fri, 28 May 2004 5:45 AM
Updated: Wed, 28 Jul 2004 8:51 AM
Environment: Windows XP, J2SE1.4.2_03, maven 1.0-rc2
Description:
I've had now twice today that components/cm
org.apache.jetspeed.components.TestInterceptorAdapter.testThreadLocalDelegation()
suddenly fails.
Test report message:
Testcase:
testThreadLocalDelegation(org.apache.jetspeed.components.TestInterceptorAdapter):
FAILED
expected:<3> but was:<4>
junit.framework.AssertionFailedError: expected:<3> but was:<4>
at
org.apache.jetspeed.components.TestInterceptorAdapter.testThreadLocalDelegation(TestInterceptorAdapter.java:137)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
When I run it again the problem is gone.
I expect this is a timing issue. I haven't looked deep into it though.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
