| Summary: | SOA-P production config - Out of the box log level definitions too verbose for a production environment (4K+ hibernate and jbpm DEBUG msg/min) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Len DiMaggio <ldimaggi> | ||||
| Component: | Configuration | Assignee: | Mike Brock <cbrock> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.2 Beta 1 | CC: | jwulf, rruss | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.2 Beta 2 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-222 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: |
soa-4.2.0-IR8.0.zip
|
|||||
| Last Closed: | 2008-01-21 17:29:44 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Attachment: Added: server.log fixed. Still too verbose, I would prefer to add <param name="Threshold" value="INFO"/> on file appender What's the status of this? Seems like an easy fix. done. Link: Added: This issue is related to SOA-347 Verified in beta2 build. Link: Added: This issue related SOA-536 Link: Added: This issue related SOA-1073 Link: Added: This issue related SOA-1537 |
Date of First Response: 2007-12-17 23:26:37 project_key: SOA Description of problem: The out of the box SOA-P soa-4.2.0-IR8.0.zip production config logging definitions in server/production/conf/jboss-log4j.xml are identical to EAP 4.3. With SOA-P, this log4j configuration results in a very verbose log due to jbpm+hibernate DEBUG level messages. Version-Release number of selected component (IR or RC #, component ver) soa-4.2.0-IR8.0.zip How reproducible: 100% Steps to Reproduce: 1. Unzip the distribution file - start up the server Actual results: In a ~3 minute test - on an idle server - 12,000+ hibernate and 3000+ jbpm log messages were generated. head -1 server.log 2007-12-06 12:54:20,047 DEBUG [org.jboss.logging.Log4jService] Installed System.out adapter [ldimaggi@ldimaggi log]$ tail -1 server.log 2007-12-06 12:57:03,580 INFO [org.jboss.system.server.Server] Shutdown complete [ldimaggi@ldimaggi log]$ [ldimaggi@ldimaggi log]$ cat server.log | grep -i hibernate | wc -l 12045 [ldimaggi@ldimaggi log]$ cat server.log | grep -i jbpm | wc -l 3731 Expected results: The EAP 4.2 production config server has these log4j limits set: <category name="org.jboss.web"> <priority value="INFO" /> </category> <category name="org.jboss.ha"> <priority value="INFO" /> </category> Why not add limits at the INFO level for <category name="org.hibernate"> <priority value="INFO" /> </category> <category name="org.jbpm"> <priority value="INFO" /> </category> Additional info: (e.g., stack trace) This problem has been present in the SOA-P builds since the beginning. It's likely that customers will adjust logging for their own environments. But - there is an out of the box impact for users. The getting started guide includes instructions for the customer to deploy and run the helloworld quickstart. On the production config, the user will have to tail or grep the server.log to see the test results. It is VERY hard to see the results from the quickstart with 4000+ jbpm and hibernate DEBUG messages being written to the log every minute. Attachments (e.g., server log)