Paging queries or paging records is an often-used approach in web applications. It displays subsets of data records as a page, allowing the user to navigate more easily through all pages. The straightforward implementation of a paging query running over large data sets in a stored procedure in MS SQL 2005 can cause increased server load when large numbers of paging queries are executed simultaneously.

Recently, we’ve been dealing with an issue related to our Tomcat Application Server and wanted to share how we solved this one. We found one that the application server was irrelevant (it could be Glassfish or another as well). The server was running the latest version, Tomcat Application Server 6.0.18, and it was crashing in irregular intervals. There was no easy solution because the server stopped making logs before crashing.

Developers who have used NetBeans 6.1 and 6.5 for web development with Visual JSF (Woodstock) might have encountered an issue with their web application when deployed on a secured server (HTTPS) and opened with Internet Explorer. The issue lies in the way IE treats links to JavaScript and CSS files loaded in the pages. Under HTTPS, the links to JavaScript have to be absolute, not relative. IE does not assume that the “relative” folder is secured.