Bizarre problem -- works fine, then doesn't

[Ethan Michaels <et...@dnai.com>]

Hi Tomcat experts. I have installed Tomcat on Linux and created two Web
applications, one fairly simple and one more complicated. The server works
great, and both Web apps run perfectly when I leave work in the evening and
when I test them from home at night. But when I get to work the next day
they are both having problems. The thing is, the Tomcat is still running
and delivering the initial pages of the Web apps, but beyond that nothing
seems to work right.

I have discovered that restarting Tomcat returns everything to smooth
functioning. It appears that somehow, in the middle of the night, some
condition changes and causes the Web apps to fail. What could be happening?

Thanks,

Ethan

Re: Bizarre problem -- works fine, then doesn't

[Matt Goss <mg...@rtci.com>]

are you closing you resultsets and prepared statements before you try closing the
connection?
ie:
rs.close();
ps.close();
conn.close();
Matt

Ethan Michaels wrote:

> I was not calling close() on some database connections. That may have been
> the problem. It's hard to tell because in the course of fixing that I
> created some other problems that I'm still in the middle of debugging. If
> any useful information emerges, I'll let y'all know.
>
> I can say that previously, when the applications were displaying the bad
> behavior I described in my original message, there were no error messages
> in the console.
>
> Ethan
>
> >> I have restarted Tomcat again this morning, and all the material that was
> >> in the logs is no longer there (since the restart). That seems a little
> >> weird. Is that normal?
> >
> >Yeah. I'm not sure if I like that either.
> >
> >> Anyway, I recall that none of them had anything that looked like an error
> >> message. The jasper log recorded a series of requests and the parameters
> >> that were sent. The servlet log just had a series of about 15 entries that
> >> began with
> >
> >This was my stupid, java errors show up on the console you started tomcat
> >on, not in the error log. Sorry about that.
> >
> >> Meanwhile, I'll explore this dropped database connection concept. Maybe
> >> there's something to that.
> >
> >I actually have two seperate errors regarding DB stuff but I haven't had
> >time to track them down yet. If you can, check your tomcat startup console
> >to see what happens.
> >
> >(And let me know what happens, too, 'cuz maybe it'll help me out :D
> >
> >Dave
>
> ====================================
>
> Ethan Michaels
> Graphics
>
> METROPOLITAN TRANSPORTATION COMMISSION
> Transportation planning, financing, and
> coordinating for the San Francisco Bay Area
> http://www.mtc.ca.gov/
>
> ====================================

RE: Bizarre problem -- works fine, then doesn't

[Ethan Michaels <et...@dnai.com>]

I was not calling close() on some database connections. That may have been
the problem. It's hard to tell because in the course of fixing that I
created some other problems that I'm still in the middle of debugging. If
any useful information emerges, I'll let y'all know.

I can say that previously, when the applications were displaying the bad
behavior I described in my original message, there were no error messages
in the console.

Ethan


>> I have restarted Tomcat again this morning, and all the material that was
>> in the logs is no longer there (since the restart). That seems a little
>> weird. Is that normal?
>
>Yeah. I'm not sure if I like that either.
>
>> Anyway, I recall that none of them had anything that looked like an error
>> message. The jasper log recorded a series of requests and the parameters
>> that were sent. The servlet log just had a series of about 15 entries that
>> began with
>
>This was my stupid, java errors show up on the console you started tomcat
>on, not in the error log. Sorry about that.
>
>> Meanwhile, I'll explore this dropped database connection concept. Maybe
>> there's something to that.
>
>I actually have two seperate errors regarding DB stuff but I haven't had
>time to track them down yet. If you can, check your tomcat startup console
>to see what happens.
>
>(And let me know what happens, too, 'cuz maybe it'll help me out :D
>
>Dave






====================================

Ethan Michaels
Graphics

METROPOLITAN TRANSPORTATION COMMISSION
Transportation planning, financing, and
coordinating for the San Francisco Bay Area
http://www.mtc.ca.gov/

====================================

RE: Bizarre problem -- works fine, then doesn't

[Dave Newton <da...@solaraccess.com>]

> I have restarted Tomcat again this morning, and all the material that was
> in the logs is no longer there (since the restart). That seems a little
> weird. Is that normal?

Yeah. I'm not sure if I like that either.

> Anyway, I recall that none of them had anything that looked like an error
> message. The jasper log recorded a series of requests and the parameters
> that were sent. The servlet log just had a series of about 15 entries that
> began with

This was my stupid, java errors show up on the console you started tomcat
on, not in the error log. Sorry about that.

> Meanwhile, I'll explore this dropped database connection concept. Maybe
> there's something to that.

I actually have two seperate errors regarding DB stuff but I haven't had
time to track them down yet. If you can, check your tomcat startup console
to see what happens.

(And let me know what happens, too, 'cuz maybe it'll help me out :D

Dave

RE: Bizarre problem -- works fine, then doesn't

[Ethan Michaels <et...@dnai.com>]

I have restarted Tomcat again this morning, and all the material that was
in the logs is no longer there (since the restart). That seems a little
weird. Is that normal?

Anyway, I recall that none of them had anything that looked like an error
message. The jasper log recorded a series of requests and the parameters
that were sent. The servlet log just had a series of about 15 entries that
began with

Context log path= ...

I don't remember exactly what was in the Tomcat log. I'll have to wait til
the thing stops working again and take a look. Meanwhile, I'll explore this
dropped database connection concept. Maybe there's something to that.

Thanks,

Ethan

>> I have discovered that restarting Tomcat returns everything to smooth
>> functioning. It appears that somehow, in the middle of the night, some
>> condition changes and causes the Web apps to fail. What could be
>> happening?
>
>So, ah, is the only information you have to go on? For instance, what's
>in the logs? (Is there a dropped database connection, like there was in
>mind?)
>
>Dave






====================================

Ethan Michaels
Graphics

METROPOLITAN TRANSPORTATION COMMISSION
Transportation planning, financing, and
coordinating for the San Francisco Bay Area
http://www.mtc.ca.gov/

====================================

RE: Bizarre problem -- works fine, then doesn't

[Dave Newton <da...@solaraccess.com>]

> I have discovered that restarting Tomcat returns everything to smooth
> functioning. It appears that somehow, in the middle of the night, some
> condition changes and causes the Web apps to fail. What could be 
> happening?

So, ah, is the only information you have to go on? For instance, what's
in the logs? (Is there a dropped database connection, like there was in
mind?)

Dave