Plus, those headers are still incomplete and not crossbrowser compatible.
as I said it's not a good practice to invalidate a session when you are going to forward to a error page.
I say this because it is best practice to put all logic in beans or servlet code and keep JSPs for layout only. Using a session heavily is a bad practice because it requires a lot of memory to utilize those variables you put into it.
Although the code is working, my concern is will it cause the exception message to loose before it can be displayed in the JSP page.
Database Exception.*; public class Attendence Info Upload extends Http Servlet in the catch block.
Suppose a client has name, age and number attributes.