geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-3257) gbean dependencies should be started after collection references are updated
Date Sat, 23 Jun 2007 17:52:25 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks closed GERONIMO-3257.
----------------------------------

    Resolution: Fixed

Seems to work... rev 550068.

> gbean dependencies should be started after collection references are updated
> ----------------------------------------------------------------------------
>
>                 Key: GERONIMO-3257
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3257
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: kernel
>    Affects Versions: 2.0-M6
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.0-M7
>
>
> Some excellent debugging by jgawor revealed that JettyFilterMapping was often getting
started before all the servlets it depends on are started.  This was causing filters to sometimes
not get applied to the correct servlets.  
> JettyModuleBuilder is adding a dependency for each servlet gbean to the filter mapping
gbean, so the filter mapping wont start until after all the servlets expected to be in the
collection are started.  However, the "dependency" notification is getting fired before the
"add to reference collection" notification, so the collections of servlets is not always correct.
> I think we can put some more ordering into the system so that all the reference collections
are updated before dependencies are notified.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message