JBuilder JSPs that use connection caches to retrieve ResultSets

This section describes how to troubleshoot problems associated with JSPs in JBuilder that retrieve ResultSets using EAServer connection caches. For information about creating JSPs in JBuilder that perform this task, see the Sybase white paper, Create JSP in JBuilder to Retrieve ResultSet from EAServer Connection Cache,.

Troubleshooting JSPs in JBuilder

Verify your configuration—see “Verifying your configuration”.
If the JSP does not compile, review the content of the JBuilder Messages pane for information about why the compilation failed.
If attempts to deploy the Web module fail:
1. Review the content of the JBuilder Messages pane for information about why the deployment failed.
2. Verify that EAServer is running.
3. Verify that the server name and port number in the project deployment settings match the actual running server and HTTP listener.
If the Web browser displays a “page not found” error:
1. Verify that EAServer is running.
2. Verify that the HTTP listener can process requests by attempting to access the default documentation page; for example, http://serverName:8080.
3. Restart EAServer.
If the Web browser displays an exception, or a message that indicates there is a problem with the page; for example, “internal server error 500”:
1. Check the EAServer log files Jaguarhttpservlet.log and Jaguar.log for error details.
2. Add an error page to the JSP, then rebuild and redeploy the project. For example:
  1. Add the following line to your JSP:
```
<% page errorPage=”jsp2_error.jsp” %>
```
  2. Create a new JSP named jsp2_error.jsp with the following content:
```
<%@ page isErrorPage="true" %>
<html>
<body> 
<h1>Error page</h1>
<br>Error occurred in the JSP: <%= exception.getMessage() %>
<Br>Stack Trace:
<% 
java.io.CharArrayWriter cw = new java.io.CharArrayWriter(); 
java.io.PrintWriter pw = new java.io.PrintWriter(cw,true); 
exception.printStackTrace(pw); 
out.println(cw.toString()); 
%>
</body>
</html> 
```
If you make any changes to the Web application, you must rebuild the WAR file before redeploying it to EAServer; otherwise, the WAR file does not include your changes.