Return-Path: X-Original-To: apmail-manifoldcf-dev-archive@www.apache.org Delivered-To: apmail-manifoldcf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7F1D217DDD for ; Wed, 4 Feb 2015 17:13:39 +0000 (UTC) Received: (qmail 43214 invoked by uid 500); 4 Feb 2015 17:13:35 -0000 Delivered-To: apmail-manifoldcf-dev-archive@manifoldcf.apache.org Received: (qmail 43167 invoked by uid 500); 4 Feb 2015 17:13:35 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 43156 invoked by uid 99); 4 Feb 2015 17:13:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2015 17:13:35 +0000 Date: Wed, 4 Feb 2015 17:13:35 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CONNECTORS-1156) Can't shut down agents service when automatic ANALYZE TABLE is happening MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CONNECTORS-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-1156: ------------------------------------ Attachment: sqlstate.patch Here is a patch which should allow us to determine what the PostgreSQL driver does when interrupted. > Can't shut down agents service when automatic ANALYZE TABLE is happening > ------------------------------------------------------------------------ > > Key: CONNECTORS-1156 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1156 > Project: ManifoldCF > Issue Type: Bug > Components: Framework agents process > Affects Versions: ManifoldCF 1.8, ManifoldCF 2.0 > Reporter: Karl Wright > Assignee: Karl Wright > Fix For: ManifoldCF 1.9, ManifoldCF 2.1 > > Attachments: sqlstate.patch > > > This was detected on MCF 1.8. > The thread blocking shutdown had the following trace: > {code} > "Startup thread" daemon prio=10 tid=0x00007fe73012f000 nid=0x340b in Object.wait() [0x00007fe71f7f6000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at java.lang.Thread.join(Thread.java:1281) > - locked <0x00000000e851a0b8> (a org.apache.manifoldcf.core.database.Database$ExecuteQueryThread) > at java.lang.Thread.join(Thread.java:1355) > at org.apache.manifoldcf.core.database.Database$ExecuteQueryThread.finishUp(Database.java:694) > at org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:728) > at org.apache.manifoldcf.core.database.Database.executeUncachedQuery(Database.java:790) > at org.apache.manifoldcf.core.database.Database$QueryCacheExecutor.create(Database.java:1444) > at org.apache.manifoldcf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:146) > at org.apache.manifoldcf.core.database.Database.executeQuery(Database.java:191) > at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.performModification(DBInterfacePostgreSQL.java:656) > at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.analyzeTableInternal(DBInterfacePostgreSQL.java:1431) > at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.noteModificationsNoTransactions(DBInterfacePostgreSQL.java:1576) > at org.apache.manifoldcf.core.database.Database.playbackModifications(Database.java:429) > at org.apache.manifoldcf.core.database.Database.endTransaction(Database.java:414) > at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.endTransaction(DBInterfacePostgreSQL.java:1231) > at org.apache.manifoldcf.crawler.jobs.JobManager.resetStartupJob(JobManager.java:7575) > at org.apache.manifoldcf.crawler.system.StartupThread.run(StartupThread.java:238) > {code} > This was after many minutes of waiting for the shutdown to take place, so clearly it's looping in the sense that it keeps starting an ANALYZE, gets interrupted, and retries indefinitely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)