It sounds like our database logging option in general is a bad design. Definitely needs rethinking. And in 6.2, the default will be configuring the command/audit logging with async handlers.

2) Change the overflow-action to "DISCARD", but in this situation the log messages will be lost

From the startup log, the new startup contains errors not shown in the initial log:

server becomes unresponsive after running for a while ----------------------------------------------------- Key: TEIID-3578 URL: https://issues.jboss.org/browse/TEIID-3578 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.7.1 Environment: RHEL 6, AWS VM, JBoss EAP (standalone) 6.3.2.GA JBoss Data Virtualization 6.1.0.ER4 Reporter: Jorge Herrera Assignee: Steven Hawkins Attachments: server.log, server_startup.log, stackTrace_TEIID-3578, threaddump.txt Server becomes unresponsive, it does ack new sessions, but nothing else, admin-console, and direct queries are completely unresponsive. If I reboot the server it works just fine. Disk space / RAM / CPU all seem just fine. [root@BIJDVDev2 ~]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/xvde1 6062016 4601808 1397596 77% / none 7619624 0 7619624 0% /dev/shm [BIJDVDev2.dev.a1.vary.redhat.com] [11:38:48 AM] [root@BIJDVDev2 ~]# top top - 11:43:05 up 14 days, 13:31, 1 user, load average: 0.00, 0.00, 0.00 Tasks: 151 total, 1 running, 150 sleeping, 0 stopped, 0 zombie Cpu(s): 0.1%us, 0.1%sy, 0.0%ni, 99.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 15239248k total, 5387488k used, 9851760k free, 203540k buffers Swap: 0k total, 0k used, 0k free, 2887904k cached