jason,
thankyou for yor responses.
in the interests of "keeping it simple", i've decided to try to lobby
the rest of the team to go back to using db generated keys (i.e. identity
columns in the case of ms sql server ) and throw out key our
key generation code.
we'll then have a single .ear that can be deployed on any box
with minimal changes to 1 or 2 orion files to allow clustering, and
the only single point of failure will then be the database, and not
the box generating keys.
cheers,
greg.
----- Original Message -----
From: "Jason Smith" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Sunday, June 10, 2001 2:36 AM
Subject: RE: clustering and key generation
> Have you tried setting:
> <ejb-module remote="true" path="keygenerator" />
> in your orion-application.xml on machines B,C, and D? The only place the
> KeyGenerator bean is really deployed is on A, so machine A's
> orion-application.xml will have remote="false". I am assuming you have
> already set up your rmi.xml, etc. correctly to support this kind of
> operation (as in the links I posted earlier).
>
> The only other thing I can think of right now is maybe try making a parent
> application which has the KeyGenerator bean and run children apps on the
> other machines. I haven't tried the parent/child app deployment, so you
> would have to check the archives to see if this is feasible.
>
> -jason
>
>
>
