Hi, the Felix event admin by default blacklists event handlers if they take more than 5 secs. With the setting you mentioned, you turn off the timeout for all event handlers.
If you want a more fine grained setting, you can use the property org.apache.felix.eventadmin.IgnoreTimeout to disable timeout handling for specific handlers or java packages (see http://felix.apache.org/site/apache-felix-event-admin.html) I assume the Equinox implementation does no blacklisting by default Carsten 2012/1/25 jerome moliere <jerome.moli...@gmail.com>: > I'll try a test with the following property setted to 0 : > org.apache.felix.eventadmin.Timeout > I'll let you know results of such experiments > > regards > J.MOLIERE - Mentor/J > auteur Eyrolles > blog: http://romjethoughts.blogspot.com > > > > > 2012/1/25 jerome moliere <jerome.moli...@gmail.com>: >> Hi all, >> I 've one part of my application that used equinox to run with a >> Tomcat 6 and Spring-DM, it was really very clever so I dropped all >> this stuff and replaced all this spaghetti plate with a simple felix >> with jetty http service. >> This works excepted that for the case where a servlet declaares itself >> (in one activator) as a consumer for events coming on a topic.... >> I 'm using eventadmin 1.2.14 version... >> It seems (I've got some logs) that emitter from the event is >> blacklisted by the EventAdmin service (due to timeout) >> I don't understand why this works at 100% cases with equinox and fails >> in 100% cases with Felix ? >> I watched the source code and I've seen the culprit with >> BlackListingHandlerTasks class ... >> What can I do to avoid this ? Can I use some magic config to shunt >> this mecanism ? Can I prevent this module to blacklist a bundle ? >> >> Thanks for your help >> any tip is wlecome >> J.MOLIERE - Mentor/J >> auteur Eyrolles >> blog: http://romjethoughts.blogspot.com -- Carsten Ziegeler cziege...@apache.org
