Alwyn Schoeman wrote:
On Thu, Nov 20, 2003 at 05:33:48PM +0200, Alexey Loubyansky wrote:
From what I can learn on the web it seems that a read-mostly pattern is
where
you have 2 copies of a bean, one read-only and the other read-write. It
seems
that you need to write at a specific interval. Is
Alwyn Schoeman wrote:
I'm not that familiar with CMP and JBoss yet.
Would that mean commit option B for the row-locking?
Yes.
From what I can learn on the web it seems that a read-mostly pattern is where
you have 2 copies of a bean, one read-only and the other read-write. It seems
that you need
On Thu, Nov 20, 2003 at 05:33:48PM +0200, Alexey Loubyansky wrote:
From what I can learn on the web it seems that a read-mostly pattern is
where
you have 2 copies of a bean, one read-only and the other read-write. It
seems
that you need to write at a specific interval. Is this possible?
Sent: Tuesday, November 18, 2003 10:43 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] CMP2 and loadbalancing
In this case, to ensure the consistency of the data you have to lock the
data in the database. It means using row-locking, i.e SELECT ... FOR
UPDATE. To solve the scalability problem, you
In this case, to ensure the consistency of the data you have to lock the
data in the database. It means using row-locking, i.e SELECT ... FOR
UPDATE. To solve the scalability problem, you could consider a
read-mostly pattern with 'Standard CMP 2.x EntityBean with cache
invalidation' container.
Hi,
My application environment is the following:
1) The same application is duplicated on multiple servers.
2) These servers are loadbalanced by hardware in front of the servers which
basically round-robins between the servers.
3) All client requests via http are session- and stateless.
4) Each
