• 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
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

WebSphere losing session stickiness

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Folks,

I had this issue dropped in my lap this morning - I'm seeking some direction on where to look first to identify what's causing this problem. Of course any "you can fix it in 10 minutes if you do this..." reply is always welcome!

Issue: A web client clicks on a link (which of course creates a WAS request) on a web page on our site, and receives their information correctly. Clicking on a *different* link on the same page occasionally results in the client needing to refresh their browser to receive the new info. The application folks tell me that when this happens they're getting a different cookie than the one they started the session with.

My guess is that WS Load Balancer (Network Dispatcher) is overriding (or losing) the stickiness of the session due reaching a WAS load threshold, but I'm not certain.

We're using WSLB (ND) 5.0 and JRE 1.3.1 as follows:

Internet|-------------- DMZ ------------|-------- Network--------------|

..........-- ND1(pri)--....-- proxy A --....-- ND3 (pri) --....-- WAS1
Client-|.................|--|................|--|..................|--|
..........-- ND2(bu) --....-- proxy B --....-- ND4 (bu) --....-- WAS2


(Doh! Please ignore the .dots, it was the only way I could get the drawing to line up reasonably close. and yes, I know it looks like crap)

I don't have the WAS version info yet. I'm in the process of getting more info from the application folks, but any suggestions at this point would be greatly appreciated.

---------------------------------------------------------------------------
A quick update:
There are two, sometimes more, ASPSESSIONID cookies associated with the client (WSLB) address in the IIS logs. Back to the same question question as to what might cause multiple cookies...
[ February 15, 2006: Message edited by: Dave Lieberman ]
 
author & internet detective
Posts: 42105
933
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dave,
As you can guess, you really need more information to solve the problem.

When searching, try looking for "session affinity" and "session replication."
 
Don't MAKE me come back there with this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic