logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Blake Day <bl...@chewy.com>
Subject syslog-ng disconnect causes thread to silently die?
Date Tue, 19 Jan 2016 19:36:39 GMT
I’m using SocketAppender to log to syslog-ng.


When logging a message that exceeds 8192 bytes (a syslog-ng setting), syslog-ng gives an error
and closes the connection.  What happens immediately after is unclear, but it appears that
the java thread just dies silently.  The thread itself is a quartz scheduler worker thread,
but I thought I’d ask here to see whether you guys think this is a log4j related issue.
 There are no java application logs (console or otherwise) to suggest what happened.


Here is the output from syslog-ng’s side:


2016-01-19T14:26:34-05:00 ERR syslog-ng[87462]: - Incoming frame larger than log_msg_size();
log_msg_size='8192', frame_length='100233'

2016-01-19T14:26:34-05:00 NOTICE syslog-ng[87462]: - Syslog connection closed; fd='34', client='AF_INET(127.0.0.1:10142)',
local='AF_INET(0.0.0.0:601)'

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message