I think it shouldn't matter which server originated the handle. It should
always work as long as a container is running the bean somewhere. This is
what the robust containers do, so should jBoss.
Sachay and Stacy have proposed/implemented some ideas for how to achieve
high-availablity. This (or a similar technique) should be the goal.
jim
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jason
> Dillon
> Sent: Thursday, April 26, 2001 3:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] Remote Proxies do not know the server they came
> from
>
>
> I spent some time (long ago...) fixing this very problem, but I have not
> really had time to integrate it into the latest codeline. I can put some
> more effort into fixing this soon.
>
> Does anyone happen to know what the EJB spec says about handles
> and if they
> should return bean refs to the *exact* server which they came from? I can
> not recall any real detail about handles except that they are
> used to allow
> clients to restore a reference to a given bean.
>
> Any ways, I do not think that this will take that long to fix. I can
> probably make this optional too (via a property that will enable the new
> behavior). The only problem that I remember running into was
> when the proxy
> is generated there isn't an easy way to find out what the
> provider url is for
> the current machine (in a non-jboss specific fashion). Perhaps that has
> changed.
>
> What I might do is force users who are interested in this, to provide some
> extra properties (or another jndi properties file) that specifies
> the exact
> environment properties required to restore a bean from a handle.
>
> --jason
>
>
> On Thu, 26 Apr 2001, Alf Werder wrote:
>
> > Hi,
> >
> > The last two months I made my first experiences with jboss as a bean
> > developer. I am really surprised and impressed by the work, that is
> > done. But now, the first serious problem arised.
> >
> > In an EJB client a tried to obtain the home interface of a bean from its
> > remote interface. But a call to EJBObject.getEJBHome() throws an
> > exception. That was the first sign. Later, I tried to use a HomeHandle
> > to reobtain a home interface after a server restart.
> > HomeHandel.getEJBHome() throws an exception.
> >
> > I had a deeper look and found the problem: My code was
> >
> > Hashtable env = new Hashtable();
> > env.put("java.naming.factory.initial",
> > "org.jnp.interfaces.NamingContextFactory");
> > env.put("java.naming.provider.url", "localhost:1099");
> > env.put("java.naming.factory.url.pkgs", "org.jboss.naming");
> >
> > MyHome home = (MyHome) new InitialContext(env).lookup("MyHome");
> > MyHome h = (MyHome) home.getHomeHandle().getEJBHome();
> >
> > The last line throws the exception. It works, when I change the code to:
> >
> > Hashtable env = new Hashtable();
> > System.setProperty("java.naming.factory.initial",
> > "org.jnp.interfaces.NamingContextFactory");
> > System.setProperty("java.naming.provider.url", "localhost:1099");
> > System.setProperty("java.naming.factory.url.pkgs",
> "org.jboss.naming");
> >
> > MyHome home = (MyHome) new InitialContext().lookup("MyHome");
> > MyHome h = (MyHome) home.getHomeHandle().getEJBHome();
> >
> > So had a look into the jboss source code. The HomeHandle implementation
> > simply does not know the server, is came from. It just creates a new
> > inital context without any Arguments. So it gets the local root context,
> > which is not the context its home interface is bound to.
> >
> > -alf
> >
> >
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
