Below are some stats from the EAP 4.3.GA_CP01 build with the default log settings.

• AS after restart:
• server.log is 1.1.MB
• deploy the seam booking example
• pretty typical but basic application with hibernate, EJBs, jsf, and richfaces components.
• log to 1.4 MB
• one access to application and login
• 1.5MB
• book one hotel
• 1.8MB
• Book and cancel 4 hotels
• 3.7MB in about 2-3 minutes with one user.

I will attach the final 3.7MB log for review. Please review it to see what is logged on every request (jsf, hibernate, ejb, ajax, etc...).

Now extrapolate that to an actual production environment and you are quickly consuming GB's of disk space, and effecting the entire applications performance.

In previous EAP releases this issue was covered and discussed with the following jiras: JBPAPP-46, and JBPAPP-472.

However I feel that it needs to be reviewed for the latest release 4.3.GA_CP01. I have not determined a delta with the previous release.

Maybe there are some new logging categories that need to be adjusted, or perhaps the default logging level can't be DEBUG.

I know that one of the arguments against this is that it helps support to diagnose issues. However this is an issue all its own, and hampering all users all the time to make it easier to help the few who have issues once in a while does not seem the best coarse of action. Not to mention that most of the output will be useless to support, and even most developers.

Another argument that I have heard against this is that the logging level will always need to be tweaked so we can't adjust it without knowing the customers needs. My confusion here comes from the fact that the production server is supposed to be our recommended production configuration. The current log setting are certainly not a production setting. No customer would want to see this out of the box, and this frustrates me every time I see it.