Bug 779219 (SOA-1612)

Summary:	Disable jBPM logging in the optional service configurations
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Martin Weiler <mweiler>
Component:	JBPM - within SOA	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3 CP02	CC:	dlesage
Target Milestone:	---
Target Release:	4.3 CP04 ER1
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1612
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-23 14:56:47 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	779338

Description Martin Weiler 2009-11-17 19:28:55 UTC

Date of First Response: 2009-12-18 07:51:40
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/363726
project_key: SOA

As of SOA-1368, the jBPM logging service is disabled by default. The alternative jms or quartz based service configurations [1] should be aligned and have the logging service disabled as well.

[1] http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html/Administration_Guide/sect-jbpm_message_and_scheduler_service.html

Comment 1 Julian Coleman 2009-12-16 16:50:48 UTC

Link: Added: This issue is a dependency of SOA-1727

Comment 2 Julian Coleman 2009-12-18 12:51:40 UTC

Fixed with revision 4572 (4.3 branch) of:
  build-tools/builders/jbpm/build.xml

Commit message:
  SOA-1612.
  Disable logging in the optional (JCA inflow) configuration.

Comment 3 David Le Sage 2010-02-25 06:01:02 UTC

Please review the following draft text for the Resolved Issues section of the Release Notes:

https://jira.jboss.org/jira/browse/SOA-1612

    jBPM logging was incorrectly enabled by default for the optional JMS and Quartz-based service
    configurations. Consequently, these alternative configurations were out of alignment with the main
    jBPM logging service.

    Logging has now been disabled for these (JCA inflow) configurations. As a result, the behaviour
    across all configurations has been standardized.

Comment 4 Jiri Pechanec 2010-03-23 14:56:47 UTC

Verified in ER1