Thanks. I verified that a bean deployed on server1 can register itself in
server2's namespace. However, if I deploy the same bean on server2, with the
same namespace, the namespace can handle only one instance bound to the same
name. The last bean bound, wins. This will solve some of my testing situations,
so I thank you.

Moving forward, however, I would hope that I can deploy beans to two different
containers, but have them located via a smarter naming service. When a client
requests the bean, it will get the bean bound in server1. The next client would
get the bean (bound under the same name) from server2. This would support a
rudimentary form of load-balancing. If server1 crashes, the client's EJB
reference will re-lookup the bean and be handed a remote reference to server2's
bean. This would support failover.

Regardless of how these "smart" naming services can be created, it will probably
be neccessary for a name service to support multiple beans cound to the same
JNDI name. There may be other approaches as well.

Where would one look to see the proposed (or current?) direction of failover and
load balancing support. Basic clustering.

jim


----- Original Message -----
From: "Alexander Kogan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 03, 2001 1:10 PM
Subject: Re: [JBoss-user] Multiple Servers - Bean Locating


> James,
>
> it's quite simple:
>
> First server (primary) has standard configuration.
> I only changed java.naming.provider.url from localhost
> to real.host1.name, but I think it's not necessary.
>
> On the second server, set java.naming.provider.url
> from jndi.properties to real.host1.name (primary server host).
> Then I disabled (commented out) JMX adapters in jboss.jcml:
>
>   <!-- JMX adaptors *** DISABLE ***
>   <mbean code="org.jboss.jmx.server.JMXAdaptorService"
> name="Adaptor:name=RMI" />
>
>   <mbean code="org.jboss.jmx.server.RMIConnectorService"
> name="Connector:name=RMI" />
>    -->
>
> And that's it.
>
> One more thing. Of course, "secondary" server must be started
> after "primary" one.
>
> In this setup (based on jboss-2.1) I'm able to lookup EJBs
> deployed on both servers and they are able to call each other.
> The only problem I discovered that I cannot lookup a bean from
> the second server without having its home/remote interface.
> I means that
>
> Object o = context.lookup("EjbFromSecondServer");
>
> throws an CNF exception if EjbFromSecondServer's home/remote
> interfaces are unknown for a client.
>
>
>
>
> James Cook wrote:
> >
> > ----- Original Message -----
> > From: "Alexander Kogan" <[EMAIL PROTECTED]>
> >
> > > > As I said before, server architectures get around multi-vm bean lookup
using
> > > > various mechanisms. Borland uses a "smart-broadcast" technology called
> > OSAgent.
> > > > Other servers use a federated namespace, or a single name service. I was
> > trying
> > > > to setup the single namespace approach with jBoss, but it looks like it
> > can't be
> > > > run that way. At least, it appears that the container will not deploy
beans
> > > > unless it has its own (local) name service running.
> > >
> > > Sorry, but it's not true. I'm successfully running two jBoss servers
> > > bounded to
> > > one jnp NameServer (the primary server has the standard configuration
> > > with embedded
> > > naming and the second server uses nameservice from the primary server).
> > > Works
> > > quite well. If you need details, I'll can describe the setup.
> >
> > This is exactly what I would like the details on. Please describe.
> >
> > jim
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
>
> --
> __________________________________________________
> Alexander Kogan  PTC   www.ptc.com
> [EMAIL PROTECTED]    140 Kendrick St. Needham MA 02494
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>


_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to