[jboss-jira] [JBoss JIRA] Commented: (JBRULES-3152) Control of KnowledgeAgent instances
Davide Sottara (JIRA)
jira-events at lists.jboss.org
Wed Jul 27 06:27:23 EDT 2011
[ https://issues.jboss.org/browse/JBRULES-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616679#comment-12616679 ]
Davide Sottara commented on JBRULES-3152:
-----------------------------------------
How do you manage the KA lifecycle?
The user is expected to control the monitoring threads:
ResourceFactory.getResourceChangeNotifierService().start()/stop();
ResourceFactory.getResourceChangeScannerService().start()/stop();
and to dispose the KA when no longer needed:
kAgent.dispose();
-----------------------
At the moment, the KA name is not unique and they are not tracked. Could you provide a few more details on your use case so I can see if it is necessary/reasonable to implement an agent registry?
> 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
More information about the jboss-jira
mailing list