• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Websphere Clustered Environment

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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...
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

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
 
Terry Schulting
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Kyle, yes this is an EJB client and the bean in question is a stateless session bean.
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.

Kyle
 
Terry Schulting
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Kyle, I PM'd you. to answer this question, we are locating and caching a Home object. We then use that Home Object for all calls...
 
Kyle Brown
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Terry Schulting:
Kyle, I PM'd you. to answer this question, we are locating and caching a Home object. We then use that Home Object for all calls...



I replied to your PM. BTW, there's no need to cache a Home in WAS. We added an internal cache for this two or three versions ago...

Kyle
 
Terry Schulting
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
reply
    Bookmark Topic Watch Topic
  • New Topic