Killing long running processes

Poster	Content
jrogers nk4um User Posts: 101	<div>See <a href="http://1060.org/forum/topic/284" target="_new">http://1060.org/forum/topic/284</a> for more on this topic.</div> 2009-10-17T06:25:13.000ZOctober 17, 2009 06:25db timeouts See http://1060.org/forum/topic/284 for more on this topic.
tab nk4um Moderator Posts: 485	<div>Hi Gary,<br/><br/>unfortunately one limitation of the thread termination capability in java seems to be that it cannot interrupt IO. I would guess this is the situation with a remote database call.<br/><br/>The standard connection pool has the ability to specify timeouts. If your custom one has that ability that might be the way to go.<br/><br/>Cheers,<br/>Tony</div> 2009-09-23T22:17:21.000ZSeptember 23, 2009 22:17limitation of the jvm Hi Gary, unfortunately one limitation of the thread termination capability in java seems to be that it cannot interrupt IO. I would guess this is the situation with a remote database call. The standard connection pool has the ability to specify timeouts. If your custom one has that ability that might be the way to go. Cheers, Tony
gary.sole nk4um User Posts: 74	<div>Note: We are seeing these long running activities on the Active Requests page. We have also seen that when we try to manually kill the process that does not always work.</div> 2009-09-23T21:21:17.000ZSeptember 23, 2009 21:21Long running processes Note: We are seeing these long running activities on the Active Requests page. We have also seen that when we try to manually kill the process that does not always work.
gary.sole nk4um User Posts: 74	<div>We currently have our Deadlock Period set at 90000. 90 seconds. <br/>Our expectation is that NK would kill long running processes. However, we are having an issue where we are having some sort of database slow down (possibly being caused by locks) but the threads do not die. Instead, some are running for as much as 5+ minutes. We then are getting multiple of these requests happening and NK eventually hangs when it runs out of threads - thus impacting our client applications.<br/>We are using Java based accessors and connecting to the DB through our own JDBC and pool based libraries. <br/><br/>Does this mean that NK is unable to kill the thread after 90 seconds?</div> 2009-09-23T21:20:09.000ZSeptember 23, 2009 21:20Killing long running processes We currently have our Deadlock Period set at 90000. 90 seconds. Our expectation is that NK would kill long running processes. However, we are having an issue where we are having some sort of database slow down (possibly being caused by locks) but the threads do not die. Instead, some are running for as much as 5+ minutes. We then are getting multiple of these requests happening and NK eventually hangs when it runs out of threads - thus impacting our client applications. We are using Java based accessors and connecting to the DB through our own JDBC and pool based libraries. Does this mean that NK is unable to kill the thread after 90 seconds?

nk4um

Killing long running processes