Tomcat Deadlock 2004-01-09 - By Ralph Einfeldt
Back
Can just answer the easy one:
If a browser is closed in the middle of the request
doesn't change the way the request is processed.
If the application is waiting on a lock, it will keep
waiting. There is just one way to find out if the browser
has been closed: write to the output stream (but that
isn't very precise due to buffers and caches).
Sorry for the rest.
> -- --Original Message-- --
> From: Hooper, Brian [mailto:brian.hooper@(protected)]
> Sent: Friday, January 09, 2004 5:19 PM
> To: Tomcat Users List
> Subject: Tomcat Deadlock
>
> After that, the site was no longer accessible. The
> only way to get it working again was to restart the Tomcat service.
>
> Looking at the various log files, the only entry that appears
> interesting is the following from the site's log:
> 2004-01-09 10:43:18 StandardWrapper[/WIPT:action]: Waiting for 2
> instance(s) to be deallocated
>
> I'm using tomcat 4.1.27 with SQL Server 2000 on a Win2K box.
> I've been
> having similar problems off and on for the last couple of
> weeks and have
> tried a number of different things to fix it. I made sure I
> closed all
> connections, statements, and result sets. I put all of the close code
> in a finally block. Another quick question - if the browser is closed
> in the middle of an operation, is the code in the finally block
> executed?
>
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)
|
|
