To respond to my posting, I've gotten the PoolInvokerHA working.
To do this I copied and pasted the PooledInvoker entry in jboss-service.xml,
appended HA to the class name, and made the MBean name unique (e.g.,
jboss:service=invoker,type=pooledha). Once I had my PooledInvokerHA MBean
defined I followed the instructions on
http://www.jboss.org/wiki/Wiki.jsp?page=PooledInvokerConfig with the only
difference being that I used the PooledInvokerHA MBean for the clustered
<invoker-proxy-bindings> entries.
The only issue I ran into was that the PooledInvokerHA attribute,
ClientConnectAddress, was initially set to ${jboss.bind.address}. For my
environment the ${jboss.bind.address} resolves to 0.0.0.0. So after the JNDI
lookup it appeared that the client was attempting to use 0.0.0.0 to incorrectly
connect to itself (running the client and server locally was fine but running
the client and server on separate boxes caused problems). To resolve I simply
removed ClientConnectAddress entry entirely --which I read somewhere then calls
InetAddress.getLocalAddress(). With the attribute removed the ciorrect IP of
the server was set in the ClientConnectAddress.
After working past the above, the PooledInvokerHA is working well and the
cluster is behaving much better under higher loads.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860908#3860908
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860908
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
