jeanbza commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2985370633
Howdy. We ran into this, or something very similar to this, today. We're
using `ConsoleAppender`.
Our disk was 100% full at the time, which I think is related? Here's p
bharathchandrathakkallapally-cpi commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2042616999
sorry, the object `0x7f7ea87c4000` only appeared once in the dump, and
it is with the "http-nio-8080-exec-123" thread .
--
This is an automate
bharathchandrathakkallapally-cpi commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2042613196
@ppkarwasz
It appeared in the stacktrace of another thread, that is trace is pointing
to a line in the code, but that line or method the thread is
ppkarwasz commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2042579641
@bharathchandrathakkallapally-cpi,
Any idea what kind of object `0x7f7ea87c4000` might be? Does it appear
in the stacktraces of other threads?
--
This is an au
bharathchandrathakkallapally-cpi commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2042573768
@ppkarwasz here is the data your are asking
```
"http-nio-8080-exec-123" #2723 daemon prio=5 os_prio=0
tid=0x7f7e94095800 nid=0x34a8f waitin
ppkarwasz commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2042086722
I think that the crucial information that is missing here, is what is thread
`http-nio-8080-exec-123` waiting for. The lock on `RollingFileManager` should
be the last one r
bharathchandrathakkallapally-cpi commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2041407219
@tcmot yes, all the servers in the cluster are facing this issue. There is
no problem with the hard drive or IO, we had the AWS guy checked our quota
tcmot commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2041371880
Are all servers like this? Is there a problem with the hard drive? If there
is no deadlock, it is likely that data cannot be written to the hard drive.
@bharathchandrath
bharathchandrathakkallapally-cpi commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2041354023
@tcmot according the thread dump analysis we did, there is no deadlock.
@jvz If it is related to the rollover, this issue should be only seen a
jvz commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2040314637
Does this deadlock coincide with the hourly log file rollover you
configured? I wonder if there's a race condition here between incoming log
events and the rollover process.
--
tcmot commented on issue #2447:
URL:
https://github.com/apache/logging-log4j2/issues/2447#issuecomment-2039705734
I think this is a deadlock.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
bharathchandrathakkallapally-cpi opened a new issue, #2447:
URL: https://github.com/apache/logging-log4j2/issues/2447
## Description
We are using the RollingFileAppender with below configuration
```
appender.file.type=RollingFile
appender.file.name=LOGFILE
appender.file.fileNa
12 matches
Mail list logo
