Hide Forgot
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.
Link: Added: This issue depends JBPM-1450
Link: Removed: This issue depends JBPM-1450
Link: Added: This issue is related to JBPM-1450
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
Attachment: Added: a.txt
Attachment: Removed: a.txt
Attachment: Added: solution.txt
To be committed in two days if no objections. Comments welcome.
Attachment: Removed: solution.txt
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
Thanks Julian's comments. Solution has been updated.
Attachment: Added: solution_2.txt
Thanks Jiri's comments. Solution has been updated.
Solution 2 looks OK
Fixed at https://svn.devel.redhat.com/repos/jboss-soa/branches/4.3/build-tools/builders/jbpm/build.xml, revision 3169
Link: Added: This issue is a dependency of SOA-1727