This week's book giveaway is in the Design forum.
We're giving away four copies of Design for the Mind and have Victor S. Yocco on-line!
See this thread for details.
Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Does Tomcat Timeout?

 
Charessa Reilly
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What would make a JSP not finish running and not throw an error?

I have a JSP that queries an MS Access database, which is a very slow process (we're hopefully going to be using an Oracle database soon). But this code I've been using has always finished executing before.In addition, the page is displaying information that is in the page well after the connection the database is closed.

After it takes the information from the database it puts that information in some beans that I've written for this app. The beans have been working normally in a nearly identical set of code in a different JSP.

It then iterates through the list made of the data (a list of 35 items, which is the count it gives me when I have it display the size of the results) and displays data from up to 10 rows that meet certain criteria. It does fine through 15 iterations then stops without any error (showing 5 of the 23 records that meet the criteria). Then it just stops. No error, nothing else. It just shows me the output line at the end of the loop then stops.

Is there a timeout setting in Tomcat that I can extend? And if there is, does the timeout record an error?
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64700
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is unlikely to be caused by any sort of time-out. Rather is sounds just like what happens when an exception occurs. This may not result in any error being shown by the browser.

Have you combed the logs for any stack traces?
 
Charessa Reilly
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yeah, there are times when I just feel like I'm in the wrong position.

I'm used to working in PHP and Perl - I would get errors right in my face as soon as I ran them. I'm used to seeing it in one place.

So when the console shows SOME things -- the stuff I wrote into my bean to display -- but doesn't show me a stack trace, i forget I have these handy logs.

SOooo yeah. I was still using an old version of a bean. Which was causing the failure. Time from checking log to successfully testing the fix: 2 minutes.

>.< Sorry to bug everyone with my ineptness.
 
Bear Bibeault
Author and ninkuma
Marshal
Pie
Posts: 64700
86
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you learned something from the exercise (such as now knowing to look in the logs and to recognize when behind-the-scenes exceptions are boofing things up), then no one's time was wasted.

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic