Bug 1295665 - (6.4.z) Syslog handler does not connect to syslog
Summary: (6.4.z) Syslog handler does not connect to syslog
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.10
Assignee: baranowb
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks: 1278806 eap6410-payload
TreeView+ depends on / blocked
 
Reported: 2016-01-05 07:13 UTC by baranowb
Modified: 2017-01-17 13:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 13:01:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker LOGMGR-123 0 'Major' 'Resolved' 'TCP reconnect will only attempt to reconnect once' 2019-12-03 14:04:39 UTC

Description baranowb 2016-01-05 07:13:51 UTC
if syslog is not available on server boot, handler will try to connect once and thats it. It will not connect when syslog boots later on.

Comment 5 Jiří Bílek 2016-08-09 15:53:42 UTC
Verified with EAP 6.4.10.CP.CR1

Comment 6 Petr Penicka 2017-01-17 13:01:05 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.


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