tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Frankson" <dfrank...@qwest.net>
Subject Re: AW: Java program interferring with Tomcat
Date Mon, 19 Nov 2001 19:42:16 GMT
> Not with SQL Server.  If thread A has a write lock on a table, thread b
will
> wait until the write is completed before reading.  If thread A is in a
> transaction that is long running then a perfectly funcitoning application
> can seem to hang.  Its also possible that some form of infinite loop or
> deadlock in thread A could cause it to never release the transaction,
making
> you either kill the application or use Enterprise Manager to kill the
lock.

Does changing the transaction isolation level affect things?  The tomcat
application is a high traffic transactional system, and the commandline app
is a read-only data export tool that fires off twice a day.  Both are set to
TRANSACTION_READ_COMMITTED.

Dave




--
To unsubscribe:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands: <mailto:tomcat-user-help@jakarta.apache.org>
Troubles with the list: <mailto:tomcat-user-owner@jakarta.apache.org>


Mime
View raw message