servlets - Session values are not retained even tough Jsession remain same second time access -
after doing analysis original problem listed in second section found issue due 304 response below detailed explanation.
i have developed web application users clicks on link , takes him servlet set few session variables , forward jsp. first time when access application things work fine after closing browser , opening browser , accessing application null pointer exception in jsp because trying access session data reason getting 304 response servlet , means servlet not invoked , jsp getting called ? since servlet not called session values not set .
is understanding correct.
i observing in ie9
--------------------- original question below --------
we have integrated siteminder in our application , have observed siteminder cookie sm session created different domain application specific cookie created proper domain.
for every request see new smsession value application cookie remains same , though cookie remains same values set in session using servlet not available in jsp.
i have printed jsession id, jsession id same request.
below flow.
user hits url siteminder intercepts , asks credentials once user logs in redirected servlet set few values in session dispatch control index.html has 2 frames . loading 2 jsp these frames , in these jsps trying access session values unable .
i observing behaviour in ie9 ie8 behaves correctly, first time access works fine second time not in ie9
can let me know if change in smsesson incurs changes in httpsession java app ? don't think jsession id remains same.
what possible reason this.
have checked if jsps being called in frames has same session id 1 in servlet?
to give background on smsession , jsession:-
the smession id cookie keeps getting changed web agent periodically , tagged base domain. example - if application hosted @ a.b.com - jsession id typically set domain a.b.com , smsession set b.com domain. default siteminder behaviour since assumes applications in b.com domain need cookie sso. can change using aco agent either setting domain name explicitly or setting scope of domain needs used. unless application has logic depends on value of smsession id , modifies java session, jsessionid cookie not impacted change in value of smsession
Comments
Post a Comment