Bug 1148433 - Changing reconnect-timeout value for syslog handler requires server reload
Summary: Changing reconnect-timeout value for syslog handler requires server reload
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: DR7
: EAP 6.4.0
Assignee: Kabir Khan
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-01 12:54 UTC by Petr Kremensky
Modified: 2019-08-19 12:46 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:46:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1145680 0 unspecified CLOSED Syslog handler for audit log throws NPE after syslog server restart (UDP protocol) 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker EAP6-230 0 Major Closed audit syslog handler should be able to automatically reconnect 2017-03-02 18:32:14 UTC
Red Hat Issue Tracker WFCORE-191 0 Major Resolved Syslog reconnect timeout does not take effect at runtime 2017-03-02 18:32:14 UTC

Internal Links: 1145680

Description Petr Kremensky 2014-10-01 12:54:12 UTC
Description of problem:
 Changing value for reconnect-timeout doesn't have any effect unless we reload a server.

Version-Release number of selected component (if applicable):
 EAP 6.4.0.DR3

How reproducible:
 Always

Steps to Reproduce:
1. Configure a syslog handler
/core-service=management/access=audit/logger=audit-log:write-attribute(name=enabled,value=true)
batch
/core-service=management/access=audit/syslog-handler=mysyslog:add(formatter=json-formatter, max-failure-count=2)
/core-service=management/access=audit/syslog-handler=mysyslog/protocol=tcp:add(host=<syslog_host>, port=514, reconnect-timeout=30)
run-batch
/core-service=management/access=audit/logger=audit-log/handler=mysyslog:add

2. Change the value for reconnect-timeout
./core-service=management/access=audit/syslog-handler=mysyslog/protocol=tcp:write-attribute(name=reconnect-timeout, value=20)

3. Make a syslog server failover and see logs

Actual results:
 JBAS013417: Attempting reconnect to syslog handler 'mysyslog; after timeout of 30 seconds

Expected results:
 JBAS013417: Attempting reconnect to syslog handler 'mysyslog; after timeout of 20 seconds
or
 "reload required"

Additional info:
 First mgmt operation on disabled syslog server doesn't increase the failure counter, every other triggers NPE.

Comment 1 Kabir Khan 2014-10-21 17:20:00 UTC
https://github.com/jbossas/jboss-eap/pull/1830

Comment 2 Petr Kremensky 2014-10-29 09:04:56 UTC
Verified on EAP 6.4.0.DR7

Comment 3 JBoss JIRA Server 2015-04-28 15:03:40 UTC
John Doyle <jdoyle> updated the status of jira EAP6-230 to Closed


Note You need to log in before you can comment on or make changes to this bug.