Clustering Stateless EJB in 3.2 Problem

[toddmcf2002]

Hi,

I'm using 3.2 and a Stateless Session Bean. RoundRobin EJB works great when the caller is a java client outside of the server JVM, but when JSP does the EJB call it pins to the node hosting the JSP.

I searched the forum on this and I've tried every combination of caching (and not caching) the Home interface and the Bean itself to no avail. It always gets pinned.

I've used RoundRobin, FirstAvailableIdenticalAllProxies and FirstAvaliable.

I've tried a blank URL (discovery), a list and localhost:1100.

Again, it works great outside of the Server (remote client) but pins to the node hosting JSP the JSP page.

Please help,

Thanks,
- Todd

[toddmcf2002]

I'm using Tomcat 4.1 now outside of the JBoss JVM to make this work. Sadly, nobody responded to my inquiry :(

The 3.2 doc seems to insist this works inside the server VM but as far as I can tell that's not accurate.

If someone can chime in I'd be really grateful. I'd rather not have all this server indirection.

Thanks,
- Todd

[slaboure]

This is by design: jboss will use the target in the local JVM if it is available and, in this case, will not load-balance.

If you want two boxes, deploy EVERYTHING two times i.e. the app server AND the servlet server and put a load balancer in front of them, this way you will get more performances.

Cheers,

sacha