On Tue, 2003-10-14 at 20:07, Renner Klaus wrote: > We have a big deadlock-problem, > > Kernel 7.4.3 Build 017-123-039-277 > Runtime Environment : X64/SUN 7.4.3 Build 017-123-039-277 > > A java-program fills our sapdb with data running on localhost every 5 > minutes. This is done in one transaction. The required time normally varies > from 20 seconds to some minutes. > So we stored about 6 Gigabytes in a few tables, all belonging to the same > database user account. > > To read this stuff we are using a java-servlet with jdbc on tomcat on a > remote computer. This program uses only select, no insert or update . > When using the query-program in the timespan while the data-feed program is > inserting data, then the deadlock occures. > Closing the webinterface has no effect, tomcat still holds the connections. > Stopping the application in tomcat causes tomcat to release connections > after 20 minutes. So the concurrent tasks should be finished, but after > closed connections the feed-program is still waiting further 10 minutes > before finishing with some (ca 1000) insert-statements.
This looks like a pretty standard OLTP workload. Are you sure that you close all the result sets and all the connections correctly ? Leaving results sets and connections open will obviously result in the behaviour you're seeing. -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
