yeah ive been looking at this, i have noticed that promptDelivery is called in a a different thread i.e.
public void promptDelivery(final Queue queue)
| {
| // TODO - do we really need to prompt on a different thread?
| executor.execute(new Runnable()
| {
| public void run()
| {
| queue.deliver();
| }
| });
| }
if i change this the problem goes away, maybe this is causing a race condition!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149059#4149059
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149059
In what cases are eviction regions created after nodes are created in the cache? The only potential situations I can think of are preloading from a cache loader or a state transfer, both of which happen during startup, before the region is created. Perhaps we should look into reordering the startup sequence so that any preloading or state transfer happens after eviction regions are set up, and that preloading and state transfer create the necessary events in the eviction queue?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149053#4149053
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4149053