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...
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...
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.