Add some debugging logging into your servlet to see what is being returned by your query, and also where you are forwarding to.
For example Page is null...at least, I can't see where it is set.
There are a few things I would suggest about the code.
First off, create a model class to represent your data, instead of adding each individual bit of data from a row as a separate entry in your List.
Second, when handling your exception, print the stack trace, not just the exception, otherwise you wont know exactly where the error occurred.
Third, you're not closing your Connection, so you'll eventually run out. You ought to be using a connection pool in a web app, but you can look into that at your own pace.
Finally, the resources (connection, statement and resultset) all ought to be closed in a finally block, or you should use a try-with-resources.
That way you ensure you don't leak any resources (which database connections are).
Oh, and JSP pages shouldn't have code snippets in like that. Again, look into EL (espression language) to see how you can print out a list of stuff, and format it, in a JSP.
I'm surprised you weren't mauled by the Bear for that.
As you have now discovered, it's a really task to try and debug Java code that's embedded in scriptlets on a JSP page. So take Dave's advice. Move the Java code to a java class source file and read up on how to do model/view/controller design with servlets and JSPs.
When it comes to destroying a civilization, gas chambers cannot hold a candle to echo chambers.