Eclipse Community Forums: EclipseLink » EclipseLink/Toplink Cache coordination using JMS for manual DB updates

Help

Home

Home » Eclipse Projects » EclipseLink » EclipseLink/Toplink Cache coordination using JMS for manual DB updates

Show: Today's Messages :: Show Polls :: Message Navigator

EclipseLink/Toplink Cache coordination using JMS for manual DB updates [message #916125]

Tue, 18 September 2012 15:22

suneel allareddy

Messages: 2
Registered: September 2012

Junior Member

We are having 2 web application using same Database and common Toplink library, but 2 different session objects for both the applications. We are using JMS for cache coordination. JMS propagating messages successfully between the applications and able to see the object changes in both the applications properly. Now, we are trying to refresh cache for manual updates in Database.
We are trying to refresh particular object which is modified in database in one application, it is able to refresh in the application from which refresh happened but not in other application. Is there any way we can force JMS to propagate these changes/updates?

Our intention is refreshing in one application so that JMS should coordinate and update in others when DB manual updates. Please let us know any comments for the same.

Database using: Oracle 11g
Toplink Version:- 9.0.3

Also, we are planning to migrate Toplink to eclipse Link soon but i think above issue will be persists.

Please let us know if any more details required on the same.

Report message to a moderator