Bug 779296 (SOA-1684)

Summary: RecordingServerHandler should be disabled by default
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Martin Vecera <mvecera>
Component: IntegrationAssignee: Ken Johnson <kejohnso>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER4   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1684
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
standard-jaxws-endpoint-config.xml none

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...).