Please reply soon... to my mail firstname.lastname@example.org or here.
What did the clients see ? any error ? blank page ? whats the view source of it?
.I am confused because some clients are able to see the login page but some are not.Is it due to some problem related to printwriter class[out object] which is unable to write the response back to the HttpResponse object?
It cant be. response writer behaves same for all client
There are many cases to be evaluated.. check logs for any errors ? app log , context log or SOP .
if logs are fine , then issue can be only sorted through brainstorming questions..
What browsers do they use ? do they same clients alternate behavior? or is the problem with same clients.
If this happens then it must be same for all the clients. Right?
Only if they are using identical browsers with identical settings performing identical requests.
Did you actually check your code to see if all possible paths result in closing the output stream? Did you check the logs for errors? Did you "view source" to see if any output has been received? When you have experienced servlet developers giving suggestions, you should follow up.
client is getting blank page and waiting for long to get any response.After few minutes browser is showing timeout error.
Perhaps your code is throwing an exception which is not being properly recorded. I have yet to see where you examined all the log files and found no errors.
Am I correct in assuming that this "login page" does not involve database access for the initial display?
Souvik Basu wrote:Yes all of them are using same browsers.But don't know about the settings.Yes output streams are closed.Those who are not been able to access,when they try to "view source" nothing is showing [probably nothing is responded back].Is it possible that due to some difference in settings browsers will behave differently?If it is so, then please tell me what to do to change the settings.And this problem is occurring mainly in the corporate access.Is it due to the fact that corporate firewall setting is blocking our response?
If you still suspect firewall , access simple html and see if you get the complete html page , then there is no issue with firewall , but with the browser settings..