it to reconfigure using the new location.
Ralph
> On Oct 17, 2022, at 6:03 AM, Joan ventusproxy
> wrote:
>
> Hello,
>
> Solved ... I don't exactly understand why ... but solved.
>
> I had to change my code in this way. Instead of:
> System.setProperty("lo
quot;);
Now is:
LoggerContext context = (LoggerContext) LogManager.getContext(false);
context.setConfigLocation("/opt/ventusproxy/app/proxy/ROOT/WEB-INF/log4j.xml");
this.systemLog = context.getLogger("LOGGER_SYSTEM");
Thanks,
Joan.
-Original Message-
From: Joan ve
lectorNamed
true
log4jContextName
ventusproxy
Thanks,
Joan.
-Original Message-
From: Joan ventusproxy
Sent: Sunday, October 16, 2022 9:03 PM
To: 'Log4J Users List'
Subject: RE: Issue after moving to log4j 2.19
Is not this? (second gist):
DEBUG StatusLogger Wa
. It is ending up using the default configuration.
Ralph
> On Oct 15, 2022, at 3:45 PM, Joan ventusproxy
> wrote:
>
> Hi Piotr,
>
> Thanks for your quick response.
>
> Below two gists with the traces for both cases:
>
> 1. Using "this.systemLog =
Hi Piotr,
Thanks for your quick response.
Below two gists with the traces for both cases:
1. Using "this.systemLog = LogManager.getLogger("LOGGER_SYSTEM");":
Hello,
�
We have moved to log4j 2.19.0 from log4j 2.17.2. Our environment is Centos9
stream with tomcat 8.5.83 and jdk11. After doing that, logging has stopped
working (the code related to log4j2 has not been changed for years)
�
All our loggers are asynchronous by adding:
Hi,
Sorry, I’m using http async client 4.1.4.
Thanks,
Joan.
From: Joan grupoventus
Sent: Friday, January 8, 2021 4:57 PM
To: 'Joan ventusproxy'
Subject: Response buffer size
Hello,
I’m using HttpClient 4.5.7. reading responses from a backend through a
‘HttpAsyncResponseConsumer
Hello,
Tomcat 8.5.55 (also tried with 8.5.37).
Similar to “Bug 62614 - Async servlet over HTTP/2 WriteListener does not work
because onWritePossible is never called back again” but using NIO connector:
I’m unable to create an example that reproduces this issue. So I will explain
what’s
Hello,
�
I’m using the following pattern to log lines:
%m%d{-MM-dd HH:mm:ss.SSS}%n
�
And writing the line with: this.accessLog.info(variable)
�
I was wondering if there is any chance to get the timestamp printed in the line
(%d{-MM-dd HH:mm:ss.SSS}) after writing it to the file
Hi Ralph,
Is this a bug definitely? Do you want I open an issue?
Thanks,
Joan.
-Original Message-
From: Joan ventusproxy
Sent: Tuesday, February 11, 2020 7:36 PM
To: 'Log4J Users List'
Subject: RE: Wrong extensions when rotating files using RollingRandomAccessFile
. It doesn’t look
correct. Is it possible you could test with 2.13.0 just to rule out that it
might have already been fixed?
Ralph
> On Feb 11, 2020, at 9:30 AM, Joan ventusproxy
> wrote:
>
> Hi Ralph,
>
> Do you think this is a bug or a misconfiguration on my side?
>
Hi Ralph,
Do you think this is a bug or a misconfiguration on my side?
Thanks,
Joan.
-Original Message-
From: Joan ventusproxy
Sent: Thursday, February 6, 2020 6:21 PM
To: 'Log4J Users List'
Subject: RE: Wrong extensions when rotating files using RollingRandomAccessFile
add status=DEBUG to the configuration element you will see logs appear
in stdout that identify some things that are useful for debugging issues during
rollover. Could you provide that please?
Ralph
> On Feb 5, 2020, at 9:50 AM, Joan ventusproxy
> wrote:
>
> Hello,
>
> We
Hello,
We have 5 async logs in our log4j2 configuration that rotates every day at
00:01. This is the config for one of them:
%m%d{HH:mm:ss.SSS}%n
So at 5 Feb 00:01 we expected to have 5 logs with the '2020-02-04' extension,
but we see files with '2020-02-05'
Hello,
�
We are having an issue with HttpClient 5 beta4 / HttpCore 5 Beta7 and socket
timeout after switching from asyncClient 1.3.
�
Our requests have a response timeout of 4 seconds. When a response timeout
occurs we see this in our log:
2019-05-27 13:05:35 � � � � [62.73.191.161]
15 matches
Mail list logo
