Bug 779296 (SOA-1684) - RecordingServerHandler should be disabled by default
Summary: RecordingServerHandler should be disabled by default
Keywords:
Status: NEW
Alias: SOA-1684
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Integration
Version: 5.0.0 ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: FUTURE
Assignee: Ken Johnson
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-08 09:52 UTC by Martin Vecera
Modified: 2011-04-08 20:17 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Feature Request

Attachments (Terms of Use)
standard-jaxws-endpoint-config.xml (3.40 KB, text/xml)
2009-12-08 09:55 UTC, Martin Vecera 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1684 0 None None None 2012-12-06 13:06:24 UTC

Description Martin Vecera 2009-12-08 09:52:53 UTC 
Date of First Response: 2010-01-12 11:24:47
project_key: SOA

jboss-as/server/*/deployers/jbossws.deployer/META-INF/standard-jaxws-endpoint-config.xml contains logging handlers (org.jboss.wsf.framework.invocation.RecordingServerHandler). These should be disabled by default.
Comment 1 Martin Vecera 2009-12-08 09:55:38 UTC 
See the attached file for proposed changes.
Comment 2 Martin Vecera 2009-12-08 09:55:38 UTC 
Attachment: Added: standard-jaxws-endpoint-config.xml
Comment 4 Martin Vecera 2010-09-15 14:36:32 UTC 
The justification is simple - we do have all logging disabled in production configuration except for the main logger set to WARN.
It does not have a big perf. impact. Definitely under 1%. But it could become a problem if there were some change to the code base.
All in all, such a logging has no place there. It is the same as Hibernate or jUDDI logging...
Disabling it in all configurations is questionable. I would follow the already established practices for other logging facilities (e.g. jUDDI, jBPM...).
Note You need to log in before you can comment on or make changes to this bug.