[jboss-jira] [JBoss JIRA] Commented: (JBRULES-3152) Control of KnowledgeAgent instances
[
https://issues.jboss.org/browse/JBRULES-3152?page=com.atlassian.jira.plug...
]
Burkhard Vogel commented on JBRULES-3152:
-----------------------------------------
We use a singleton to manage the communication from application to the jBPM runtime. When
the singleton is created it creates a KnowledgeAgent which in turn updates the
KnowledgeBase if a change is made to the Guvnor. As it is a singleton we have no control
over the shutdown of the KnowledgeAgent and neither
ResourceFactory.getResourceChangeScannerService().stop();
ResourceFactory.getResourceChangeNotifierService().stop();
nor
kAgent.dispose()
is called.
Problem arises when during the development cycle the application gets redeployed - then
another KnowledgeAgent is created while the before exiting does not get disposed - still
they carry the same name. As we do development to the console the same applies to the
jbpm-gwt-server that as well creates a KnowledgeAgent and does not dispose it.
Control of KnowledgeAgent instances
-----------------------------------
Key: JBRULES-3152
URL: https://issues.jboss.org/browse/JBRULES-3152
Project: Drools
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Affects Versions: 5.2.0.Final
Reporter: Burkhard Vogel
Assignee: Mark Proctor
There should be a way limit the number of KA on a server - as I restart test-clients and
redeploy my client apps they tend to accumulate. Shouldn't the KA name be unique and
any reference to a KA with the same name recover the already created KA? Or shouldn't
all KA created by a client app (web or standalone) die when the creating app terminates?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira