Hi,
We are having an issue with our custom bean-load-balance-policy when used with PooledInvokerHA. Jboss is not using the custom policy and doing routing on Round Robin basis.
App Server : jboss 5.1.0 GA
EJB - Stateless session beans ( EJB 2.1)
This works fine if we use JRMPInvokerHA , but for performance issues we are trying to switch to PooledInvokerHA. When we use PooleInvokerHA we see in the logs that jboss is executing the custom policy but stiil it doesn't route as per that instead it routes on round robin basis..
jboss.xml
<session>
<ejb-name>WorkerHome</ejb-name>
<jndi-name>WorkerHome</jndi-name>
<local-jndi-name>WorkerLocalHome</local-jndi-name>
<clustered>True</clustered>
<cluster-config>
<partition-name>${jboss.partition.name:DefaultPartition}</partition-name>
<home-load-balance-policy>org.jboss.ha.framework.interfaces.RoundRobin</home-load-balance-policy>
<bean-load-balance-policy>CustomRouterJBoss</bean-load-balance-policy>
</cluster-config>
</session>
standarjboss.xml
<invoker-proxy-binding>
<name>clustered-stateless-rmi-invoker</name>
<invoker-mbean>jboss:service=invoker,type=pooledha</invoker-mbean>
<proxy-factory>org.jboss.proxy.ejb.ProxyFactoryHA</proxy-factory>
<proxy-factory-config>
<client-interceptors>
...........
Is there any known limitaion of using PooledInvokerHA with custom load balancing policy ? Appreciate any help.
Thanks, Ashvin
Update - We found an issue with the custom routing code, we were not using right API to get the server node name after changing that it worked fine.