Just to clarify, I'm not using ACC at all. This is simply submitting requests from a simple client app straight to the ORB port (localhost:33700) on either host. There's no interaction with any external load balancing going on. The app generates reports - so a report generation job is submitted to ORB, and out plops a report at the other end (on the filesystem). Also there's no session persistence/availability set. I suppose I was slightly surprised at first to see that submitting a job to ORB on one node does actually run on the other - it just doesn't seem to balance across nodes in a very fair way from what I see! I don't know if this behaviour can be configured anywhere within the app server?
If I stick a load balancer in front of the ORB ports on each node, even just distributing in a simple round-robin fashion, I still see the same behaviour in that a bunch of job submissions run on one node, then some poinrt later it seems the other node decides to do all the work,
[Message sent by forum member 'ocoro02' (ocoro02)]
http://forums.java.net/jive/thread.jspa?messageID=242535