[JBoss JIRA] Created: (JBCACHE-745) nodeEvicted being called for nodes that don't actuall get evicted
by gregorypierce (JIRA)
nodeEvicted being called for nodes that don't actuall get evicted
-----------------------------------------------------------------
Key: JBCACHE-745
URL: http://jira.jboss.com/jira/browse/JBCACHE-745
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.4.0.SP1
Reporter: gregorypierce
Assigned To: Manik Surtani
Attachments: CacheEviction.java
Working on class example from training materials CacheEviction.java. Will receive a nodeEvicted call that the root node has been evicted, but if you look at the console itself and print the tree - the root node doesn't get evicted. Should not call nodeEvicted with a node that hasn't actually already been evicted from the tree. Looks like it realizes that the node is a parent node and decides against evicting it after the interface call.
// FIXME We extend AbstractTreeCacheListener, which provides a default implementation
// of the TreeCacheListener interface. You just need to override methods to write to
// the console for cache events in which you are interested. Do something like this:
public void nodeCreated(Fqn fqn) {
System.out.println("nodeCreated(): fqn: " +fqn);
}
public void nodeEvicted(Fqn fqn)
{
System.out.println("nodeEvicted(): fqn: " +fqn);
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 9 months
[JBoss JIRA] Created: (JBPM-741) JbpmSchedulerThread does not terminate the scheduler/command threads properly
by Alejandro Guizar (JIRA)
JbpmSchedulerThread does not terminate the scheduler/command threads properly
-----------------------------------------------------------------------------
Key: JBPM-741
URL: http://jira.jboss.com/jira/browse/JBPM-741
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM 3.1.1
Reporter: Alejandro Guizar
Fix For: jBPM 3.1.3
The implementation of SchedulerThread and CommandExecutorThread in 3.1.1 does not provide a mechanism to exit the run() method, allowing the Thread to exit properly and release any resources it is holding.
This becomes an issue for perm gen in JBoss AS and other containers.
For SchedulerThread, keepRunning (bool) should be public or provide mutators, so whatever launches the Thread can modify it.
For CommandExecutorThread, the while(true) in run() should be changed to something like SchedulerThread uses and, of course, provide mutators to the loop control variable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 9 months