If you look at the stacktraces, I sent in my previous mails, you see, that the
order, in which the
filters are called, is right:
When receiving:
...
at
org.apache.mina.filter.ssl.SslHandler.flushScheduledEvents(SslHandler.java:310)
<--- SslFilter
at
Le 11/02/16 10:10, Norbert Irmer a écrit :
> If you look at the stacktraces, I sent in my previous mails, you see, that
> the order, in which the
> filters are called, is right:
>
> When receiving:
>
> ...
> at
> org.apache.mina.filter.ssl.SslHandler.flushScheduledEvents(SslHandler.java:310)
>
> The new version I have put on http://people.apache.org/~elecharny should
> solve the problem : instead of getting the lock whe we enter in the
> flushScheduledEvents() event, we exit immediately, doing nothing but
> incrementing the number of scheduled-events, instead of getting the
> lock.
Le 11/02/16 17:38, Norbert Irmer a écrit :
>
>> The new version I have put on http://people.apache.org/~elecharny should
>> solve the problem : instead of getting the lock whe we enter in the
>> flushScheduledEvents() event, we exit immediately, doing nothing but
>> incrementing the number of
Hello everyone!
I hope this email finds you well. I hope everyone is as excited about
ApacheCon as I am!
I'd like to remind you all of a couple of important dates, as well as ask for
your assistance in spreading the word! Please use your social media platform(s)
to get the word out! The more
Hello everyone!
I hope this email finds you well. I hope everyone is as excited about
ApacheCon as I am!
I'd like to remind you all of a couple of important dates, as well as ask for
your assistance in spreading the word! Please use your social media platform(s)
to get the word out! The more
