[jboss-jira] [JBoss JIRA] (WFLY-12558) Intermittent failures in TCPSyslogAuditLogTestCase
[
https://issues.jboss.org/browse/WFLY-12558?page=com.atlassian.jira.plugin...
]
James Perkins commented on WFLY-12558:
--------------------------------------
My guess is the test syslog server has not been started by the time the message is sent.
I've personally never really liked any of these syslog tests, but there are quite a
few now. Others seem to occasionally fail as well. I do wonder if we should invest some
time and write our own mock syslog server.
Anyway for the fix I'm not sure setting the reconnect attempts would work. Failed
messages aren't re-logged so it would likely take a loop of some sort until the
message is found.
Intermittent failures in TCPSyslogAuditLogTestCase
--------------------------------------------------
Key: WFLY-12558
URL: https://issues.jboss.org/browse/WFLY-12558
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Brian Stansberry
Assignee: Darran Lofthouse
Priority: Major
5 tests in TCPSyslogAuditLogTestCase are frequently failing since late August:
https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTyp...
Initial failure has this in the server log:
{code}
ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2)
WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "elytron"),
("syslog-audit-log" => "TCPSyslogAuditLogTestCase")
]) - failure description: {"WFLYCTL0080: Failed services" =>
{"org.wildfly.security.security-event-listener.TCPSyslogAuditLogTestCase" =>
"WFLYELY00004: Unable to start the service.
Caused by: java.io.IOException: ELY12001: The maximum reconnect attempts value of 0
was reached. The syslog endpoint will be shutdown."}}
{code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)