JSP issue in JavaBean or Netwok settings?

Hi,

I have a JSP application running on Tomcat server 4.1.31.
We have issue with the application as stated below:
First user logged in as user “A”. After he logged out, user “B” logged in, however system will show that the user is logged in as the previous user “A”.

It works perfectly in some network; however it doesn’t work as it should be in other network. It has this problem only in certain network or ISP configuration.
We noticed those computers in the network that has problem with “tracert” command has issue in our JSP application.

Please see the following link for detailed explanation, screen shot of the "tracert" and the sample JSP codes
http://s18.yousendit.com/d.aspx?id=1JKZQ21Y0B6N40TFYOOA46Q1UF

Please advise, Thanks.
rospccAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

fargoCommented:
Hi,

in a quick check, when the user is logging off, does it give some errors?

try {
      ev.addRecord("Logout", "Logout", "Logout", UserInfo[2], UserInfo[11], UserInfo[10]);
}catch(SQLException SE) {}

catch the exception here and see what is happening up.
may be it couldn't logoff the first user. Just a guess.

fargo
0
rospccAuthor Commented:
The log off didn't give any issue. It works perfectly in most of the networks.
0
rospccAuthor Commented:
I've found the solution by forcing the network to clear the cache with the codes below:
<%
        // Set to expire far in the past.
        response.setHeader("Expires", "Sat, 6 May 1995 12:00:00 GMT");
        // Set standard HTTP/1.1 no-cache headers.
        response.setHeader("Cache-Control", "no-store, no-cache, must-revalidate");
        // Set IE extended HTTP/1.1 no-cache headers (use addHeader).
        response.addHeader("Cache-Control", "post-check=0, pre-check=0");
        // Set standard HTTP/1.0 no-cache header.
        response.setHeader("Pragma", "no-cache");
%>

Thanks
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

rospccAuthor Commented:
How do I close this question?
0
VenabiliCommented:
0
GranModCommented:
Closed, 250 points refunded.
GranMod
The Experts Exchange
Community Support Moderator of all Ages
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
JSP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.