"It looks like you already have a discussion going on related to this topic. Frankly, I think you've made a poor choice of architecture (Tomcat) for your requirements (reports churning through huge amounts of data).
"
I'd be inclined to move the report functionality off into another application and have a light web application that submits report requests to that app. The report app can send users the reports via email or upload the report somewhere that Tomcat can access and include a URL to the report in the email."
Originally posted by Rama Krishna:
Any suggestions on free to use servers for displaying or processing huge reports or database data? Anyways, we do not have much of a choice as we cannot afford and so lets assume that Tomcat is the server.
Originally posted by Rama Krishna:
1. How do we stop a running (a particular session) method in Tomcat by just a user click
Originally posted by Rama Krishna:
2. what is the best way to stop displaying or catching any kind of exceptions/errors from being displayed in the users display page?
Originally posted by Rama Krishna:
3. safe way to close a hibernate session, we had to comment out the session.close() or session.flush() in our method that returns the current session or that creates a new session for use.
Tomcat can handle the complex front end stuff (multiple simultaneous users, authentication). All you need is something to run reports. I've got many examples that are simple daemon processes, all of 200 lines of code, that read requests off a JMS queue and process them.
I am far from a hibernate expert, so you'd be best to ask this in the Hibernate forum. I've been using an interceptor like the example on page 54-55 of Ted Husted's Struts 2 from Square One and it works fine for my purposes.
Originally posted by Rama Krishna:
I was unable to download the interceptor or able to find an example as I could not get access to Ted Husted's Struts 2 book. Any suggestions where I can get I can access it easily?