Frankson [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 19. November 2001 18:17
An: tomcat-user
Betreff: Java program interferring with Tomcat
I have a server running Tomcat 4.0 on Win2k with the Sun
VM JRE 1.3.1. At 11am each day I have a commandline Java
program scheduled to run using
Ralph Einfeldt wrote:
Sounds like a deadlock on the database.
To verify that have a look at the server manager
to see if there are locks.
I agree with Ralph, that the problem is probably in your SQL access.
Do *both* processes hang (e.g. Tomcat the scheduled job) or only
Tomcat?
I would
on
Win2k?
Dave
- Original Message -
From: Denis Haskin [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Monday, November 19, 2001 12:09 PM
Subject: Re: AW: Java program interferring with Tomcat
Ralph Einfeldt wrote:
Sounds like a deadlock on the database
David Frankson wrote:
Only Tomcat hangs, the other program continues on. I thought a database
deadlock only happens when both threads are trying to write and holding a
lock on each other's data? The external java process is read-only.
Hmm. That's why I asked. Sounds like maybe the db
]
To: tomcat-user [EMAIL PROTECTED]
Sent: Monday, November 19, 2001 12:17 PM
Subject: Java program interferring with Tomcat
I have a server running Tomcat 4.0 on Win2k with the Sun VM JRE 1.3.1.
At 11am each day I have a commandline Java program scheduled to run using
Window's scheduler. When
-Original Message-
From: David Frankson [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 19, 2001 1:42 PM
To: Tomcat Users List
Subject: Re: AW: Java program interferring with Tomcat
Only Tomcat hangs, the other program continues on. I
thought a database
deadlock only
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
To: Tomcat Users List
Subject: Re: AW: Java program interferring with Tomcat
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
: AW: Java program interferring with Tomcat
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