Hello all,
Does anyone have experiences to share about caching in EJB environments ?
I would like to know how multiple JBoss/OJB instances can share the same
cache or at least not have long-term cache-inconsistencies.
If the "backoffice" CMS webapp updates items I want to see them a short
time lateron correctly changed in the "frontoffice" website.
Not having a cache at all however would severely impact our performance.
Background:
I am currently investigating the possibilities of improving performance of our OJB
based application. The application consists of
three webapplications on Tomcat, connected to Session EJB's on a central JBoss server
that uses OJB for Object/Relational mapping.
I think that the performance of the application depends on the use of caching (the
application is mostly retrieval from searching).
We use the default implementation.
We use separate Tomcat webservers: the frontoffice is a separate webapp in it's own
Tomcat instance, and the backoffice CMS is is a
separate webapp in it's own Tomcat. So they each talk with JBoss via RMI over the
network !
However, JBoss advices to use the integrated Tomcat with JBoss, because it avoids the
RMI network transports and the serialisation
of data.
If we would go for integrated JBoss+Tomcat instances then we would have multiple OJB
instances that share the same database but not
the same cache ! That would probably mean cache inconsistencies because the default
implementation AFAIK has no maximum object
lifetime and no distributed synchronisations ?
Answers anyone ?
Theo Niemeijer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
