[
http://jira.amdatu.org/jira/browse/AMDATU-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10443#comment-10443
]
Ivo Ladage - van Doorn commented on AMDATU-189:
-----------------------------------------------
After discussion with Angelo our conclusion was that the dependency with the
filebasedconfig bundle should be removed and configuration entries should be
provided by the integration test itself. Doing this, I found another issue in
the JSP servlet registration.
The problem is as follows;
The resource provider listener in the JSP bundle listens whiteboard style to
available ResourceProviders. So it has an optional dependency on this interface
with callback methods onAdded and onRemoved. In the onAdded the JSP servlet is
registered, in the onRemoved the JSP servlet is unregistered. The destroy also
unregisters these JSP servlets, since the service itself might be stopped
before the ResourceProviders are.
Now this causes a concurrency issue: onAdded and destroy may be invoked
concurrent. So while registration of a new JSP servlet, the service holding the
httpcontent on which that servlet should be registered is destroyed.
> Random failures for filter/jsp integration test
> -----------------------------------------------
>
> Key: AMDATU-189
> URL: http://jira.amdatu.org/jira/browse/AMDATU-189
> Project: Amdatu
> Issue Type: Bug
> Components: Testing
> Affects Versions: 0.0.6
> Reporter: Bram de Kruijff
> Assignee: Ivo Ladage - van Doorn
> Priority: Blocker
> Fix For: 0.0.6
>
>
> I got a buildfailure on the testFilter integration test after a commit that
> AFAIK totally unrelated. Looking at bamboo it seems this happens every now
> and then:
> http://bamboo.amdatu.org/bamboo/browse/AMDATU-TRUNK/test/case/2719767
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
