I’m not surprised. My plan for the socket appender is to look at leveraging
Netty. I believe it handles all of what I want to do really well.
Ralph
> On Nov 6, 2018, at 4:38 PM, Gary Gregory wrote:
>
> On Tue, Nov 6, 2018 at 4:10 PM Remko Popma wrote:
>
>> It may be wise to always include so
On Tue, Nov 6, 2018 at 4:10 PM Remko Popma wrote:
> It may be wise to always include some (configurable) backoff mechanism, to
> prevent our failover/reconnect logic from essentially initiating a denial
> of service attack when the service appears to be unavailable.
>
> Not sure if we currently h
Sorry, still haven’t had time to look at this.
(Shameless plug) Every java main() method deserves http://picocli.info
> On Nov 6, 2018, at 11:20, Gary Gregory wrote:
>
>> On Tue, Oct 30, 2018 at 7:08 PM Gary Gregory wrote:
>>
>>> On Mon, Oct 22, 2018 at 5:40 PM Remko Popma wrote:
>>>
>>> I
It may be wise to always include some (configurable) backoff mechanism, to
prevent our failover/reconnect logic from essentially initiating a denial of
service attack when the service appears to be unavailable.
Not sure if we currently have this anywhere, but if we’re thinking to extract
some
It would be helpful if we could implement failover and retrial in a
way that is compatible with disabling immediate flush. The current
implementations may surface a failure to the attempt to log an end of
batch, but don't provide a mechanism to retry queued or buffered
events.
On Tue, Nov 6, 2018
On Tue, Nov 6, 2018 at 11:19 AM Ralph Goers
wrote:
> The socket appender already has the ability to reconnect. It just needs to
> ability to load balance or send to an alternate host if the connection
> fails.
>
Sure, I just would like reconnection and failover to be abstracted in our
core frame
The socket appender already has the ability to reconnect. It just needs to
ability to load balance or send to an alternate host if the connection fails.
Ralph
> On Nov 6, 2018, at 11:15 AM, Gary Gregory wrote:
>
> Speaking of failover kind of things, the JMS Appender has a reconnect
> feature
Speaking of failover kind of things, the JMS Appender has a reconnect
feature and I am wrapping up a similar feature for the JDBC Appender. This
kind of feature is a MUST for services that need to stay up and running for
longer periods of time.
It would be nice to have a reconnect feature abstract
Oops, never mind, this is the -rc2 vote thread. Matt created an -rc3
vote thread already. Apologies for the noise.
On Tue, Nov 6, 2018 at 10:16 AM Raman Gupta wrote:
>
> I think Matt forgot to update the list... as far as I can tell, the
> source zip is ok now, thanks Matt.
> On Sat, Nov 3, 2018 a
I think Matt forgot to update the list... as far as I can tell, the
source zip is ok now, thanks Matt.
On Sat, Nov 3, 2018 at 3:44 PM Matt Sicker wrote:
>
> Whoops, not sure how I missed that. Let me try again.
>
> On Sat, 3 Nov 2018 at 13:25, Ralph Goers wrote:
>
> > -1
> >
> > The source zip is
Hello all,
thanks for integrating this pull request.
Any chance that someone reviews my other pull request
https://github.com/apache/logging-log4j2/pull/224 that fixes
https://issues.apache.org/jira/browse/LOG4J2-2403 and hopefully integrate
it as well?
Best regards
Marco
On Sun, Nov 04, 2018
11 matches
Mail list logo
