You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ppkarwasz (via GitHub)" <gi...@apache.org> on 2023/03/05 18:36:01 UTC
[I] `JeroMqAppenderTest` timeouts (logging-log4j2)
ppkarwasz opened a new issue, #1342:
URL: https://github.com/apache/logging-log4j2/issues/1342
The `JeroMqAppenderTest` timeouts every other CI run on Windows.
This might be a problem with the runner's resources (TCP port), some race condition in the test, but it can be also a problem in the `JeroMqAppender`.
--
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 specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `JeroMqAppenderTest` timeouts (logging-log4j2)
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #1342:
URL: https://github.com/apache/logging-log4j2/issues/1342#issuecomment-1980368449
The `JeroMqAppenderTest` is misbehaving again on Windows.
The relevant failure is:
```
2024-03-06T08:10:26.616Z main ERROR Test `testMultiThreadedServer(JeroMqAppender, LoggerContext)` has failed, dumping sta
tus data... org.opentest4j.AssertionFailedError: expected: <20> but was: <19>
at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:531)
at org.apache.logging.log4j.core.appender.mom.jeromq.JeroMqAppenderTest.testMultiThreadedServer(JeroMqAppenderTest.java:136)
```
The status logger gives the following messages:
```
2024-03-06T08:10:26.208Z main INFO Starting ZMonitor for JeroMqAppender JeroMQAppender.
2024-03-06T08:10:26.208Z pool-4-thread-1 INFO Starting JeroMqTestClient.
2024-03-06T08:10:26.208Z pool-4-thread-1 INFO Subscribing JeroMqTestClient to JeroMqAppender.
2024-03-06T08:10:26.318Z awaitility-thread INFO JeroMqAppender received an event of type ZEvent [type=HANDSHAKE_PROTOCOL, code=32768, address=tcp://0.0.0.0:56729, value=3]
2024-03-06T08:10:26.318Z pool-5-thread-1 INFO JeroMqAppender sent a message: Hello (0).
2024-03-06T08:10:26.318Z pool-5-thread-2 INFO JeroMqAppender sent a message: Hello (1).
2024-03-06T08:10:26.318Z pool-5-thread-2 INFO JeroMqAppender sent a message: Hello (1).
2024-03-06T08:10:26.318Z pool-5-thread-2 INFO JeroMqAppender sent a message: Again (1).
2024-03-06T08:10:26.318Z pool-5-thread-2 INFO JeroMqAppender sent a message: Again (1).
2024-03-06T08:10:26.318Z pool-5-thread-4 INFO JeroMqAppender sent a message: Hello (3).
2024-03-06T08:10:26.318Z pool-5-thread-4 INFO JeroMqAppender sent a message: Hello (3).
2024-03-06T08:10:26.318Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (1).
2024-03-06T08:10:26.318Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (1).
2024-03-06T08:10:26.318Z pool-5-thread-4 INFO JeroMqAppender sent a message: Again (3).
2024-03-06T08:10:26.318Z pool-5-thread-4 INFO JeroMqAppender sent a message: Again (3).
2024-03-06T08:10:26.318Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (3).
2024-03-06T08:10:26.318Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (3).
2024-03-06T08:10:26.318Z pool-5-thread-5 INFO JeroMqAppender sent a message: Hello (4).
2024-03-06T08:10:26.318Z pool-5-thread-5 INFO JeroMqAppender sent a message: Hello (4).
2024-03-06T08:10:26.318Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (4).
2024-03-06T08:10:26.318Z pool-5-thread-5 INFO JeroMqAppender sent a message: Again (4).
2024-03-06T08:10:26.318Z pool-5-thread-5 INFO JeroMqAppender sent a message: Again (4).
2024-03-06T08:10:26.318Z pool-5-thread-3 INFO JeroMqAppender sent a message: Hello (2).
2024-03-06T08:10:26.318Z pool-5-thread-3 INFO JeroMqAppender sent a message: Hello (2).
2024-03-06T08:10:26.318Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (4).
2024-03-06T08:10:26.349Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (2).
2024-03-06T08:10:26.349Z pool-5-thread-3 INFO JeroMqAppender sent a message: Again (2).
2024-03-06T08:10:26.349Z pool-5-thread-3 INFO JeroMqAppender sent a message: Again (2).
2024-03-06T08:10:26.349Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (2).
2024-03-06T08:10:26.364Z pool-5-thread-6 INFO JeroMqAppender sent a message: Hello (5).
2024-03-06T08:10:26.364Z pool-5-thread-6 INFO JeroMqAppender sent a message: Hello (5).
2024-03-06T08:10:26.364Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (5).
2024-03-06T08:10:26.364Z pool-5-thread-6 INFO JeroMqAppender sent a message: Again (5).
2024-03-06T08:10:26.364Z pool-5-thread-7 INFO JeroMqAppender sent a message: Hello (6).
2024-03-06T08:10:26.364Z pool-5-thread-7 INFO JeroMqAppender sent a message: Hello (6).
2024-03-06T08:10:26.364Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (6).
2024-03-06T08:10:26.364Z pool-5-thread-6 INFO JeroMqAppender sent a message: Again (5).
2024-03-06T08:10:26.364Z pool-5-thread-7 INFO JeroMqAppender sent a message: Again (6).
2024-03-06T08:10:26.364Z pool-5-thread-7 INFO JeroMqAppender sent a message: Again (6).
2024-03-06T08:10:26.364Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (5).
2024-03-06T08:10:26.364Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (6).
2024-03-06T08:10:26.380Z pool-5-thread-8 INFO JeroMqAppender sent a message: Hello (7).
2024-03-06T08:10:26.380Z pool-5-thread-8 INFO JeroMqAppender sent a message: Hello (7).
2024-03-06T08:10:26.380Z pool-5-thread-8 INFO JeroMqAppender sent a message: Again (7).
2024-03-06T08:10:26.380Z pool-5-thread-8 INFO JeroMqAppender sent a message: Again (7).
2024-03-06T08:10:26.380Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (7).
2024-03-06T08:10:26.380Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (7).
2024-03-06T08:10:26.380Z pool-5-thread-9 INFO JeroMqAppender sent a message: Hello (8).
2024-03-06T08:10:26.380Z pool-5-thread-9 INFO JeroMqAppender sent a message: Hello (8).
2024-03-06T08:10:26.380Z pool-5-thread-9 INFO JeroMqAppender sent a message: Again (8).
2024-03-06T08:10:26.380Z pool-5-thread-9 INFO JeroMqAppender sent a message: Again (8).
2024-03-06T08:10:26.380Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (8).
2024-03-06T08:10:26.380Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (8).
2024-03-06T08:10:26.380Z pool-5-thread-10 INFO JeroMqAppender sent a message: Hello (9).
2024-03-06T08:10:26.380Z pool-5-thread-10 INFO JeroMqAppender sent a message: Hello (9).
2024-03-06T08:10:26.380Z pool-5-thread-10 INFO JeroMqAppender sent a message: Again (9).
2024-03-06T08:10:26.380Z pool-5-thread-10 INFO JeroMqAppender sent a message: Again (9).
2024-03-06T08:10:26.380Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (9).
2024-03-06T08:10:26.380Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (9).
2024-03-06T08:10:26.380Z pool-5-thread-1 INFO JeroMqAppender sent a message: Hello (0).
2024-03-06T08:10:26.380Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Hello (0).
2024-03-06T08:10:26.489Z pool-5-thread-1 INFO JeroMqAppender sent a message: Again (0).
2024-03-06T08:10:26.489Z pool-5-thread-1 INFO JeroMqAppender sent a message: Again (0).
2024-03-06T08:10:26.489Z pool-4-thread-1 DEBUG JeroMqTestClient received a message: Again (0).
2024-03-06T08:10:26.616Z awaitility-thread INFO JeroMqAppender received an event of type ZEvent [type=DISCONNECTED, code=512, address=tcp://0.0.0.0:56729, value=3]
```
All seems to work out, but still it fails.
--
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 specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `JeroMqAppenderTest` timeouts (logging-log4j2)
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #1342:
URL: https://github.com/apache/logging-log4j2/issues/1342#issuecomment-1825244869
This is part of #1568.
--
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 specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `JeroMqAppenderTest` timeouts (logging-log4j2)
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz closed issue #1342: `JeroMqAppenderTest` timeouts
URL: https://github.com/apache/logging-log4j2/issues/1342
--
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 specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] `JeroMqAppenderTest` timeouts (logging-log4j2)
Posted by "ppkarwasz (via GitHub)" <gi...@apache.org>.
ppkarwasz commented on issue #1342:
URL: https://github.com/apache/logging-log4j2/issues/1342#issuecomment-1980372139
This is related to the upgrade to JeroMq 0.6.0 and may be related to zeromq/jeromq#975, although I didn't investigate it further.
--
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 specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org