Hi,
We are trying to using
ejb cahing (by specifying commit type A) on Websphere. It worked fine on a stand alone
test server. But when we moved to a cloned/clustered environment, we began to see several unnecessary database reads. Basically, in the cloned environment, the cache is ignored and info. is read from database even when the data should be in the cache. I found a link (
http://www-3.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/was/040301.html) that said that ejb cahing (commit type a) and cloning are incompatible. But without the caching, the performance deteriorates significantly and it does not seem to make sense to use EJBs. Is there a way around this ? Kindly advise.
Thanks,
Sankar