Bug 778932 (SOA-1368) - jBPM logging is enabled by default
Summary: jBPM logging is enabled by default
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1368
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Build Process, Configuration
Version: 4.3 CP01,4.2 CP04
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Ryan Zhang
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks: SOA-1727
TreeView+ depends on / blocked
 
Reported: 2009-06-12 10:22 UTC by Jiri Pechanec
Modified: 2009-12-16 16:50 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-17 10:16:32 UTC
Type: Bug


Attachments (Terms of Use)
solution.txt (780 bytes, text/plain)
2009-06-16 06:15 UTC, Ryan Zhang
no flags Details
solution_2.txt (783 bytes, text/plain)
2009-06-16 11:48 UTC, Ryan Zhang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1368 0 Critical Closed jBPM logging is enabled by default 2013-03-11 08:59:10 UTC

Description Jiri Pechanec 2009-06-12 10:22:51 UTC
Date of First Response: 2009-06-12 10:21:35
project_key: SOA

jBPM logging has serious impact on jBPM performance and is disabled by default in jBPM defaul config file. Unfortunately SOA-P's jbpm.cfg.xml overwrites this setting and enables the logging again.

Comment 1 Jiri Pechanec 2009-06-12 10:23:29 UTC
Link: Added: This issue depends JBPM-1450


Comment 2 Jiri Pechanec 2009-06-12 10:23:44 UTC
Link: Removed: This issue depends JBPM-1450 


Comment 3 Jiri Pechanec 2009-06-12 10:24:00 UTC
Link: Added: This issue is related to JBPM-1450


Comment 4 Len DiMaggio 2009-06-12 14:21:35 UTC
History on this issue:

* For 4.3 GA/CP01, the jBPM issues were linked together in https://jira.jboss.org/jira/browse/SOA-647

* For 4.2 CP03/CP04, the jBPM issues were linked together in https://jira.jboss.org/jira/browse/SOA-646

* It's not a regression, it is also present in 4.2 CP03 - documented in rel notes - https://jira.jboss.org/jira/browse/SOA-1122 - also documented for 4.3 CP01 as open issue 

* The jBPM JIRA is https://jira.jboss.org/jira/browse/JBPM-1450



Comment 5 Ryan Zhang 2009-06-16 06:11:10 UTC
Attachment: Added: a.txt


Comment 6 Ryan Zhang 2009-06-16 06:11:25 UTC
Attachment: Removed: a.txt 


Comment 7 Ryan Zhang 2009-06-16 06:12:27 UTC
Attachment: Added: solution.txt


Comment 8 Ryan Zhang 2009-06-16 06:15:12 UTC
To be committed in two days if no objections.

Comments welcome.

Comment 9 Ryan Zhang 2009-06-16 06:15:12 UTC
Attachment: Added: solution.txt


Comment 10 Ryan Zhang 2009-06-16 06:15:24 UTC
Attachment: Removed: solution.txt 


Comment 11 Jiri Pechanec 2009-06-16 06:20:44 UTC
Are you really sure that you will not lose ESB specific config changes using this approach?

An exmaple what has to be in the jbpm.cfg.xml file is
        <bean class="org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory">
          <field name="isTransactionEnabled"><false/></field>
          <field name="isCurrentSessionEnabled"><true/></field>
        </bean>

If you want to use default.jbpm.cfg.xml as a template to start you should identify diffs between default cfg and ESB specific changes and then apply XSL transformation on it

Comment 12 Ryan Zhang 2009-06-16 11:48:05 UTC
Thanks Julian's comments.

Solution has been updated.


Comment 13 Ryan Zhang 2009-06-16 11:48:05 UTC
Attachment: Added: solution_2.txt


Comment 14 Ryan Zhang 2009-06-17 02:11:35 UTC
Thanks Jiri's comments. Solution has been updated.


Comment 15 Jiri Pechanec 2009-06-17 05:31:07 UTC
Solution 2 looks OK

Comment 17 Julian Coleman 2009-12-16 16:50:48 UTC
Link: Added: This issue is a dependency of SOA-1727



Note You need to log in before you can comment on or make changes to this bug.