This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
We have a clustered environment (Websphere v6.0) with 2 physical servers hosting 1 app server each. We are noticing that our client is not load balancing between the two servers. with regards to WLM, is there something that the client could have missed? They are using the clustered jndi lookup...
Originally posted by Terry Schulting: We have a clustered environment (Websphere v6.0) with 2 physical servers hosting 1 app server each. We are noticing that our client is not load balancing between the two servers. with regards to WLM, is there something that the client could have missed? They are using the clustered jndi lookup...
I take it this is an EJB client? Is this a stateless session bean?
Kyle, yes this is an EJB client and the bean in question is a stateless session bean.
posted 11 years ago
OK, as I remember it (I'll have to go back and read my own book on this one!) we do have some localization of requests from the EJB client. Is what you're seeing that you create one client stub, send a bunch of messages from it to the servers, and they all go to the same server? If so, that's normal.
On the other hand, if you create multiple client stubs in either the same program or in different programs then you should see the requests from the different stubs spread across both servers.
Also, if you bring one server down you should see transparent failover to the other server as well in any case.
As it turns out, the client was not using the Websphere Application Client. No form of it (thin client, j2ee application client, not even the pluggable client). so, after pulling in the IBM jvm and the j2ee application client, we are noticing that load balancing and failover is occurring. One issue or question though. We do not want to use the IBM jvm. The client code that is running is compiled with jdk1.5, and the application client that comes for WAS 6 is only 1.4.2 compliant (from what we can tell). So, the question is this. Is it possible to 'overwrite' the JRE that is used plugging in a jre 1.5 sun version? I say yes (it appears to work), but are there any issues in doing this that anybody is aware of?
After some pecan pie, you might want to cleanse your palatte with this tiny ad: