Records of one of my database server is being modified by two way:

1) using an application where hibernate is used
2) using another server which also changes the same database using somehow.

My problem is that: changes done by another server is not reflects instantly in my application. My hibernate cache is not refreshed instantly.

What is the solution for this?

Use evict() method for ur sessionFactory.

.....

That is fine. But how my application will know that the there is some db changes done. Because db changes was done from external system.

That is fine. But how my application will know that the there is some db changes done. Because db changes was done from external system.

User timer task to invoke evict() at specific intervals.

Normally hibernate makes itself synchronize with DB server.

Only method to synchronize with ur DB without restarting web server is using evict() methods on ur sessionFactory in specific intervals.

We have already used a timeInterval of 30 min after which the cached is refreshed.

We cannot decrease this interval. I want that when the data changed externally, the cache should be refreshed instantly.

Then you need to arrange some way for the external application to notify your Hibernate application that the database has changed so that it can call SessionFactory.evict(). There is no way Hibernate can know when an update happens unless the external system somehow sends a note. Is it possible for you to use a clustered cache (for example the JBoss cache) and have the external system also use this cache? Or at least notify it that data has changed?

Decreasing the cache timeout is not a useful option since it will clear the cache even if the data hasn't change.

See the situation below:
I have no way to inform the hibernate of second system about the db change done.

just write a thread for calling evict() method in interval , becaz it doesn't take more time to execute.

u can do this by using JMS...

write the messaging system to alert the DB changes to ur other end, if the DB chage msg comes call evict() methods.

i think u will use openJMS for this purpose, becaz it'e very easy.

http://openjms.sourceforge.net/

Thanks for your idea of Messaging.

I have below issues:
1) Both the side we need the J2EE env.
2) Data are transfered mannualy.
3) Also, both the system are geographically at different locations, so jms will send a asynchronous messages which is not sure that when it will be read by other system.

OpenJMS doesn't need any J2ee stack, it's available as standalone.

u use persistent to send msg without any interruption. if u use that msg it will surely send to the system.

Issue unresoved:

Data are transfered mannualy.

Oracle AQ can trigger a JMS message. If you are using PL/SQL to transfer data from ORA-1 to ORA-2, the same function may trigger a message to System-2. On receiving the message, System-2 may evict necessary objects.