From dev-return-19332-archive-asf-public=cust-asf.ponee.io@manifoldcf.apache.org Tue Mar 12 06:13:16 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 05325180600 for ; Tue, 12 Mar 2019 07:13:15 +0100 (CET) Received: (qmail 9118 invoked by uid 500); 12 Mar 2019 06:13:15 -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 9106 invoked by uid 99); 12 Mar 2019 06:13:14 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Mar 2019 06:13:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D12CAC0576 for ; Tue, 12 Mar 2019 06:13:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.8 X-Spam-Level: * X-Spam-Status: No, score=1.8 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=linguamatics.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id UsHiEGk_shjv for ; Tue, 12 Mar 2019 06:13:12 +0000 (UTC) Received: from mail.linguamatics.com (mail.linguamatics.com [188.39.80.203]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id DE4CC60FB9 for ; Tue, 12 Mar 2019 06:13:11 +0000 (UTC) Received: from mail.linguamatics.com (localhost [127.0.0.1]) by mail.linguamatics.com (Postfix) with ESMTP id 330EB84B280 for ; Tue, 12 Mar 2019 06:13:05 +0000 (UTC) Received: by mail.linguamatics.com (Postfix, from userid 1001) id 1555B84B283; Tue, 12 Mar 2019 06:13:05 +0000 (UTC) Received: from hermes.linguamatics.com (unknown [10.252.6.15]) by mail.linguamatics.com (Postfix) with ESMTP id 9889F84B280 for ; Tue, 12 Mar 2019 06:13:04 +0000 (UTC) Received: from [10.252.5.238] (vpn238.cam.linguamatics.com [10.252.5.238]) by hermes.linguamatics.com (Postfix) with ESMTPSA id 4374086ED0A; Tue, 12 Mar 2019 06:13:04 +0000 (UTC) To: dev@manifoldcf.apache.org From: James Thomas Subject: How to deal with MCF server failing to start when connector class not found? Message-ID: <234fc5ae-cf05-9cc7-4eaf-e196235afa5e@linguamatics.com> Date: Tue, 12 Mar 2019 06:13:03 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------BB6F6B0F303F56705312B0DB" Content-Language: en-GB X-Virus-Scanned: ClamAV using ClamSMTP --------------BB6F6B0F303F56705312B0DB Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, We've been experimenting with a transformation connector and have decided not to use it. With its code removed from the jar that we deploy into MCF I find that my test MCF server will not start because there is some memory of the connector (MetadataToXMLTransformer) in the database. The server shows this trace in the console at startup: --- Successfully unregistered all domains Successfully unregistered all output connectors org.apache.manifoldcf.core.interfaces.ManifoldCFException: No connector class '...MetadataToXMLTransformer' was found.         at org.apache.manifoldcf.core.interfaces.ConnectorFactory.getThisConnectorNoCheck(ConnectorFactory.java:120)         at org.apache.manifoldcf.core.interfaces.ConnectorFactory.deinstallThis(ConnectorFactory.java:58)         at org.apache.manifoldcf.agents.interfaces.TransformationConnectorFactory.deinstall(TransformationConnectorFactory.java:79)         at org.apache.manifoldcf.agents.transformationconnmgr.TransformationConnectorManager.unregisterConnector(TransformationConnectorManager.java:210)         at org.apache.manifoldcf.crawler.system.ManifoldCF.unregisterAllConnectors(ManifoldCF.java:370)         at org.apache.manifoldcf.crawler.system.ManifoldCF.reregisterAllConnectors(ManifoldCF.java:157)         at org.apache.manifoldcf.jettyrunner.ManifoldCFJettyRunner.main(ManifoldCFJettyRunner.java:239) ---- I tried the following: * Removing the relevant entry in connectors.xml * Deleting the instance of the connector that was visible via the MCF web view * Removing references to MetadataToXMLTransformer in all of the jobs visible in the MCF web view * Downloading JSON of all of my jobs and looking for references to the connector (there are none) * Looking in https://manifoldcf.apache.org/release/release-2.12/en_US/how-to-build-and-deploy.html#file+properties for useful config I am guessing that there's some historical data from jobs that were run using the transformation connector. In my test environment I can simply delete the database and the problem goes away, but in production environment this seems like it could present a problem if we ever want to change a connector class after it's been used. What's the recommended way of dealing with this situation? Cheers, James -- James Thomas | Head of Testing | Linguamatics, an IQVIA company 324 Cambridge Science Park, Milton Road, CB4 0WG Cambridge, UK Telephone number: +44 (0)1223 651910 web: www.linguamatics.com Twitter |Linkedin |Facebook |YouTube ------------------------------------------------------------------- Winner of the Frost & Sullivan Market Leadership Award 2016, 2017 and 2018 ------------------------------------------------------------------- Linguamatics will process your personal data fairly and lawfully in accordance with professional standards and the Data Protection Act 2018, General Data Protection Regulation (EU) 2016/679 (as applicable) and any other applicable laws relating to the protection of personal data and the privacy of individuals. Further information is available in our privacy policy: https://www.linguamatics.com/privacy. This email has been sent for the sole use of the intended recipient(s). The contents of this email and any attachments are very likely to contain confidential or proprietary information. If you received this email in error please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. Linguamatics Limited is a company incorporated in England and Wales with registered number: 4248841 --------------BB6F6B0F303F56705312B0DB--