Re: Event admin blacklisting?

[Markus Rathgeb <ma...@gmail.com>]

AFAIK there is also "org.apache.felix.eventadmin.Timeout=0" to disable the
timeout handling at all.

Another approach would be that your event handlers only take the event and
add it to a blocking queue (e.g. LinkedBlockingDeque).
You could use another thread that handles the elements added to that queue.
I assume in that case you return very fast.

At leat we don't see any blacklisting anymore (without the timeout=0 option
but with delegation the event handling to a separate thread).

Am Mi., 20. Juni 2018 um 18:36 Uhr schrieb Leschke, Scott <
SLeschke@medline.com>:

> I’m still having some issues with this.  I have a 2 (maybe 3) event
> handlers in my app and I’ve recently started having blacklist issues.  I
> don’t know what’s causing it since the handlers themselves haven’t changed
> and should run very quickly, probably under a 10 millis or so in most cases.
>
>
>
> Anyway, per Ben Graf’s response below, I updated  file
> org.apache.felix.eventadmin.impl.EventAdmin.cfg with the following line:
>
>
>
> org.apache.felix.eventadmin.IgnoreTimeout=com.medline.*
>
>
>
> Given the description of the property, I expected this to cover all the
> event handlers in my app but I’m still seeing at least one of the handlers
> get blacklisted.  Is the syntax wrong or are there any other
> recommendations regarding this?
>
>
>
> Thanks in advance,
>
> Scott
>
>
>
> *From:* Benjamin Graf [mailto:benjamin.graf@gmx.net]
> *Sent:* Wednesday, June 13, 2018 11:16 AM
> *To:* user@karaf.apache.org
> *Subject:* Re: Event admin blacklisting?
>
> Hi Scott,
>
> timeout for blacklisting is 5000ms. (see
>
> http://felix.apache.org/documentation/subprojects/apache-felix-event-admin.html
> )
>
> Regards
>
> Benjamin
>
>
> Am 13.06.2018 um 17:41 schrieb Leschke, Scott:
> >  I'm having an issue where events sto
>
>
>