Improving robustness of JBoss EAP 6.0.1 syslog logging - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

JBoss server stops logging
In JBoss EAP 6.0.1 log4j's SyslogAppender can be used to log to syslog, but it has limited recoverability from loss of connection to the backing syslogd. Syslogd downtime may occur routinely as part of log rotation. This article describes a workaround to improve robustness of syslog logging with JBoss EAP 6.0.1.
Note: from EAP 6.2 onwards, the JBoss SyslogHandler can be used. SyslogHandler includes provisions for reconnection, and is now the recommended way to handle syslog logging: 268783 | How to use syslog in JBoss EAP 6.

Environment

Red Hat JBoss Enterprise Application Platform 6.0.1
Red Hat Enterprise Linux 6.4
rsyslogd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)