[ https://issues.jboss.org/browse/WFLY-2605?page=com.atlassian.jira.plugin.... ] Brent Douglas edited comment on WFLY-2605 at 12/16/13 7:01 PM: --------------------------------------------------------------- [~pferraro] As you say, not using eager start stops hibernates cache leaking. Clearly that cache should not be eager started. I was a little unclear what was going on when I filed this but I think I can see use cases where this is an actual problem, and one that now I have a better idea what is going on, they are cases that I would actually like to use. For example if I pre-cache a bunch of stuff (for arguments sake say I'm only caching <Integer,BigDecimal>) which is calculated on startup and takes a significant amount of time. During a development it would be super handy to be able to run this cache as an eager starting cache so that redeploying the app doesn't need to refill this every time. Anyway, I am going to submit a PR to infinispan and see where that goes. was (Author: brentdouglas): Paul Ferraro As you say, not using eager start stops hibernates cache leaking. Clearly that cache should not be eager started. I was a little unclear what was going on when I filed this but I think I can see use cases where this is an actual problem, and one that now I have a better idea what is going on, they are cases that I would actually like to use. For example if I pre-cache a bunch of stuff (for arguments sake say I'm only caching <Integer,BigDecimal>) which is calculated on startup and takes a significant amount of time. During a development it would be super handy to be able to run this cache as an eager starting cache so that redeploying the app doesn't need to refill this every time. Anyway, I am going to submit a PR to infinispan and see where that goes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira