Entity Bean's distributed cache

[xsantana]

Hi all,

I'm using jboss 3.2.1 on a cluster with the 'all' server configuration, and I'm getting a very bad performance. Although I'm using commit option 'A', the entities cache is not working.
Having a look to old documentation (august 2003) I see distributed cache for entities was not supported. Is it currently supported? Do I need to change anything from the default 'all' configuration? I know I should re-buy documentation, but I'd like to know first if entities cache across the clustrer is currently supported.

Thanks,

Xavi

[julien.dubois]

Hi,

You should upgrade to JBoss 3.2.3, the version you use had a big issue with CMP+commit option A.
I, too, had performance issues with JBoss 3.2.1 : the day I switched, they disappeared...

[traxx]

Hi,

There is no distributed cache but there is a cache invalidation system with 3.2 releases, 3.2.3 is better. Distributed cache will be in JBoss 4.
A litte bug, you must use transactions to manage all your entities...

[xsantana]

Thanks guys.

Can anyone tell me if I'm wrong?

- Distributed cache is not supported, so using commit option A in a cluster is not possible. The server will act as if commit option B or C (i'm not sure about the difference) was selected. Or does it allow using local cache for each node?
- I'll only keep cache within a transaction. When commiting it, cache contents will be no longer valid.
- If I'm right in the first point, I suppose cache invalidation system should be a mechanism to invalidate local entities cache for each node to avoid using inconsistent data.

Thanks again for the help.

Xavier

[juha]

Correct.