Hey Rickard,
Thanks for the pointer to the article.
Did you notice how it describes how an entity bean might get
"pinned" against a single server in the cluster? Did you understand
this? It didn't make a whole lot of sense to me.
A clustered entity would use commit option "C", right? So the
claim that it would be too expensive to have multiple copies of the
same entity seemed obviously false. However, I can envision many
scenarios where a stateful session bean might get pinned to a
server. Do you think this is what he was reaching for? Or was he
referring to some strange clustered commit option "A" scenario, or
maybe a client-managed transaction?
-Dan
On 22 Feb 01, at 13:43, Rickard Öberg wrote:
> Hey
>
> You may want to read this:
> http://www.onjava.com/pub/a/onjava/2000/12/15/ejb_clustering.html
>
> regards,
> Rickard
>
> --
> Rickard Öberg
>
> Email: [EMAIL PROTECTED]
>
