Thanks for your replies. I guess I'm seeing the behaviour that Brian described,
where my client gets the EJB-proxy, and since the EJBs are configured as
clustered, all calls to that EJBs are load-balanced.
I just remembered that we had to manually set the invoker-proxy-bindings to
support
Possibilities include:
1) Don't mark the bean as clustered if you don't want it clustered. The only
clustering behavior an SLSB has is failover and loadbalancing; if you don't
want that then there is no point making the bean clustered.
2) Only deploy the bean on the server you want, or deploy
Actually, load-balancing is not bad at all. It's just that our testers should
test the system before it goes into production, and they should of course test
a system that is as close to the final production version as possible.
This pretty much rules out all the options you have mentioned. But
Btw, all nodes are running on the same server with the same IP address. Might
this be important?
Martin
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024301#4024301
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4024301
I think you understanding is correct; at least it matches mine. :)
I was unable to replicate your findings using JBoss 4.0.5. I used multiple IP
addresses rather than the service binding manager but I wouldn't think that
would matter. When I bound objects locally on both nodes and then
Perhaps you are confusing the behavior of the naming proxy vs. the EJB proxy?
They are completely independent. If that's not what you're doing, ignore the
rest of this, and just treat it as useful info for other people who stumble on
this thread. ;-)
If you create an InitialContext that
