Persist the cache in your JBoss instance
Persisting Cache in your JBoss instance In this example, consider if our server that is restarted comes back up with no market data – that might lead our customers to not make a decision that they could have profited from. Again, how your recover in this scenario is a business decision. For our example, we will assume that our business is ok with high frequency market data being slightly off (because updates will come quickly) but they do not want empty data. With this in mind, we decide that our application should persist its cache to a database periodically. We assume that the necessary code changes (annotations based, determines what to cache and eviction policies) are implemented to our data layer. Cache Loaders are configured in the JBoss Cache XML file. In this same file, we define the fqns (objects) we want loaded at startup as well (defined in the preload tag).