if that's the case.\n>\n> Best regards,\n>\n> Pablo\n> -----BEGIN PGP SIGNATURE-----\n> Version: GnuPG v1.4.10 (GNU/Linux)\n>\n> iQIcBAEBCAAGBQJLJXnzAAoJEMJ09r9KJ69qOEcP/1DBsNmExuDlbAS/+ssl40xg\n> oOtHfBFNUTk+akfNgtYMsXq593CP3aZyBmBof+hIAyrJBXegkd/BdEObhkTMtMzl\n> mElm4iHPNUTAb+90Mp/dSAo2RmZFeY7rLFKhdwupJJjhVrA5yeEBVQeKMISFolzQ\n> uZJvlF8U1RhKAKSrkBYrjNmskEsGzP/7Tlqs9pn0xF8+BHsSdcWlfjEP4zc/SwM/\n> mKTp1iZH/iFr4+n9eqKORJiTIKwsnPv3VzAYmDUaOqbIv+p37GUxdQ14+Xdrm3/Y\n> 1vuEaMzODEa88F1RUZh45kVFFOEZw30pu/74Uct4cRh8k4z7Q75HUjT2DrA0MSFk\n> EhzHx3rp8eZS1zMg8QWiOX9+t6vuybLLuZPMittwDFgJ1fjShC9Pn2rWCMb+yvuN\n> elgt/Sprwpodt4Vdj9KQko4oyvizYAbz4jaziHLDzUV/rM5G+z+igWcpGbVwZjRg\n> r7ShBu3GGo5GbpA/QRLf8J1WW+im6ajypW+7m8to982thDJDVsHUv5KEwrZaxIPm\n> bRiIRxoffTrE9ugYed42f3xbUTRpfDsFTRXarrrS5bvcEqX9n3U3sZDLj7Ia1I97\n> 4UZceECNUagPqMjqZtwTM5Biixen6e1O6G3/eS5UI2cf2inrwKNy5GwuhB3N5IYe\n> yKkgfWBELeYaS8kBIOSo\n> =5qWr\n> -----END PGP SIGNATURE-----\n> \n\n\nFrom uima-user-returnkavery@example.com Mon Dec 14 02:34:01 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 99933 invoked from network); 14 Dec 2009 02:34:00 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 14 Dec 2009 02:34:00 -0000\nReceived: (qmail 58390 invoked by uid 500); 14 Dec 2009 02:34:00 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 58251 invoked by uid 500); 14 Dec 2009 02:34:00 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 58241 invoked by uid 99); 14 Dec 2009 02:34:00 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 02:34:00 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_HELO_PASS,SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO lo.gmane.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 02:33:50 +0000\nReceived: from list by lo.gmane.org with local (Exim 4.50)\n\tid 1NK0ka-0004pm-OT\n\tfor kavery@example.com; Mon, 14 Dec 2009 03:33:29 +0100\nReceived: from eth3395.vic.adsl.internode.on.net ([161.129.204.104])\n by main.gmane.org with esmtp (Gmexim 0.1 (Debian))\n id 1AlnuQ-0007hv-00\n for ; Mon, 14 Dec 2009 03:33:28 +0100\nReceived: from hansen.candrawinata by eth3395.vic.adsl.internode.on.net with local (Gmexim 0.1 (Debian))\n id 1AlnuQ-0007hv-00\n for ; Mon, 14 Dec 2009 03:33:28 +0100\nX-Injected-Via-Gmane: http://gmane.org/\nTo: kavery@example.com\nFrom: Hansen Candrawinata \nSubject: Re: Exception thrown when deploying CAS Processors in managed mode\nDate: Mon, 14 Dec 2009 02:32:59 +0000 (UTC)\nLines: 76\nMessage-ID: \nReferences: \nMime-Version: 1.0\nContent-Type: text/plain; charset=us-ascii\nContent-Transfer-Encoding: 7bit\nX-Complaints-To: kavery@example.com\nX-Gmane-NNTP-Posting-Host: sea.gmane.org\nUser-Agent: Loom/3.14 (http://gmane.org/)\nX-Loom-IP: 161.129.204.104 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:161.129.204.104) Gecko/20091102 Firefox/3.5.5)\nSender: news \nX-Virus-Checked: Checked by ClamAV on apache.org\n\nJaroslaw Cwiklik writes:\n> The CPM stopping is a consequence of an error while serializing a message\n> into XCAS. Not sure exactly what causes that. As I understand it, your\n> managed CP deployment failed but than process() method is called and an\n> exception from a XCAS serializer is thrown. Can you describe the sequence\n> that leads to this problem.\n\nHi Jaroslaw,\n\nSorry for the late reply - I got caught up with some other things at work in \nthe past few days and was not able to experiment more with UIMA until recently.\n\nYes, I am still not able to deploy my CAS processors in managed mode. I still\nget the same error, that is, a failure in converting CAS object to CAS data\nwhich then lead to the CPM and Vinci service stopping. The log messages and \nthe stack trace of the exceptions were in my previous posts.\n\nI will try to describe what my application is doing and how I ran it in managed\nmode. Basically, the application is reading files the off disk and pass them \nto some text extractor tools to extract the text and write it to the disk. \nThe application consists of:\n * A collection reader that reads files off the disk.\n * An aggregate Analysis Engine with two components/annotators - each component\nis a text extractor tool.\n * A user-defined flow that controls the data flow between the components in\nthe aggregate analysis engine.\n * A main Java class that reads the XML CPE descriptor, creates a CPE object\nand then initiates the processing (\"cpe.process()\").\n\nAs I explained before, if I configure my CPE descriptor to deploy the CAS\nprocessors in integrated mode, everything works fine. The collection reader\ngets called to read the contents of files from the disk (i.e. getNext(CAS aCas)\nis called), the annotators in the analysis engine get called to process the \nJCas object that contains the contents of the files read in by the collection \nreader (i.e. process(JCas aJCas) is called).\n\nI was interested to deploy the CAS processors in managed mode, so:\n * I modified the XML CPE descriptor accordingly such that: deployment=\"local\"\nand the descriptor element is pointing to a Vinci service deployment descriptor.\n * I also added the runInSeparateProcess element as mentioned in the \ndocumentation.\n * However, when I ran the application, my CAS processors didn't get kavery@example.com. Instead, the CPM seemed to be caught in the loop because the service port\nwas not available.\n * Then, I did a little debugging and found that the vinci service\n(VinciAnalysisEngineService_impl) failed to be started[*].\n * I figured that this was due to misconfiguration in the classpath in the\nrunInSeparateProcess element in my CPE descriptor. I tried to fix it, but \nfailed.\n * I tried to run the VNS and my vinci service from the command line (using\n\"startVNS.bat\" and \"startVinciService.bat\" respectively) and they seemed to run\njust fine.\n * I figured that I would just run my application (still with the CPE\ndescriptor configured to deploy the CAS processors in managed mode), let it loop\nuntil it finds a service port, and then run my vinci service from the command\nline (with \"startVinciService.bat\") to connect to the internal VNS started by my\napplication.\n * This is where I encounter the error of failing to convert CAS object to CAS\ndata which then lead to the CPM and Vinci service stopping.\n \nHope this makes sense and helps in debugging the problems. Let me know if you\nneed more information. FYI, my previous posts contain some other information\nthat may be useful (the log messages and stack trace of the exceptions thrown).\n\nAlso, are there any examples of applications/code that deploy CAS processors in\nmanaged mode that I can use as a reference?\n\nThanks,\nHansen\n\n[*] An exception should have been thrown in this case in my opinion, but \ninstead UIMA seems to silently ignore this. \nSee org.apache.uima.collection.impl.cpm.container.deployer.vinci\n.VinciCasProcessorDeployer\nline 551, where the Process object returned should have been used to check the\nstatus of the spawned process.\n\n\nFrom uima-user-returnkavery@example.com Mon Dec 14 14:30:17 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 86561 invoked from network); 14 Dec 2009 14:30:16 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 14 Dec 2009 14:30:16 -0000\nReceived: (qmail 29362 invoked by uid 500); 14 Dec 2009 14:30:16 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 29304 invoked by uid 500); 14 Dec 2009 14:30:15 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 29294 invoked by uid 99); 14 Dec 2009 14:30:14 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 14:30:14 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO ns.neofonie.de) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 14:30:04 +0000\nReceived: from [161.129.204.104] (helo=perseus.exchange.neofonie.de)\n\tby ns.neofonie.de with esmtp (Exim 4.63)\n\t(envelope-from )\n\tid 1NKBvk-0007o5-6v\n\tfor kavery@example.com; Mon, 14 Dec 2009 15:29:44 +0100\nReceived: from [161.129.204.104] ([161.129.204.104]) by perseus.exchange.neofonie.de with Microsoft SMTPSVC(314)481-9074);\n\t Mon, 14 Dec 2009 15:29:36 +0100\nMessage-ID: \nDate: Mon, 14 Dec 2009 15:29:43 +0100\nFrom: =?UTF-8?B?Q2hyaXN0b3BoIELDvHNjaGVy?=\n \nUser-Agent: Thunderbird 161.129.204.104 (X11/20080421)\nMIME-Version: 1.0\nTo: kavery@example.com\nSubject: Re: Problems with \"deserializeCasFromXmi\" after using C++ AS Annotator\nReferences: \t \t \nIn-Reply-To: \nContent-Type: multipart/mixed;\n boundary=\"------------060500070400020708050900\"\nX-OriginalArrivalTime: 14 Dec 2009 14:29:36.0656 (UTC) FILETIME=[DCB46100:01CA7CC9]\nX-Virus-Checked: Checked by ClamAV on apache.org\n\n--------------060500070400020708050900\nContent-Type: text/plain; charset=UTF-8; format=flowed\nContent-Transfer-Encoding: 7bit\n\nHi,\n\nI did some further testing and the problem seems to happen when the FS is not\ndeclared in the remote C++ TAE but declared and set in an AE in the (lokal) main\n application (in out case a CPE running various Java AEs).\nIn my unit test I create a \"DummyAE\" descriptor basically doing nothing but\ndeclaring a \"DocumentData\" type with the URL Feature. I also created a\ncustomResourceSpecifier pointing to the DAVEDETECTORQ on the remote system. My\ntest looks like this:\n\n\npublic class RemoteCTaeTest {\n\n private AnalysisEngine daveAe;\n private AnalysisEngine myAe;\n\n /**\n * @throws java.lang.Exception\n */\n @Before\n public void setUp() throws Exception {\n URL daveResource =\nRemoteCTaeTest.class.getClassLoader().getResource(\"DaveResource.xml\");\n URL myResource =\nRemoteCTaeTest.class.getClassLoader().getResource(\"DummyAE.xml\");\n ResourceSpecifier res =\nUIMAFramework.getXMLParser().parseResourceSpecifier(\n new XMLInputSource(daveResource));\n AnalysisEngineDescription aeDesc =\nUIMAFramework.getXMLParser().parseAnalysisEngineDescription(\n new XMLInputSource(myResource));\n this.daveAe = UIMAFramework.produceAnalysisEngine(res);\n this.myAe = UIMAFramework.produceAnalysisEngine(aeDesc);\n }\n\n /**\n * @throws Exception\n */\n @Test\n public void testSendCAS() throws Exception {\n CAS cas = CasCreationUtils.createCas(Arrays.asList(new\nAnalysisEngineMetaData[] {\n this.daveAe.getAnalysisEngineMetaData(),\nthis.myAe.getAnalysisEngineMetaData() }));\n JCas cas2 = cas.getJCas();\n DocumentData metadata = new DocumentData(cas2);\n\nmetadata.setDocumentURL(\"http://www.gesundheitsnachrichten.net/live/navigation/live.php?navigation_id=11&_psmand=1\");\n String text = \"This is a Dave Test.\";\n cas2.setDocumentText(text);\n cas2.addFsToIndexes(metadata);\n this.daveAe.process(cas2);\nSystem.out.print(cas2.getJFSIndexRepository().getAllIndexedFS(DocumentData.type).next());\n }\n}\n\nThe test fails when I used the DaveDetector descriptor delivered with\n\"2.2.2-incubating\". When I add DocumentData type to the DaveDetector descriptor,\nthe test succeeds and the URL is returned correctly by the remote AE:\n\n(../examples/descriptors/DaveDetector.xml)\n\n \n \n org.apache.uima.examples.David \n uima.tcas.Annotation \n \n \n \n \n de.neofonie.DocumentData \n Metadata for a document \n uima.cas.TOP \n \n \n documentURL \n The original URL of the document \n uima.cas.String \n \n \n \n \n \n\nI will attach both descriptors used in the test. The implementation of the\nDummyAE is completely empty, since it is not called in the test.\n From my UIMA understanding so far a remote AS service shouldn't have to declare\nor import all types and type systems by potential AE clients connecting to it,\nor am I wrong in this regard?\nI attached the descriptors used in the Junit test above. Hope this helps. I will\ncontinue to try to reproduce the problem using CVD.\n\nChristoph\n\n\nEddie Epstein schrieb:\n> Hi,\n> \n> Well, I tried another, simpler scenario based on your description:\n> \n> Just add the following to DaveDetector.xml:\n> \n> uima.tcas.Chris \n> uima.tcas.Annotation \n> \n> \t\n> \t documentURL \n> \t uima.cas.String \n> \t \n> \n> \n> \n> Create the following CasXmi file:\n> \n> xmlns:tcas=\"http:///uima/tcas.ecore\"\n> xmlns:xmi=\"http://www.omg.org/XMI\" xmi:version=\"2.0\">\n> \n> mimeType=\"text\" sofaString=\"This is a text document with Dave for\n> analysis\"/>\n> \n> documentURL=\"http://www.gesundheitsnachrichten.net/live/navigation/live.php?navigation_id=11&_psmand=1\"/>\n> \n> \n> Launch the unaltered DaveDetector as a service, have CVD connect to it\n> via JMS service descriptor, use File->Read Xmi Cas File to load the test Cas,\n> use Run->Run DaveDetector On CAS to call the remote service, and, finally\n> expand the annotation index to see the results. No problems.\n> \n> This was using something close to uima-2.3.0.\n> \n> Eddie\n> \n> \n> \n> On Fri, Dec 11, 2009 at 9:04 AM, Christoph Buescher\n> wrote:\n>> Hi Eddie,\n>>\n>> unfortunately I'm out of the office today so I can only send you the unit\n>> test reproducing the problem on monday. But our scenario is more or less the\n>> following:\n>>\n>> - A CPE running several Java AEs first, then send the CAS to a remote AS\n>> Service which is a C++ AE\n>> - the collection reader adds a FS with document metadata (including the\n>> String Feature \"URL\") to the CAS. This FS directly extends the Top-Type, not\n>> Annotation.\n>> - I used the unaltered DaveDetector to replace our own C++ AE to reproduce\n>> the problem\n>>\n>> For the unit test I wrote a \"No-OP\" Java AE which uses a Typesystem only\n>> including this \"DocumentData\" FS with only this one String Feature. I used a\n>> Custom Resource Specifier like in the AS Documentation to reference the\n>> DaveDetector on a remote machine. I then create a CAS using the\n>> CasCreationUtil which in turn uses the \"No-OP\" AE descriptor and the\n>> DaveDetector-Resource Specifier. I then add the problematic Feature in\n>> question and call \"process\" on the remote Dave-AE. Then the exception I\n>> mentioned in my earlier mail happens.\n>>\n>> I will send you the test code on monday and also try to use CVD to reproduce\n>> the problem.\n>>\n>> Thanks,\n>> Christoph\n\n--------------060500070400020708050900\nContent-Type: text/xml;\n name=\"DaveResource.xml\"\nContent-Transfer-Encoding: base64\nContent-Disposition: inline;\n filename=\"DaveResource.xml\"\n\nPD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiID8+CjxjdXN0b21SZXNvdXJj\nZVNwZWNpZmllciB4bWxucz0iaHR0cDovL3VpbWEuYXBhY2hlLm9yZy9yZXNvdXJjZVNwZWNp\nZmllciI+CiAgPHJlc291cmNlQ2xhc3NOYW1lPm9yZy5hcGFjaGUudWltYS5hYWUuam1zX2Fk\nYXB0ZXIuSm1zQW5hbHlzaXNFbmdpbmVTZXJ2aWNlQWRhcHRlcjwvcmVzb3VyY2VDbGFzc05h\nbWU+CiAgPHBhcmFtZXRlcnM+CiAgICA8cGFyYW1ldGVyIG5hbWU9ImJyb2tlclVSTCIgdmFs\ndWU9InRjcDovL215SG9zdDo2MTYxNiIvPgogICAgPHBhcmFtZXRlciBuYW1lPSJlbmRwb2lu\ndCIgdmFsdWU9IkRBVkVERVRFQ1RPUlEiLz4KICA8L3BhcmFtZXRlcnM+IAo8L2N1c3RvbVJl\nc291cmNlU3BlY2lmaWVyPg==\n--------------060500070400020708050900\nContent-Type: text/xml;\n name=\"DummyAE.xml\"\nContent-Transfer-Encoding: 7bit\nContent-Disposition: inline;\n filename=\"DummyAE.xml\"\n\n\n\n\t\n\t\torg.apache.uima.java\n\t \n\ttrue \n\t\n\t\tDummyAE\n\t \n\t\n\t\tDummyAE \n\t\tFor testing purposes only. \n\t\t1.0 \n\t\t\n\t\t \n\t\t\n\t\t\t\n\t\t\t\t\n\t\t\t\t\tde.neofonie.DocumentData \n\t\t\t\t\tMetadata for a document \n\t\t\t\t\tuima.cas.TOP \n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tdocumentURL \n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tThe original URL of the document\n\t\t\t\t\t\t\t \n\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tuima.cas.String\n\t\t\t\t\t\t\t \n\t\t\t\t\t\t \n\t\t\t\t\t \n\t\t\t\t \n\t\t\t \n\t\t \n\t\t\n\t\t\t\n\t\t\t\t \n\t\t \n\t\t\n\t\t\tfalse \n\t\t\ttrue \n\t\t\tfalse \n\t\t \n\t \n\t\nDelivered-To: kavery@example.com\nReceived: (qmail 91901 invoked from network); 14 Dec 2009 14:40:20 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 14 Dec 2009 14:40:20 -0000\nReceived: (qmail 41868 invoked by uid 500); 14 Dec 2009 14:40:20 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 41834 invoked by uid 500); 14 Dec 2009 14:40:20 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 41824 invoked by uid 99); 14 Dec 2009 14:40:20 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 14:40:20 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO mail-ew0-f220.google.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 14:40:12 +0000\nReceived: by ewy20 with SMTP id 20so498775ewy.20\n for ; Mon, 14 Dec 2009 06:39:52 -0800 (PST)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:in-reply-to:references\n :date:message-id:subject:from:to:content-type\n :content-transfer-encoding;\n bh=T8a92iPMYPa8nEKVgO5N9krordu7NpoXT4t0fQBEpXI=;\n b=anEqVdAx3aIoCPnMi/hzV0RIp5IIYLMkFzqZW/YmdiqF+lADf8IbMstj7yOSTsbx2o\n TG6GlNYCDK8Ub7fouD/lzBF7B4lPz972fh+ofkiLO/wr0ruraMs5qtex/z5seUU75s3v\n rmNPrJPajEx6m7Wc3SudR1VL5NZpNMBCPiFqM=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:in-reply-to:references:date:message-id:subject:from:to\n :content-type:content-transfer-encoding;\n b=P/3l3QgU7A9OH6WHks7HavK5FAKkRS0n7o4U1GY771u49N9ngHNVbechXpAOX9P5xL\n D8FIeUX9pk6OsixgvuhcVTejHzPni4KpWuOJIN+JZ1eHkMT3KvUjCgo1AcUVc/++jaMq\n G+sdCf9CSUL4cBw+7cqQW07c2NlWs/A89aYcs=\nMIME-Version: 1.0\nReceived: by 161.129.204.104 with SMTP id d52mr2045597wef.51.1260801589898; Mon, \n\t14 Dec 2009 06:39:49 -0800 (PST)\nIn-Reply-To: \nReferences: \n\t \n\t \n\t \n\t \nDate: Mon, 14 Dec 2009 09:39:49 -0500\nMessage-ID: \nSubject: Re: Problems with \"deserializeCasFromXmi\" after using C++ AS \n\tAnnotator\nFrom: Eddie Epstein \nTo: kavery@example.com\nContent-Type: text/plain; charset=ISO-8859-1\nContent-Transfer-Encoding: quoted-printable\nX-Virus-Checked: Checked by ClamAV on apache.org\n\nOn Mon, Dec 14, 2009 at 9:29 AM, Christoph B=FCscher\n wrote:\n> Hi,\n>\n> I did some further testing and the problem seems to happen when the FS is\n> not\n> declared in the remote C++ TAE but declared and set in an AE in the (loka=\nl)\n> main\n> =A0application (in out case a CPE running various Java AEs).\n\nAh, must have to do with C++ service handing of \"out-of-type-system\" data.\n\n> =A0From my UIMA understanding so far a remote AS service shouldn't have t=\no\n> declare\n> or import all types and type systems by potential AE clients connecting t=\no\n> it,\n> or am I wrong in this regard?\n> I attached the descriptors used in the Junit test above. Hope this helps.=\n I\n> will\n> continue to try to reproduce the problem using CVD.\n\nYour understanding is correct. We should have enough to go on for now.\nWonder if this is a problem for remote Java annotators too :)\n\nThanks for debugging!\nEddie\n\nFrom uima-user-returnkavery@example.com Mon Dec 14 15:28:23 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 14679 invoked from network); 14 Dec 2009 15:28:23 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 14 Dec 2009 15:28:23 -0000\nReceived: (qmail 38943 invoked by uid 500); 14 Dec 2009 15:28:22 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 38880 invoked by uid 500); 14 Dec 2009 15:28:22 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 38870 invoked by uid 99); 14 Dec 2009 15:28:22 -0000\nReceived: from athena.apache.org (HELO athena.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 15:28:22 +0000\nX-ASF-Spam-Status: No, hits=-2.6 required=5.0\n\ttests=BAYES_00\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO ns.neofonie.de) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 15:28:20 +0000\nReceived: from [161.129.204.104] (helo=perseus.exchange.neofonie.de)\n\tby ns.neofonie.de with esmtp (Exim 4.63)\n\t(envelope-from )\n\tid 1NKCq7-0006Dz-9f\n\tfor kavery@example.com; Mon, 14 Dec 2009 16:27:59 +0100\nReceived: from [161.129.204.104] ([161.129.204.104]) by perseus.exchange.neofonie.de with Microsoft SMTPSVC(314)481-9074);\n\t Mon, 14 Dec 2009 16:27:59 +0100\nMessage-ID: \nDate: Mon, 14 Dec 2009 16:27:58 +0100\nFrom: =?UTF-8?B?Q2hyaXN0b3BoIELDvHNjaGVy?=\n \nUser-Agent: Thunderbird 161.129.204.104 (X11/20080421)\nMIME-Version: 1.0\nTo: kavery@example.com\nSubject: Re: Problems with \"deserializeCasFromXmi\" after using C++ AS \tAnnotator\nReferences: \t \t \t \t \nIn-Reply-To: \nContent-Type: text/plain; charset=UTF-8; format=flowed\nContent-Transfer-Encoding: 8bit\nX-OriginalArrivalTime: 14 Dec 2009 15:27:59.0010 (UTC) FILETIME=[04453020:01CA7CD2]\n\nHi Eddie,\n\nI just checked the same test using the Java RoomNumberAnnotator from the UIMA AS \nexamples. This specific problem doesn't seem to happen there. Hope this helps.\nChristoph\n\nEddie Epstein schrieb:\n> On Mon, Dec 14, 2009 at 9:29 AM, Christoph Büscher\n> Wonder if this is a problem for remote Java annotators too :)\n> \n> Thanks for debugging!\n> Eddie\n\nFrom uima-user-returnkavery@example.com Tue Dec 15 21:15:47 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 28970 invoked from network); 15 Dec 2009 21:15:46 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 15 Dec 2009 21:15:46 -0000\nReceived: (qmail 2600 invoked by uid 500); 15 Dec 2009 21:15:46 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 2544 invoked by uid 500); 15 Dec 2009 21:15:45 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 2534 invoked by uid 99); 15 Dec 2009 21:15:45 -0000\nReceived: from athena.apache.org (HELO athena.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 21:15:45 +0000\nX-ASF-Spam-Status: No, hits=-2.6 required=5.0\n\ttests=BAYES_00\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO mail-ew0-f220.google.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 21:15:43 +0000\nReceived: by ewy20 with SMTP id 20so337123ewy.20\n for ; Tue, 15 Dec 2009 13:15:21 -0800 (PST)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:in-reply-to:references\n :date:message-id:subject:from:to:content-type\n :content-transfer-encoding;\n bh=Sn5ZbIXG2OA/JCJzWBGCkFW3QsmQBzWn6Opnya7IZjM=;\n b=wgDFXTNMRx26yDLZhmlWAT4ttMD7OgnpTGlOT1+hc4nQ/hKmpZ4eLCHkWRkxTDx+Jc\n odbMUdTQR9cmmOqY91d1VYUqZLhD6Uk0sh8OdSLkHcg5q6I3T0NVKvC3J6jVkRQZsKzo\n pFB5YnIoVxR32WORD6LAaIjuGQx68T4lJ9wVE=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:in-reply-to:references:date:message-id:subject:from:to\n :content-type:content-transfer-encoding;\n b=MR2kMXis0fO46jKtmp05rBk6ZrGQ14Hyo4xubVkrBjeJ9MyaSkzKm+0VD8qa/xgn4S\n CMemPuRae3BZF44ggIEvdD4PZtQ0MuDG0+NlEaIumhGSauYVOD5OpWaJ/3TSo+qB3YjE\n DVVLvoWIEt60+VeGAznAYZT9UefgOX0efuNg4=\nMIME-Version: 1.0\nReceived: by 161.129.204.104 with SMTP id w45mr34943wee.82.1260911721657; Tue, \n\t15 Dec 2009 13:15:21 -0800 (PST)\nIn-Reply-To: \nReferences: \n\t \n\t \n\t \n\t \n\t \n\t \nDate: Tue, 15 Dec 2009 16:15:21 -0500\nMessage-ID: \nSubject: Re: Problems with \"deserializeCasFromXmi\" after using C++ AS \n\tAnnotator\nFrom: Eddie Epstein \nTo: kavery@example.com\nContent-Type: text/plain; charset=ISO-8859-1\nContent-Transfer-Encoding: quoted-printable\n\nChristoph,\n\nIf you are building uimacpp, a fix for this problem has been\ncommited and the new code is in\n\nhttp://svn.apache.org/repos/asf/incubator/uima/uimacpp/branches/uimacpp-2.3=\n.0/src/cas/xmiwriter.cpp\n\nThanks again for the help,\nEddie\n\nOn Mon, Dec 14, 2009 at 10:27 AM, Christoph B=FCscher\n wrote:\n> Hi Eddie,\n>\n> I just checked the same test using the Java RoomNumberAnnotator from the\n> UIMA AS examples. This specific problem doesn't seem to happen there. Hop=\ne\n> this helps.\n> Christoph\n>\n> Eddie Epstein schrieb:\n>>\n>> On Mon, Dec 14, 2009 at 9:29 AM, Christoph B=FCscher\n>> Wonder if this is a problem for remote Java annotators too :)\n>>\n>> Thanks for debugging!\n>> Eddie\n>\n\nFrom uima-user-returnkavery@example.com Tue Dec 15 22:03:58 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 62233 invoked from network); 15 Dec 2009 22:03:57 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 15 Dec 2009 22:03:57 -0000\nReceived: (qmail 96689 invoked by uid 500); 15 Dec 2009 22:03:57 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 96649 invoked by uid 500); 15 Dec 2009 22:03:56 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nDelivered-To: moderator for kavery@example.com\nReceived: (qmail 73528 invoked by uid 99); 15 Dec 2009 20:59:06 -0000\nX-ASF-Spam-Status: No, hits=2.2 required=10.0\n\ttests=HTML_MESSAGE,SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: local policy)\nX-IronPort-AV: E=Sophos;i=\"4.47,402,1257145200\"; \n d=\"scan'208,217\";a=\"146256771\"\nFrom: Karin Verspoor \nContent-Type: multipart/alternative; boundary=Apple-Mail-49--864326504\nSubject: Resource override in aggregate AE\nDate: Tue, 15 Dec 2009 13:58:34 -0700\nMessage-Id: \nTo: kavery@example.com\nMime-Version: 1.0 (Apple Message framework v1076)\nX-Mailer: Apple Mail (2.1076)\nX-Virus-Checked: Checked by ClamAV on apache.org\n\n--Apple-Mail-49--864326504\nContent-Transfer-Encoding: 7bit\nContent-Type: text/plain;\n\tcharset=us-ascii;\n\tformat=flowed;\n\tdelsp=yes\n\nI'm trying to define an aggregate AE which overrides a resource \nbinding from one of the component AEs. The syntax of the aggregate \nappears to be correct and I get no error but the component AE is still \nrunning with the originally specified resource.\n\nHas anyone else run into problems with overriding of resource bindings?\n\nThanks,\nKarin\n\n-- \nKarin Verspoor, PhD\nResearch Assistant Professor\nCenter for Computational Pharmacology, University of Colorado Denver\nPO Box 6511, MS 8303, Aurora, CO 80045 USA\nkavery@example.com / tel: (314)481-9074 / campus: 4-3758\n\n\n\n\n\n\n--Apple-Mail-49--864326504--\n\nFrom uima-user-returnkavery@example.com Tue Dec 15 22:04:22 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 62605 invoked from network); 15 Dec 2009 22:04:22 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 15 Dec 2009 22:04:22 -0000\nReceived: (qmail 97192 invoked by uid 500); 15 Dec 2009 22:04:21 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 97121 invoked by uid 500); 15 Dec 2009 22:04:21 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nDelivered-To: moderator for kavery@example.com\nReceived: (qmail 62773 invoked by uid 99); 15 Dec 2009 20:52:33 -0000\nX-ASF-Spam-Status: No, hits=-2.2 required=5.0\n\ttests=BAYES_00,HTML_MESSAGE,NORMAL_HTTP_TO_IP,URI_HEX,WEIRD_PORT\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:date:message-id:subject\n :from:to:content-type;\n bh=iY9gyys3OSoCh2rm+VOsmn95U84eTj9AKS5RIBmN25Q=;\n b=g7Kmp/y31W7cvbnOswzQhbSC7kiamFONnvj9FaAe/PbCkQD9ZIvEb4V4gfzVnWWKPI\n 5JHZy0ERohS+7vVH6/sYc/6UIoSqEdHy62BBvF7VOLGkEb06zP8sJB1XLhh9KqZv5Kg0\n Fd5VBsEXyr38shawO/bY1FAGST/l7P8i4eiIQ=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:date:message-id:subject:from:to:content-type;\n b=PEFPdTtwoH+Xdf9dEEl5Cj+1PACuKWKmKPs7YKaZvVfN3jr5P9icbEhA8BrIRq6Jep\n lsajl9KSpO7fMBNKLkI+wVL2ViR6CHBHE9tWzJCcPt8eQg6ZQCmDdr0D84yy1SJdsgvX\n 8Oe2tDUHkG/NXmca8xzMdrpuw3yGAVZ4e4zPE=\nMIME-Version: 1.0\nDate: Tue, 15 Dec 2009 22:52:06 +0200\nMessage-ID: \nSubject: Error on getMeta call to remote service\nFrom: Prokopis Prokopidis \nTo: kavery@example.com\nContent-Type: multipart/alternative; boundary=0016e6d77df5212d68047aca90e2\n\n--0016e6d77df5212d68047aca90e2\nContent-Type: text/plain; charset=ISO-8859-1\n\nHi,\n\nI have the following timeout problem. I have deployed the\nRoomNumberAnnotator Analysis Engine example from the UIMA AS 2.2.2\ndistribution on a linux machine with java 1.6, and I am getting getMeta\nerrors while trying to call the service from another machine with the same\nconfiguration, with firewalls disabled on both machines. I am attaching the\nmessages I get on the client side and in the server's activemq log. If it's\nany help, when calling the service from the machine on which it has been\ndeployed, or when reversing the service-client roles between the two\nmachines, everything works as in the README file.\n\nThanks in advance for any hints,\n\nProkopis\n\n---------------------------------------------------------\n$ runRemoteAsyncAE.sh tcp://sikinos.mydomain.org:61616\nRoomNumberAnnotatorQueue -c\n/usr/local/apache-uima-as/examples/descriptors/collection_reader/FileSystemCollectionReader.xml\n\nGot MBeanServer Started\nError on getMeta call to remote service:\norg.apache.uima.aae.error.UimaASMetaRequestTimeout\n at\norg.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.notifyOnTimout(BaseUIMAAsynchronousEngineCommon_impl.java:1206)\n at\norg.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$ClientRequest$1.run(BaseUIMAAsynchronousEngineCommon_impl.java:1529)\n at java.util.TimerThread.mainLoop(Timer.java:534)\n at java.util.TimerThread.run(Timer.java:484)\nTerminating Client...\nException in thread \"main\"\norg.apache.uima.resource.ResourceInitializationException\n at\norg.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.initialize(BaseUIMAAsynchronousEngine_impl.java:439)\n at\norg.apache.uima.examples.as.RunRemoteAsyncAE.run(RunRemoteAsyncAE.java:241)\n at\norg.apache.uima.examples.as.RunRemoteAsyncAE.main(RunRemoteAsyncAE.java:297)\nCaused by: org.apache.uima.aae.error.UimaASMetaRequestTimeout\n ... 3 more\n\n\n------------------------------------------------------\n[localhost:61616] DEBUG WireFormatNegotiator - Sending:\nWireFormatInfo { version=2, properties={CacheSize=1024, CacheEnabled=true,\nSizePrefixDisabled=false, TcpNoDelayEnabled=true,\nMaxInactivityDuration=30000, TightEncodingEnabled=true,\nStackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}\n[161.129.204.104:32918] DEBUG WireFormatNegotiator - Received\nWireFormat: WireFormatInfo { version=2, properties={CacheSize=1024,\nCacheEnabled=true, SizePrefixDisabled=false, TcpNoDelayEnabled=true,\nMaxInactivityDuration=30000, TightEncodingEnabled=true,\nStackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}\n[161.129.204.104:32918] DEBUG WireFormatNegotiator - tcp:///\n161.129.204.104:32918 before negotiation: OpenWireFormat{version=2,\ncacheEnabled=false, stackTraceEnabled=false, tightEncodingEnabled=false,\nsizePrefixDisabled=false}\n[161.129.204.104:32918] DEBUG WireFormatNegotiator - tcp:///\n161.129.204.104:32918 after negotiation: OpenWireFormat{version=2,\ncacheEnabled=true, stackTraceEnabled=true, tightEncodingEnabled=true,\nsizePrefixDisabled=false}\n[161.129.204.104:32918] DEBUG TransportConnection - Setting up new\nconnection:\norg.apache.activemq.broker.jmx.ManagedTransportConnection@16b6c55\n[161.129.204.104:32918] DEBUG AbstractRegion - Adding consumer:\nID:anafi.mydomain.org-41122-1260898846989-1:0:-1:1\n[161.129.204.104:32918] DEBUG AbstractRegion - Adding\ndestination: temp-queue://ID:anafi.mydomain.org-41122-1260898846989-1:0:1\n[161.129.204.104:32918] DEBUG AbstractRegion - Adding consumer:\nID:anafi.mydomain.org-41122-1260898846989-1:0:2:1\n[161.129.204.104:32918] DEBUG AbstractRegion - Adding\ndestination: topic://ActiveMQ.Advisory.Consumer.Queue.ID:\nanafi.mydomain.org-41122-1260898846989-1:0:1\n[161.129.204.104:32918] DEBUG Transport - Transport failed:\njava.io.EOFException\njava.io.EOFException\n at java.io.DataInputStream.readInt(DataInputStream.java:392)\n at\norg.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)\n at\norg.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156)\n at\norg.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136)\n at java.lang.Thread.run(Thread.java:636)\n[161.129.204.104:32918] DEBUG TransportConnection - Stopping\nconnection: /161.129.204.104:32918\n[161.129.204.104:32918] DEBUG TransportConnection - Stopped\nconnection: /161.129.204.104:32918\n[161.129.204.104:32918] DEBUG TransportConnection - Cleaning up\nconnection resources.\n[161.129.204.104:32918] DEBUG AbstractRegion - Removing consumer:\nID:anafi.mydomain.org-41122-1260898846989-1:0:-1:1\n[161.129.204.104:32918] DEBUG AbstractRegion - Removing consumer:\nID:anafi.mydomain.org-41122-1260898846989-1:0:2:1\n[161.129.204.104:32918] DEBUG AbstractRegion - Removing\ndestination: temp-queue://ID:anafi.mydomain.org-41122-1260898846989-1:0:1\n[161.129.204.104:32918] DEBUG AbstractRegion - Removing\ndestination: topic://ActiveMQ.Advisory.Consumer.Queue.ID:\nanafi.mydomain.org-41122-1260898846989-1:0:1\n\n--0016e6d77df5212d68047aca90e2--\n\nFrom uima-user-returnkavery@example.com Tue Dec 15 23:04:04 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 98006 invoked from network); 15 Dec 2009 23:04:03 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 15 Dec 2009 23:04:03 -0000\nReceived: (qmail 74208 invoked by uid 500); 15 Dec 2009 23:04:03 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 74136 invoked by uid 500); 15 Dec 2009 23:04:02 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 74126 invoked by uid 99); 15 Dec 2009 23:04:02 -0000\nReceived: from athena.apache.org (HELO athena.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 23:04:02 +0000\nX-ASF-Spam-Status: No, hits=-2.6 required=5.0\n\ttests=BAYES_00\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO ey-out-1920.google.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 23:04:00 +0000\nReceived: by ey-out-1920.google.com with SMTP id 3so114868eyh.8\n for ; Tue, 15 Dec 2009 15:03:39 -0800 (PST)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:in-reply-to:references\n :date:message-id:subject:from:to:content-type;\n bh=Ddsa2bO/JUsMTXDNdwk8kXBW7Myb/tjSaUYYrxTee/Y=;\n b=fVXIWsFKafITEqybS/88j1yzOyT+X5etyCgOhRkRZFu49LJJcLnpVO1uyMOVvmoru5\n RTr1vFS0ANhRs7iP/P8X6ypZWA4GmgZ/srFXILQ6VovyjH/3JFbeg5GG8TFTpVPlRixq\n dLO+2/bilYlW1/9Zw5mv81eZxM+j7GRXPuW28=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:in-reply-to:references:date:message-id:subject:from:to\n :content-type;\n b=WXde5uF2Ik425rs8PyyDq9el9vCUYyf7fWiqS8UjImgNWrvDLu6ANCZdZEvYnLW+iC\n XLjdBSgZq/N4nhP+tayfhN7paed09btZAktIcAgmHCs+r7DqZlkIxoluvRx+3PPu+WD6\n k8jNykRh3RsIeM4ow2rzXkdEPGwX+tqJghEkg=\nMIME-Version: 1.0\nReceived: by 161.129.204.104 with SMTP id c7mr84464wef.62.1260918218831; Tue, 15 \n\tDec 2009 15:03:38 -0800 (PST)\nIn-Reply-To: \nReferences: \nDate: Tue, 15 Dec 2009 18:03:38 -0500\nMessage-ID: \nSubject: Re: Error on getMeta call to remote service\nFrom: Eddie Epstein \nTo: kavery@example.com\nContent-Type: text/plain; charset=ISO-8859-1\n\nOn Tue, Dec 15, 2009 at 3:52 PM, Prokopis Prokopidis\n wrote:\n> If it's\n> any help, when calling the service from the machine on which it has been\n> deployed, or when reversing the service-client roles between the two\n> machines, everything works as in the README file.\n\nHmmm, smells like a clock synchronization problem. In order to avoid\nundeliverable messages building up on a broker, timeout settings are\nused to create time-to-live properties in the JMS messages. ActiveMQ\nimplements time-to-live based on the client and server machine clocks.\n\nEddie\n\nFrom uima-user-returnkavery@example.com Tue Dec 15 23:05:55 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 98506 invoked from network); 15 Dec 2009 23:05:55 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 15 Dec 2009 23:05:55 -0000\nReceived: (qmail 75400 invoked by uid 500); 15 Dec 2009 23:05:55 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 75322 invoked by uid 500); 15 Dec 2009 23:05:54 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 75312 invoked by uid 99); 15 Dec 2009 23:05:54 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 23:05:54 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO mail-iw0-f201.google.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 23:05:46 +0000\nReceived: by iwn39 with SMTP id 39so278485iwn.32\n for ; Tue, 15 Dec 2009 15:05:25 -0800 (PST)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:in-reply-to:references\n :date:message-id:subject:from:to:content-type;\n bh=51ODYyq3HYXaJ8eQaBfFD4YT5AMghaqwwXHQxspKk8Y=;\n b=CsS8NIr/uUkh5kMsJVlQ5ZWBv/5beyAJmX0w3twF9iPpJuPB0YpfzigmYneY7Csavg\n YtrDSv7LOAQKZGBAjUzv9TGvbWvG9OmWSj1+BI6aIG88t8JfD+PEwtCbx+vVPk6jiIRP\n gKDdHKoVC2F0KroYxUgf1Jd7YXleHbcnFTOiU=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:in-reply-to:references:date:message-id:subject:from:to\n :content-type;\n b=XRowM8PWIClvooUMZf217jKGjdU0JZZQtaVOX36Yd9f+0hI+0AvlvJg+iU9AWbAymz\n hqGO9EixLgYrJWBJ1/ryR4SPyETfYnEU3A+CzYxTZZeaH44KPmVhfGZzueID/ptSXPwR\n YhvNSwUhYKuMsKl0dG/6ke/RUvqNdQbOHmQyQ=\nMIME-Version: 1.0\nReceived: by 161.129.204.104 with SMTP id r20mr198342iby.7.1260918325805; Tue, \n\t15 Dec 2009 15:05:25 -0800 (PST)\nIn-Reply-To: \nReferences: \nDate: Tue, 15 Dec 2009 18:05:25 -0500\nMessage-ID: \nSubject: Re: Resource override in aggregate AE\nFrom: Pablo Duboue \nTo: kavery@example.com\nContent-Type: text/plain; charset=ISO-8859-1\nX-Virus-Checked: Checked by ClamAV on apache.org\n\nHi Karin!\n\nGlad to hear you're using UIMA.\n\nI have had no particular problem with the resource bindings and I'm\nusing them quite heavily. Do you mind posting the relevant bits from\nyour descriptors?\n\nSending you my best regards from NY,\n\nPablo\n\nFrom uima-user-returnkavery@example.com Wed Dec 16 10:03:02 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 58884 invoked from network); 16 Dec 2009 10:03:02 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 10:03:02 -0000\nReceived: (qmail 93495 invoked by uid 500); 16 Dec 2009 10:03:02 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 93440 invoked by uid 500); 16 Dec 2009 10:03:01 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 93430 invoked by uid 99); 16 Dec 2009 10:03:00 -0000\nReceived: from athena.apache.org (HELO athena.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 10:03:00 +0000\nX-ASF-Spam-Status: No, hits=-2.6 required=5.0\n\ttests=BAYES_00\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: local policy)\nReceived: from [161.129.204.104] (HELO Athens.ilsp.gr) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 10:02:58 +0000\nReceived: from antiparos.ilsp.gr ([161.129.204.104]) by Athens.ilsp.gr with Microsoft SMTPSVC(314)481-9074);\n\t Wed, 16 Dec 2009 12:02:35 +0200\nMessage-ID: \nDate: Wed, 16 Dec 2009 12:02:30 +0200\nFrom: Prokopis Prokopidis \nOrganization: ILSP\nUser-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:161.129.204.104pre) Gecko/20090922 Fedora/3.0-3.9.b4.fc12 Lightning/1.0pre Thunderbird/3.0b4\nMIME-Version: 1.0\nTo: \"uima-user \"@incubator.apache.org\nSubject: Re: Error on getMeta call to remote service\nContent-Type: text/plain; charset=UTF-8; format=flowed\nContent-Transfer-Encoding: 7bit\nX-OriginalArrivalTime: 16 Dec 2009 10:02:35.0252 (UTC) FILETIME=[E407A340:01CA7E36]\n\n> On Tue, Dec 15, 2009 at 3:52 PM, Prokopis Prokopidis wrote:\n>\n> > If it's any help, when calling the service from the\n> > machine on which it has been deployed, or when reversing\n> > the service-client roles between the two machines,\n> > everything works as in the README file.\n>\n> Hmmm, smells like a clock synchronization problem. In order to avoid\n> undeliverable messages building up on a broker, timeout settings\n> are used to create time-to-live properties in the JMS messages.\n> ActiveMQ implements time-to-live based on the client and server\n> machine clocks.\n>\n> Eddie\n\nThank you! Following your advice and after synchronizing the clocks on \nboth machines (via ntpd) I managed to call the service as expected.\n\nSince I am no ActiveMQ expert, I'm now left wondering whether there is a \nway to ensure that similar problems do not come up if a real-life \nservice is accessed by clients with unsynchronized clocks (on which \nclients, of course, I will not be able to synchronize the clock).\n\nIs this an issue which can be resolved in the client or server side code \nand in the example of the AS distribution as well? Should I create an \nissue in JIRA?\n\nBest,\n\nProkopis\n\n\nFrom uima-user-returnkavery@example.com Wed Dec 16 12:24:58 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 27348 invoked from network); 16 Dec 2009 12:24:58 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 12:24:58 -0000\nReceived: (qmail 98935 invoked by uid 500); 16 Dec 2009 12:24:57 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 98850 invoked by uid 500); 16 Dec 2009 12:24:56 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 98840 invoked by uid 99); 16 Dec 2009 12:24:56 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 12:24:56 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO ey-out-1920.google.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 12:24:48 +0000\nReceived: by ey-out-1920.google.com with SMTP id 3so221563eyh.8\n for ; Wed, 16 Dec 2009 04:24:28 -0800 (PST)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:in-reply-to:references\n :date:message-id:subject:from:to:content-type\n :content-transfer-encoding;\n bh=A0AIfJ0PwG4BMsFKJ+xzz5T89FmNJPTBHf5suJOLGYA=;\n b=hDEQ0QAAJxptnfAGXtl2NhOehjQd86DasRD+G54lXFeLg6knAeYZW5/yXp7hBSdaSm\n mooyax4mqgUctWbrZqIVpgJVn1zZTnhxZp5AhqFZ9i3QCKrOgFIsQLwXG31g1P7GGauj\n EMgDRCAd1cdL38zcEKVChsrMjOYyPVNa7MPUI=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:in-reply-to:references:date:message-id:subject:from:to\n :content-type:content-transfer-encoding;\n b=l66xtI/1a65sP7gp7OqTdLGhlnOhhVNHk9ZIkVF9HEfDpkRLgDvLazE2cGwec1AOVh\n 5QV4xW7AboOOG7J2FykklOYw3iKBHK+ErFXwK4OI9GoNmzB0pIanTFKuYGVzLmytdanR\n UC3gJlop2N39/0gMViKyJLKwzB56L8b3z/pVo=\nMIME-Version: 1.0\nReceived: by 161.129.204.104 with SMTP id y5mr361569wee.139.1260966268194; Wed, \n\t16 Dec 2009 04:24:28 -0800 (PST)\nIn-Reply-To: \nReferences: \nDate: Wed, 16 Dec 2009 07:24:28 -0500\nMessage-ID: \nSubject: Re: Error on getMeta call to remote service\nFrom: Eddie Epstein \nTo: kavery@example.com\nContent-Type: text/plain; charset=ISO-8859-1\nContent-Transfer-Encoding: quoted-printable\nX-Virus-Checked: Checked by ClamAV on apache.org\n\nActiveMQ has an optional broker plugin that adjusts time-to-live such that =\nonly\nthe broker and service machines have to be synchronized. We couldn't get th=\nis\nto work on AMQ 4.1.1, but assume it has been fixed in 5.2. Feel free to cre=\nate\nan issue and we can use it to at least fix documentation, if not more.\n\nEddie\n\nOn Wed, Dec 16, 2009 at 5:02 AM, Prokopis Prokopidis wro=\nte:\n>> On Tue, Dec 15, 2009 at 3:52 PM, Prokopis Prokopidis \n>> wrote:\n>>\n>> > If it's any help, when calling the service from the\n>> > machine on which it has been deployed, or when reversing\n>> > the service-client roles between the two machines,\n>> > everything works as in the README file.\n>>\n>> Hmmm, smells like a clock synchronization problem. In order to avoid\n>> undeliverable messages building up on a broker, timeout settings\n>> are used to create time-to-live properties in the JMS messages.\n>> ActiveMQ implements time-to-live based on the client and server\n>> machine clocks.\n>>\n>> Eddie\n>\n> Thank you! Following your advice and after synchronizing the clocks on bo=\nth\n> machines (via ntpd) I managed to call the service as expected.\n>\n> Since I am no ActiveMQ expert, I'm now left wondering whether there is a =\nway\n> to ensure that similar problems do not come up if a real-life service is\n> accessed by clients with unsynchronized clocks (on which clients, of cour=\nse,\n> =A0I will not be able to synchronize the clock).\n>\n> Is this an issue which can be resolved in the client or server side code =\nand\n> in the example of the AS distribution as well? Should I create an issue i=\nn\n> JIRA?\n>\n> Best,\n>\n> Prokopis\n>\n>\n\nFrom uima-user-returnkavery@example.com Wed Dec 16 12:30:41 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 29621 invoked from network); 16 Dec 2009 12:30:40 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 12:30:40 -0000\nReceived: (qmail 3648 invoked by uid 500); 16 Dec 2009 12:30:40 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 3601 invoked by uid 500); 16 Dec 2009 12:30:40 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 3591 invoked by uid 99); 16 Dec 2009 12:30:40 -0000\nReceived: from athena.apache.org (HELO athena.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 12:30:40 +0000\nX-ASF-Spam-Status: No, hits=-2.5 required=5.0\n\ttests=AWL,BAYES_00\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO gateway10.websitewelcome.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with SMTP; Wed, 16 Dec 2009 12:30:37 +0000\nReceived: (qmail 14000 invoked from network); 16 Dec 2009 12:44:50 -0000\nReceived: from gator74.hostgator.com (161.129.204.104)\n by gateway10.websitewelcome.com with SMTP; 16 Dec 2009 12:44:50 -0000\nReceived: from ool-44c6c63b.dyn.optonline.net ([161.129.204.104]:15002 helo=[161.129.204.104])\n\tby gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256)\n\t(Exim 4.69)\n\t(envelope-from )\n\tid 1NKt1D-0006xV-Jw\n\tfor kavery@example.com; Wed, 16 Dec 2009 06:30:15 -0600\nMessage-ID: \nDate: Wed, 16 Dec 2009 07:30:19 -0500\nFrom: Marshall Schor \nUser-Agent: Thunderbird 161.129.204.104 (Windows/20090812)\nMIME-Version: 1.0\nTo: kavery@example.com\nSubject: Re: Error on getMeta call to remote service\nReferences: \nIn-Reply-To: \nX-Enigmail-Version: 0.96.0\nContent-Type: text/plain; charset=UTF-8\nContent-Transfer-Encoding: 8bit\nX-AntiAbuse: This header was added to track abuse, please include it with any abuse report\nX-AntiAbuse: Primary Hostname - gator74.hostgator.com\nX-AntiAbuse: Original Domain - incubator.apache.org\nX-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]\nX-AntiAbuse: Sender Address Domain - schor.com\n\n\n\nProkopis Prokopidis wrote:\n>> On Tue, Dec 15, 2009 at 3:52 PM, Prokopis Prokopidis\n>> wrote:\n>>\n>> > If it's any help, when calling the service from the\n>> > machine on which it has been deployed, or when reversing\n>> > the service-client roles between the two machines,\n>> > everything works as in the README file.\n>>\n>> Hmmm, smells like a clock synchronization problem. In order to avoid\n>> undeliverable messages building up on a broker, timeout settings\n>> are used to create time-to-live properties in the JMS messages.\n>> ActiveMQ implements time-to-live based on the client and server\n>> machine clocks.\n>>\n>> Eddie\n>\n> Thank you! Following your advice and after synchronizing the clocks on\n> both machines (via ntpd) I managed to call the service as expected.\n>\n> Since I am no ActiveMQ expert, I'm now left wondering whether there is\n> a way to ensure that similar problems do not come up if a real-life\n> service is accessed by clients with unsynchronized clocks (on which\n> clients, of course, I will not be able to synchronize the clock).\n\nYes, this is a known issue with various versions of ActiveMQ. You can\nfind these issues via searching the web with keywords like:\nActiveMQ clock sync synchronize time live\n>\n> Is this an issue which can be resolved in the client or server side\n> code and in the example of the AS distribution as well? Should I\n> create an issue in JIRA?\n\nI'm not the expert here. However, there was a mention of some kind of\nwork-around, on this Jira:\nhttps://issues.apache.org/activemq/browse/AMQ-975\n\nwhere a user said:\n\nIn my case I don't have the machines synchronized, because producers,\nconsumers and brokers ... run in different countries and are\nadministrated by different people.\n\nand the response was:\n\nYou should set the timestamp on messages on your broker by using the\nTimeStampBrokerPlugin -\nhttp://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/util/TimeStampingBrokerPlugin.html^\n\n\nsee http://activemq.apache.org/interceptors.html^ for info on how to set\na broker interceptor\n\nThe api says:\n\nA Broker interceptor which updates a JMS Client's timestamp on the\nmessage with a broker timestamp. Useful when the clocks on client\nmachines are known to not be correct and you can only trust the time set\non the broker machines. Enabling this plugin will break JMS compliance\nsince the timestamp that the producer sees on the messages after as\nsend() will be different from the timestamp the consumer will observe\nwhen he receives the message. This plugin is not enabled in the default\nActiveMQ configuration.\n\n[ Show » ]\nRob Davies\n\nadded a comment - 23/May/09 02:00 AM You should set the timestamp on\nmessages on your broker by using the TimeStampBrokerPlugin -\nhttp://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/util/TimeStampingBrokerPlugin.html^\nsee http://activemq.apache.org/interceptors.html^ for info on how to set\na broker interceptor\nHope this helps...\n\n-Marshall\n>\n> Best,\n>\n> Prokopis\n>\n>\n>\n\nFrom uima-user-returnkavery@example.com Wed Dec 16 13:29:45 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 60506 invoked from network); 16 Dec 2009 13:29:45 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 13:29:45 -0000\nReceived: (qmail 83971 invoked by uid 500); 16 Dec 2009 13:29:45 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 83942 invoked by uid 500); 16 Dec 2009 13:29:45 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nDelivered-To: moderator for kavery@example.com\nReceived: (qmail 72067 invoked by uid 99); 16 Dec 2009 13:23:23 -0000\nX-ASF-Spam-Status: No, hits=-2.6 required=5.0\n\ttests=BAYES_00\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nFrom: michael \nContent-Type: text/plain; charset=us-ascii\nContent-Transfer-Encoding: quoted-printable\nSubject: UIMA and version conflicts\nDate: Wed, 16 Dec 2009 23:52:57 +1030\nMessage-Id: \nTo: kavery@example.com\nMime-Version: 1.0 (Apple Message framework v1077)\nX-Mailer: Apple Mail (2.1077)\n\nHi,\n\nI'm trying to use UIMA to run multiple Analysis Engines over a single =\nCAS in a Java application (not web/ tomcat stuff).\nEach Analysis Engine descriptor will have been installed from its own =\npear file and may have dependencies upon versions of jar files included =\nin the pear that conflict with those in other installed pears. I have =\nbeen trying to do this using code similar to that in the Run CPE GUI. =\nBut it seems to assume one Resource Manager must be shared between the =\nCollection Reader and each Analysis Engine. So I am stumped.\n1) Can a single CAS have a different Resource Managers to define the =\nclasspaths for each Analysis Engine that populates it?\n2) If no, Would UIMA-AS be a solution?\n3) Parameter overrides need to be able to be applied to the Analysis =\nEngines before they are run. Does this mean I cannot use UIMA-AS?=20\n\nthanks in advance,\n-Michael.=\n\nFrom uima-user-returnkavery@example.com Wed Dec 16 13:36:08 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 63367 invoked from network); 16 Dec 2009 13:36:08 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 13:36:08 -0000\nReceived: (qmail 95043 invoked by uid 500); 16 Dec 2009 13:36:08 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 95001 invoked by uid 500); 16 Dec 2009 13:36:08 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 94991 invoked by uid 99); 16 Dec 2009 13:36:08 -0000\nReceived: from athena.apache.org (HELO athena.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 13:36:08 +0000\nX-ASF-Spam-Status: No, hits=-2.5 required=5.0\n\ttests=AWL,BAYES_00\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO mail.gmx.net) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with SMTP; Wed, 16 Dec 2009 13:36:05 +0000\nReceived: (qmail invoked by alias); 16 Dec 2009 13:35:43 -0000\nReceived: from deibp9eh1--blueice2n1.emea.ibm.com (EHLO [161.129.204.104]) [161.129.204.104]\n by mail.gmx.net (mp064) with SMTP; 16 Dec 2009 14:35:43 +0100\nX-Authenticated: #25330878\nX-Provags-ID: V01U2FsdGVkX1/5vc1KGpf5wXt9Gr2UpfXsTW4CFJshimDI68qi0L\n\tjVziayVoke18mZ\nMessage-ID: \nDate: Wed, 16 Dec 2009 14:35:43 +0100\nFrom: Thilo Goetz \nUser-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:161.129.204.104) Gecko/20091204 Thunderbird/3.0\nMIME-Version: 1.0\nTo: kavery@example.com\nSubject: Re: UIMA and version conflicts\nReferences: \nIn-Reply-To: \nX-Enigmail-Version: 1.0\nContent-Type: text/plain; charset=ISO-8859-1\nContent-Transfer-Encoding: 7bit\nX-Y-GMX-Trusted: 0\nX-FuHaFi: 0.64\n\nHi, please subscribe to the mailing list so we don't have to\nmoderate your messages. Comments below.\n\nOn 12/16/2009 14:22, michael wrote:\n> Hi,\n> \n> I'm trying to use UIMA to run multiple Analysis Engines over a single CAS in a Java application (not web/ tomcat stuff).\n> Each Analysis Engine descriptor will have been installed from its own pear file and may have dependencies upon versions of jar files included in the pear that conflict with those in other installed pears. I have been trying to do this using code similar to that in the Run CPE GUI. But it seems to assume one Resource Manager must be shared between the Collection Reader and each Analysis Engine. So I am stumped.\n\nWhy don't you just create an aggregate descriptor that\npoints at the various pear descriptors?\n\n> 1) Can a single CAS have a different Resource Managers to define the classpaths for each Analysis Engine that populates it?\n> 2) If no, Would UIMA-AS be a solution?\n> 3) Parameter overrides need to be able to be applied to the Analysis Engines before they are run. Does this mean I cannot use UIMA-AS? \n\nThis is broken in 2.2.2, but fixed in the upcoming 2.3 code.\n\n> \n> thanks in advance,\n> -Michael.\n\nFrom uima-user-returnkavery@example.com Wed Dec 16 14:27:11 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 92762 invoked from network); 16 Dec 2009 14:27:11 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 14:27:11 -0000\nReceived: (qmail 77585 invoked by uid 500); 16 Dec 2009 14:27:10 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 77507 invoked by uid 500); 16 Dec 2009 14:27:09 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 77496 invoked by uid 99); 16 Dec 2009 14:27:09 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 14:27:09 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO mail-ew0-f220.google.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 14:27:01 +0000\nReceived: by ewy20 with SMTP id 20so1123252ewy.20\n for ; Wed, 16 Dec 2009 06:26:41 -0800 (PST)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:in-reply-to:references\n :date:message-id:subject:from:to:content-type;\n bh=VW7wlfIESDgF+zPtEn871j2s4OR5TjPVvRAXPkK8VoI=;\n b=qTPPYdEqESyJzHQBo3SlYYhnb7KtRfU82hPKrbroIfW7UfZnnrU+M60SAp4ZNLrDxj\n aRdPbLFmXRTqEYnOFJ2PbMf6BA2TVulzlLuN3iUIBxSPqu7Mik4snIVa8765TNo1H4/T\n GZCyhl+4GO33MRPQVpSuBw+I2CaVU1FG09zkc=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:in-reply-to:references:date:message-id:subject:from:to\n :content-type;\n b=cMY75SWgqd6OyHMPRJ5TzhuIIy12ul3Ah4oGjDWc1UAqkOVa4WMlrv77ByS8Q/NhNT\n /LNsDLdWZFFgbsxJ4hKb3Nv4gAAA4hAn7xTDb8Ps3X4YD8R16mFx+Q5Dh/Uw2at+vxzk\n 1QjJFIlkk4GFIJQM3If/MWFsaGUp7sALNVaAk=\nMIME-Version: 1.0\nReceived: by 161.129.204.104 with SMTP id y19mr409037wee.12.1260973600721; Wed, \n\t16 Dec 2009 06:26:40 -0800 (PST)\nIn-Reply-To: \nReferences: \nDate: Wed, 16 Dec 2009 09:26:40 -0500\nMessage-ID: \nSubject: Re: Error on getMeta call to remote service\nFrom: Eddie Epstein \nTo: kavery@example.com\nContent-Type: text/plain; charset=ISO-8859-1\nX-Virus-Checked: Checked by ClamAV on apache.org\n\nAnother way to deal with this issue is described here:\nhttps://issues.apache.org/jira/browse/UIMA-1120\n\nEddie\n\nFrom uima-user-returnkavery@example.com Wed Dec 16 19:59:34 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 57717 invoked from network); 16 Dec 2009 19:59:34 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 19:59:34 -0000\nReceived: (qmail 26691 invoked by uid 500); 16 Dec 2009 19:59:34 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 26607 invoked by uid 500); 16 Dec 2009 19:59:33 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 26597 invoked by uid 99); 16 Dec 2009 19:59:32 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 19:59:32 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO gateway16.websitewelcome.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with SMTP; Wed, 16 Dec 2009 19:59:23 +0000\nReceived: (qmail 4834 invoked from network); 16 Dec 2009 20:15:26 -0000\nReceived: from gator74.hostgator.com (161.129.204.104)\n by gateway16.websitewelcome.com with SMTP; 16 Dec 2009 20:15:26 -0000\nReceived: from yktgi01e0-s5.watson.ibm.com ([161.129.204.104]:31565 helo=[161.129.204.104])\n\tby gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256)\n\t(Exim 4.69)\n\t(envelope-from )\n\tid 1NL01U-00059a-N8\n\tfor kavery@example.com; Wed, 16 Dec 2009 13:59:00 -0600\nMessage-ID: \nDate: Wed, 16 Dec 2009 14:59:04 -0500\nFrom: Marshall Schor \nUser-Agent: Thunderbird 161.129.204.104 (Windows/20090812)\nMIME-Version: 1.0\nTo: kavery@example.com\nSubject: Re: UIMA and version conflicts\nReferences: \nIn-Reply-To: \nX-Enigmail-Version: 0.96.0\nContent-Type: text/plain; charset=ISO-8859-1\nContent-Transfer-Encoding: 7bit\nX-AntiAbuse: This header was added to track abuse, please include it with any abuse report\nX-AntiAbuse: Primary Hostname - gator74.hostgator.com\nX-AntiAbuse: Original Domain - incubator.apache.org\nX-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]\nX-AntiAbuse: Sender Address Domain - schor.com\nX-Virus-Checked: Checked by ClamAV on apache.org\n\n\n\nThilo Goetz wrote:\n> Hi, please subscribe to the mailing list so we don't have to\n> moderate your messages. Comments below.\n>\n> On 12/16/2009 14:22, michael wrote:\n> \n>> Hi,\n>>\n>> I'm trying to use UIMA to run multiple Analysis Engines over a single CAS in a Java application (not web/ tomcat stuff).\n>> Each Analysis Engine descriptor will have been installed from its own pear file and may have dependencies upon versions of jar files included in the pear that conflict with those in other installed pears. I have been trying to do this using code similar to that in the Run CPE GUI. But it seems to assume one Resource Manager must be shared between the Collection Reader and each Analysis Engine. So I am stumped.\n>> \n>\n> Why don't you just create an aggregate descriptor that\n> points at the various pear descriptors?\n> \n\nWhen you build an aggregate, you can have the delegates be either other\naggregates or primitives, or a pear descriptor (which you get when you\ninstall a pear). If you the pear descriptor, UIMA will set up a special\nclass loader for running whatever that pear specifies, in which the\nclasspath is set to whatever the pear says to use. This is supposed to\ndo exactly what you're hoping - allow different versions of things to\nco-exist.\n> \n>> 1) Can a single CAS have a different Resource Managers to define the classpaths for each Analysis Engine that populates it?\n>> \n\nSure - use the pear approach described above, and also described here:\nhttp://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.jcas.pear_support\n>> 2) If no, Would UIMA-AS be a solution?\n>> 3) Parameter overrides need to be able to be applied to the Analysis Engines before they are run. Does this mean I cannot use UIMA-AS? \n>> \n>\n> This is broken in 2.2.2, but fixed in the upcoming 2.3 code.\n>\n> \n\n\"This\" in the above, in case it isn't clear, means that parameter\noverrides for pears run inside an aggregate was not supported in 2.2.2,\nbut now is in the soon to be release 2.3.0 version.\n\nHope this helps... -Marshall\n>> thanks in advance,\n>> -Michael.\n>> \n>\n>\n> \n\nFrom uima-user-returnkavery@example.com Wed Dec 16 22:17:16 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 24312 invoked from network); 16 Dec 2009 22:17:16 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 22:17:16 -0000\nReceived: (qmail 18494 invoked by uid 500); 16 Dec 2009 22:17:15 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 18414 invoked by uid 500); 16 Dec 2009 22:17:14 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nDelivered-To: moderator for kavery@example.com\nReceived: (qmail 5816 invoked by uid 99); 16 Dec 2009 22:09:04 -0000\nX-ASF-Spam-Status: No, hits=2.2 required=10.0\n\ttests=HTML_MESSAGE,SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:date:message-id:subject\n :from:to:content-type;\n bh=EbYiOcPwrWimebRztr6m0/K5LmYG2S5spdcHXHsDSKc=;\n b=aKfFlvEETjtSrYt2Nk7QI4ZtWcWf26gAExoW6qupIjyOKaJo/kd3POxztvtj+M/2+I\n B00csSZ97U0W+OIJm5zDtL//KDSxEQfYBX+d54H41rlAItoo77Jo8rNolliD30Ov0Q3I\n EVahPaWxZIZRG+1en535ciImUwCNjQtgGfT0w=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:date:message-id:subject:from:to:content-type;\n b=KF7pGUWaA6qWcGJ2HJA8cK8BqHp6nI8f0eznxMBjmEZilsYTB8gA2NNi/9ZMN9BRfu\n yElRvaF2wBEEr4TFVII8A8jHMoPrAM8A0qtRMgitwfhlJ+LhQDA0Tqu7ZsJERx7g5j/K\n ImVcj/aVhDvDE+ul8t7j9de7v3nqDbdA/ltS0=\nMIME-Version: 1.0\nDate: Wed, 16 Dec 2009 14:08:35 -0800\nMessage-ID: \nSubject: Usage of annotator \"capabilities\"\nFrom: Anton Shuster \nTo: kavery@example.com\nContent-Type: multipart/alternative; boundary=0016e6dab02280175b047adfbf04\nX-Virus-Checked: Checked by ClamAV on apache.org\n\n--0016e6dab02280175b047adfbf04\nContent-Type: text/plain; charset=ISO-8859-1\n\nHello all,\n\nThere is a capabilities section in the descriptor for an annotator where one\ndefines which annotations the annotator expects to find and which ones it\nproduces. However, despite how useful this information is, I can't seem to\nfind how it gets used (other than for documentation purposes).\n\nIn particular, I was wondering if there's some sort of verifier or something\nthat can (or does) check whether an that produces annotations of type A has\nrun before an annotator that expects annotations of type A. Also, it would\nbe useful if there was a flow controller that used the capability\ninformation to call annotators in an order such that these dependencies are\nsatisfied (like in the case just mentioned).\n\nIs there anything built into UIMA that uses this stuff?\n\nThanks!\n--Anton\n\n--0016e6dab02280175b047adfbf04--\n\nFrom uima-user-returnkavery@example.com Wed Dec 16 22:26:48 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 31104 invoked from network); 16 Dec 2009 22:26:48 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 22:26:48 -0000\nReceived: (qmail 34808 invoked by uid 500); 16 Dec 2009 22:26:48 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 34771 invoked by uid 500); 16 Dec 2009 22:26:48 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 34761 invoked by uid 99); 16 Dec 2009 22:26:48 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 22:26:48 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO gateway06.websitewelcome.com) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with SMTP; Wed, 16 Dec 2009 22:26:38 +0000\nReceived: (qmail 17954 invoked from network); 16 Dec 2009 22:45:31 -0000\nReceived: from gator74.hostgator.com (161.129.204.104)\n by gateway06.websitewelcome.com with SMTP; 16 Dec 2009 22:45:31 -0000\nReceived: from yktgi01e0-s5.watson.ibm.com ([161.129.204.104]:41368 helo=[161.129.204.104])\n\tby gator74.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256)\n\t(Exim 4.69)\n\t(envelope-from )\n\tid 1NL2Jz-00042g-Il\n\tfor kavery@example.com; Wed, 16 Dec 2009 16:26:15 -0600\nMessage-ID: \nDate: Wed, 16 Dec 2009 17:26:18 -0500\nFrom: Marshall Schor \nUser-Agent: Thunderbird 161.129.204.104 (Windows/20090812)\nMIME-Version: 1.0\nTo: kavery@example.com\nSubject: Re: Usage of annotator \"capabilities\"\nReferences: \nIn-Reply-To: \nX-Enigmail-Version: 0.96.0\nContent-Type: text/plain; charset=ISO-8859-1\nContent-Transfer-Encoding: 7bit\nX-AntiAbuse: This header was added to track abuse, please include it with any abuse report\nX-AntiAbuse: Primary Hostname - gator74.hostgator.com\nX-AntiAbuse: Original Domain - incubator.apache.org\nX-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]\nX-AntiAbuse: Sender Address Domain - schor.com\nX-Virus-Checked: Checked by ClamAV on apache.org\n\n\n\nAnton Shuster wrote:\n> Hello all,\n>\n> There is a capabilities section in the descriptor for an annotator where one\n> defines which annotations the annotator expects to find and which ones it\n> produces. However, despite how useful this information is, I can't seem to\n> find how it gets used (other than for documentation purposes).\n>\n> In particular, I was wondering if there's some sort of verifier or something\n> that can (or does) check whether an that produces annotations of type A has\n> run before an annotator that expects annotations of type A. Also, it would\n> be useful if there was a flow controller that used the capability\n> information to call annotators in an order such that these dependencies are\n> satisfied (like in the case just mentioned).\n>\n> Is there anything built into UIMA that uses this stuff?\n>\n> \n\nHi Anton,\n\nHere are a few places where the capabilities are used.\n\nThere is a built-in flow controller, called Capability Language flow,\nthat uses this info - see\nhttp://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html\nand search for Capability Language.\n\nThe Document Analyzer uses this information to decide what annotations\nto show when displaying results.\n\nThe framework itself uses this information in setting up the default\n\"results specification\" for a component, although the logic is fairly\ncomplex - see the discussion here: \nhttp://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tutorials_and_users_guides/tutorials_and_users_guides.html#ugr.tug.aae.result_specification_setting\n\nThe Component Descriptor Editor has a search capability for finding\nannotators to add to an aggregate, that can search on types that are\ndeclared to be output by candidate annotators.\n\n-Marshall\n> Thanks!\n> --Anton\n>\n> \n\nFrom uima-user-returnkavery@example.com Wed Dec 16 22:38:18 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 36735 invoked from network); 16 Dec 2009 22:38:18 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 16 Dec 2009 22:38:18 -0000\nReceived: (qmail 42865 invoked by uid 500); 16 Dec 2009 22:38:18 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 42801 invoked by uid 500); 16 Dec 2009 22:38:18 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 42791 invoked by uid 99); 16 Dec 2009 22:38:18 -0000\nReceived: from athena.apache.org (HELO athena.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 22:38:18 +0000\nX-ASF-Spam-Status: No, hits=-2.6 required=5.0\n\ttests=BAYES_00\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO lo.gmane.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Dec 2009 22:38:15 +0000\nReceived: from list by lo.gmane.org with local (Exim 4.50)\n\tid 1NL2VE-00085e-UO\n\tfor kavery@example.com; Wed, 16 Dec 2009 23:37:53 +0100\nReceived: from eth3395.vic.adsl.internode.on.net ([161.129.204.104])\n by main.gmane.org with esmtp (Gmexim 0.1 (Debian))\n id 1AlnuQ-0007hv-00\n for ; Wed, 16 Dec 2009 23:37:52 +0100\nReceived: from hansen.candrawinata by eth3395.vic.adsl.internode.on.net with local (Gmexim 0.1 (Debian))\n id 1AlnuQ-0007hv-00\n for ; Wed, 16 Dec 2009 23:37:52 +0100\nX-Injected-Via-Gmane: http://gmane.org/\nTo: kavery@example.com\nFrom: Hansen Candrawinata \nSubject: Re: Exception thrown when deploying CAS Processors in managed mode\nDate: Wed, 16 Dec 2009 22:37:30 +0000 (UTC)\nLines: 12\nMessage-ID: \nReferences: \nMime-Version: 1.0\nContent-Type: text/plain; charset=us-ascii\nContent-Transfer-Encoding: 7bit\nX-Complaints-To: kavery@example.com\nX-Gmane-NNTP-Posting-Host: sea.gmane.org\nUser-Agent: Loom/3.14 (http://gmane.org/)\nX-Loom-IP: 161.129.204.104 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:161.129.204.104) Gecko/20091102 Firefox/3.5.5)\nSender: news \n\nHansen Candrawinata writes:\n> Yes, I am still not able to deploy my CAS processors in managed mode. I still\n> get the same error, that is, a failure in converting CAS object to CAS data\n> which then lead to the CPM and Vinci service stopping.\n\nHi,\n\nAnyone had a chance to look into this issue? Any hints, directions or examples\nwould be very much appreciated.\n\nThanks!\nHansen\n\n\nFrom uima-user-returnkavery@example.com Thu Dec 17 13:34:57 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 80806 invoked from network); 17 Dec 2009 13:34:21 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 17 Dec 2009 13:34:21 -0000\nReceived: (qmail 99579 invoked by uid 500); 17 Dec 2009 13:34:21 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 99501 invoked by uid 500); 17 Dec 2009 13:34:19 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nDelivered-To: moderator for kavery@example.com\nReceived: (qmail 82642 invoked by uid 99); 17 Dec 2009 00:48:27 -0000\nX-ASF-Spam-Status: No, hits=-2.6 required=5.0\n\ttests=AWL,BAYES_00,HTML_MESSAGE\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (athena.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nDKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=gamma;\n h=domainkey-signature:mime-version:received:date:message-id:subject\n :from:to:content-type;\n bh=Z/8W/hy4eehEWMSY80pA4IOdzEp1BUP0sBsucas1Ylo=;\n b=il6CA1CqM7WqSEa60DLzi5Ocxlt11vRFJsuhapMNE/bLiBct/me9dyc5xIFR6p2GdT\n +/NOz7NlLWnwfYrgkskODBySSc7MGE4zPmhjBiGtTITsIUnToqSs0cJvMEzoOzNdqNZA\n TuPMiyUDgwdWRn+41KoZy4w+fpfylSBKe4Iys=\nDomainKey-Signature: a=rsa-sha1; c=nofws;\n d=gmail.com; s=gamma;\n h=mime-version:date:message-id:subject:from:to:content-type;\n b=pHxoBCUBl+MtNi2mcWnWYXWsvfq9SrytReg2W7oZdvb0tzHuvH6a86N3VjrNtNniOj\n gQJXKH1MmJPE8hK6h2xxb3NCgCjrcYAfbX/JgOU0wBmmuv25u5R4gaCzm29DB1dexT6d\n 1W15mX9ao6CtzhH8RT2ETWezvvTcogHbQCkV0=\nMIME-Version: 1.0\nDate: Wed, 16 Dec 2009 16:48:03 -0800\nMessage-ID: \nSubject: Extent of resource management memory sharing\nFrom: Anton Shuster \nTo: kavery@example.com\nContent-Type: multipart/alternative; boundary=0016e6d56698c6e15d047ae1f95b\n\n--0016e6d56698c6e15d047ae1f95b\nContent-Type: text/plain; charset=ISO-8859-1\n\nHello all,\n\nIt seems the advantage of using the resource management features of UIMA is\nthe ability for annotators to use the same instance of a resource interface\nin memory. However, from the description in the manual it seems that this\nmay be only possible when all the annotators that use the same resource are\nin the same aggregate analysis engine descriptor. Is this true?\n\nIn particular, what happens if the annotators are loaded separately (using\ntheir respective descriptors where each one declares the same resource and\nbinds it to the same interface)? Do they share memory for the interface? Or\nwill there be two instances of the resource? Is it possible to make them\nshare memory?\n\nThanks!\n--Anton\n\n--0016e6d56698c6e15d047ae1f95b--\n\nFrom uima-user-returnkavery@example.com Thu Dec 17 14:57:16 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 31221 invoked from network); 17 Dec 2009 14:57:16 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 17 Dec 2009 14:57:16 -0000\nReceived: (qmail 82230 invoked by uid 500); 17 Dec 2009 14:57:15 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 82194 invoked by uid 500); 17 Dec 2009 14:57:15 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nDelivered-To: moderator for kavery@example.com\nReceived: (qmail 74206 invoked by uid 99); 17 Dec 2009 14:13:48 -0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nX-Authenticated: #35903713\nX-Provags-ID: V01U2FsdGVkX1/XJBw1i/vXWMkiS594ViSr6flL0X2Xb7da3hxA4f\n\ttJeNWvmxblniEE\nMessage-ID: \nDate: Thu, 17 Dec 2009 15:13:10 +0100\nFrom: Sven Hesselbach \nUser-Agent: Thunderbird 161.129.204.104 (Windows/20090812)\nMIME-Version: 1.0\nTo: kavery@example.com\nSubject: Parser Analysis Engines\nContent-Type: text/plain; charset=ISO-8859-15; format=flowed\nContent-Transfer-Encoding: 7bit\nX-Y-GMX-Trusted: 0\nX-FuHaFi: 0.67\nX-Virus-Checked: Checked by ClamAV on apache.org\n\nHello,\n\nI'm currently working on my masters thesis about (natural language) \nparsing technology.\nI'd like to integrate and test different existing Parser AEs in an UIMA \nbased NLP pipeline.\nI've already found several implementations, such as JulieLab's OpenNLP \nand MST Parser Wrapper or\nthe Enju Parser (found at http://u-compare.org/). Despite of intensive \nsearching I unfortunately\ncouldn't find additional Parser AEs.\n\nDoes anyone know about other Parser Analysis Engines (e.g. Stanford \nParser, Malt Parser)?\n\n\nThank you,\n\nSven\n\n\n\n\n\n\nFrom uima-user-returnkavery@example.com Thu Dec 17 15:03:41 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 33726 invoked from network); 17 Dec 2009 15:03:40 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 17 Dec 2009 15:03:40 -0000\nReceived: (qmail 96835 invoked by uid 500); 17 Dec 2009 15:03:39 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 96799 invoked by uid 500); 17 Dec 2009 15:03:39 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: \nReply-To: kavery@example.com\nDelivered-To: mailing list kavery@example.com\nReceived: (qmail 96789 invoked by uid 99); 17 Dec 2009 15:03:39 -0000\nReceived: from nike.apache.org (HELO nike.apache.org) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 15:03:39 +0000\nX-ASF-Spam-Status: No, hits=-0.0 required=10.0\n\ttests=SPF_PASS\nX-Spam-Check-By: apache.org\nReceived-SPF: pass (nike.apache.org: domain of kavery@example.com designates 161.129.204.104 as permitted sender)\nReceived: from [161.129.204.104] (HELO mail.gmx.net) (161.129.204.104)\n by apache.org (qpsmtpd/0.29) with SMTP; Thu, 17 Dec 2009 15:03:30 +0000\nReceived: (qmail invoked by alias); 17 Dec 2009 15:03:09 -0000\nReceived: from deibp9eh1--blueice2n1.emea.ibm.com (EHLO [161.129.204.104]) [161.129.204.104]\n by mail.gmx.net (mp070) with SMTP; 17 Dec 2009 16:03:09 +0100\nX-Authenticated: #25330878\nX-Provags-ID: V01U2FsdGVkX1/jYsgssDvjloP52wh6NWNSp2lUhSlJQ/m3zMM3Mr\n\tO8kiHu547kdslJ\nMessage-ID: \nDate: Thu, 17 Dec 2009 16:03:09 +0100\nFrom: Thilo Goetz \nUser-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:161.129.204.104) Gecko/20091204 Thunderbird/3.0\nMIME-Version: 1.0\nTo: kavery@example.com\nSubject: Re: Parser Analysis Engines\nReferences: \nIn-Reply-To: \nX-Enigmail-Version: 1.0\nContent-Type: text/plain; charset=ISO-8859-15\nContent-Transfer-Encoding: 7bit\nX-Y-GMX-Trusted: 0\nX-FuHaFi: 0.64\nX-Virus-Checked: Checked by ClamAV on apache.org\n\nI had to moderate this message through. Please subscribe\nto the mailing list if you want to post. Thanks.\n\nOn 12/17/2009 15:13, Sven Hesselbach wrote:\n> Hello,\n> \n> I'm currently working on my masters thesis about (natural language)\n> parsing technology.\n> I'd like to integrate and test different existing Parser AEs in an UIMA\n> based NLP pipeline.\n> I've already found several implementations, such as JulieLab's OpenNLP\n> and MST Parser Wrapper or\n> the Enju Parser (found at http://u-compare.org/). Despite of intensive\n> searching I unfortunately\n> couldn't find additional Parser AEs.\n> \n> Does anyone know about other Parser Analysis Engines (e.g. Stanford\n> Parser, Malt Parser)?\n> \n> \n> Thank you,\n> \n> Sven\n> \n> \n> \n> \n\nFrom uima-user-returnkavery@example.com Thu Dec 17 20:15:01 2009\nReturn-Path: \nDelivered-To: kavery@example.com\nReceived: (qmail 89349 invoked from network); 17 Dec 2009 20:15:01 -0000\nReceived: from hermes.apache.org (HELO mail.apache.org) (161.129.204.104)\n by minotaur.apache.org with SMTP; 17 Dec 2009 20:15:01 -0000\nReceived: (qmail 78292 invoked by uid 500); 17 Dec 2009 20:15:01 -0000\nDelivered-To: kavery@example.com\nReceived: (qmail 78205 invoked by uid 500); 17 Dec 2009 20:15:00 -0000\nMailing-List: contact kavery@example.com; run by ezmlm\nPrecedence: bulk\nList-Help: \nList-Unsubscribe: \nList-Post: \nList-Id: