[
https://jira.jboss.org/browse/JBPM-2947?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar updated JBPM-2947:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: jBPM 3.2.10
Description:
The VariableContainer currently does not delete variables if a *custom* logging service is
configured. This should not be the default, and instead should only be the case if the
Logging Service is DbLoggingService.
Code in question [VariableContainer]:
if (jbpmContext == null || jbpmContext.getServices().getLoggingService() != null) {
Attached is the patch.
was:
The VariableContainer currently does not delete variables if *any* logging service is
configured. This should not be the default, and instead should only be the case if the
Logging Service is DbLoggingService.
Code in question [VariableContainer]:
if (jbpmContext == null || jbpmContext.getServices().getLoggingService() != null) {
Attached is the patch.
Custom Logging Causes Orphaned Variables
----------------------------------------
Key: JBPM-2947
URL:
https://jira.jboss.org/browse/JBPM-2947
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Brad Davis
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.10
Attachments: VariableContainer.java.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The VariableContainer currently does not delete variables if a *custom* logging service
is configured. This should not be the default, and instead should only be the case if the
Logging Service is DbLoggingService.
Code in question [VariableContainer]:
if (jbpmContext == null || jbpmContext.getServices().getLoggingService() != null) {
Attached is the patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira