After caching the data needed for a request using hibernate secondary cache (ehcache) if the database is manually shutdown at any point to simulate a database down scenario, JBOSS tries to ping the database and finds that the db is unavailable and none of the requests go through although we have all the required data cached. Is there any configuration that we need to do in Hibernate which will ensure the cache is used if the database is down?

Hibernate in theory only gets a database connection when it needs to do something with database, so you should not have a problem that way even though I think this is a little ify. What operation does exactly fail?



Farzad-

I have some associations that are cached that request is going to the database instead of reading it from the cache.

how do you fetch the associations? Do you know if the cache region's life span is long enough?




Farzad-

<many-to-one class="com.class1" fetch="select" name="class1">
<column name="OFFER_SET_ID" precision="10" scale="0"/>
</many-to-one>
These are the kind of associations that I have. Do i need to change the fetching strategy?

No actually select fetching is a better idea here if you ask me. Is com.class1 cached too? what is the cache configuration for its caching region?



Farzad=

the class is also cached and it has read-write cache enabled.

how about the cache configuration?



Farzad-

i have ehcache enabled and the entries are all eternal..

so far everything you did looks good. Explain to me how you fetch the association. May be we can find something there.


Farzad-

And by the way, have you setup updateTimeStmaps cache region? Do you know if any instance of this specific class has been updated at some point? That will invalidate the whole cached instances that are cached before the last update.




Farzad-

I do have that setup but I dont think any entries have been updated..I did not understand what you meant by fetching associations.

Then set it up because hibernate will be confused as to how fresh cached objects are if the updatetimestamp cache region has a shorter life span than the rest of the entities. If possible, it is recommended that this region is eternal too. However, see the documentation for the correct region name.

As for the fetching, I want to know where in your code the association is requested, and what triggers hibernate's load action.



Farzad-

I have lazy loading set to false and when I load an object all the associations are loaded..directly although I dont use the association right away. I will set up the updateTimestamps cache so thats eternal for testing..

I still have the same problems...any suggestions?