logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: syslog-ng disconnect causes thread to silently die?
Date Tue, 19 Jan 2016 20:22:19 GMT
If the connection is closed it is likely the Appender is throwing an Exception. Normally that
exception will be ignored unless you configured it to pass the exception along to the application.
 I would suggest enabling debug logging by setting status=debug on the configuration element
in log4j2.xml.

Ralph


> On Jan 19, 2016, at 12:36 PM, Blake Day <blake@chewy.com> wrote:
> 
> 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)'
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


Mime
View raw message