This content has been marked as final. Show 1 reply
JBoss is trying to resolve the call locally, something that is A Good Thing(tm) to improve performance.
You can put a jndi.properties in your classpath so that it does not try to call ejb locally and uses RMI instead, but I wouldn't recommend it. Since RMI serialization is a mayor performance boo, leeting it just as is should be fine. Also, JSP processing seems to take a part of your overall performance, so letting always the same node doing it should not be a good idea.
Instead, put an Apache/Tomcat/Jetty before both servers doing the load-balance. You also should have to check the sticky sessions bit (I don't know how that is achieved, nor if it is possible in Apache). Forward the post still as http, don't call RMI remote.