Return-Path: 
 <uima-user-return-2706-apmail-incubator-uima-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-uima-user-archive@minotaur.apache.org
Received: (qmail 21250 invoked from network); 4 Dec 2009 00:53:26 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 4 Dec 2009 00:53:26 -0000
Received: (qmail 69003 invoked by uid 500); 4 Dec 2009 00:53:26 -0000
Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org
Received: (qmail 68913 invoked by uid 500); 4 Dec 2009 00:53:24 -0000
Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:uima-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:uima-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:uima-user@incubator.apache.org>
List-Id: <uima-user.incubator.apache.org>
Reply-To: uima-user@incubator.apache.org
Delivered-To: mailing list uima-user@incubator.apache.org
Received: (qmail 68903 invoked by uid 99); 4 Dec 2009 00:53:24 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2009 00:53:24 +0000
X-ASF-Spam-Status: No, hits=-2.6 required=5.0
	tests=BAYES_00
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of gcaug-uima-user@m.gmane.org
 designates 80.91.229.12 as permitted sender)
Received: from [80.91.229.12] (HELO lo.gmane.org) (80.91.229.12)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2009 00:53:20 +0000
Received: from list by lo.gmane.org with local (Exim 4.50)
	id 1NGMPp-0005uf-1g
	for uima-user@incubator.apache.org; Fri, 04 Dec 2009 01:52:57 +0100
Received: from eth3395.vic.adsl.internode.on.net ([59.167.195.66])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <uima-user@incubator.apache.org>; Fri, 04 Dec 2009 01:52:57 +0100
Received: from hansen.candrawinata by eth3395.vic.adsl.internode.on.net with
 local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <uima-user@incubator.apache.org>; Fri, 04 Dec 2009 01:52:57 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: uima-user@incubator.apache.org
From: Hansen Candrawinata <hansen.candrawinata@gmail.com>
Subject: Re: Exception thrown when deploying CAS Processors in managed mode
Date: Fri, 4 Dec 2009 00:52:33 +0000 (UTC)
Lines: 99
Message-ID: <loom.20091204T005643-944@post.gmane.org>
References: <loom.20091203T070748-358@post.gmane.org>
 <4B17D8E5.3090504@schor.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: sea.gmane.org
User-Agent: Loom/3.14 (http://gmane.org/)
X-Loom-IP: 59.167.195.66 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5)
Sender: news <news@ger.gmane.org>

Hi Marshall,

Marshall Schor <msa@...> writes:
> In reading the documentation
>
(http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/references/references.html#ugr.ref.xml.cpe_descriptor.descriptor.cas_processors.individual
> ) it indicates that the "managed" mode (indicated by specifying "local"
> as the deployment option) requires that the "CAS Processor descriptor
> referenced in the |<descriptor>| element must be a Vinci /Service
> Deployment Descriptor/, which configures a CAS Processor for deployment
> as a Vinci service (see Section 3.6, "Working with Remote Services"
>
<http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tutorials_and_users_guides/tutorials_and_users_guides.html#ugr.tug.application.remote_services>
> in UIMA Tutorial and Developers' Guides)."
> 
> So, that I think is the source of the problem.

Thanks for replying.  Sorry, I missed that part of the documentation.  (I was
too eager to learn fast!)

However, I am still not able to deploy my CAS Processor in managed mode.  I
followed the instructions and changed the CAS Processor descriptor in my CPE
descriptor to be a Vinci service deployment descriptor and then run the CPE code
(cpe.process()), but my CAS Processor wasn't not called at all.  Instead, the
CPM seemed to be stuck for not being able to find the service port.  Here is the
snippet of the log messages:

04/12/2009 10:45:30 AM
org.apache.uima.collection.impl.cpm.container.deployer.vns.LocalVNS initialize
INFO: The CPM is about to test its VNS port 9005 for availability. (Thread Name:
BaseCPMImpl-Thread) 
04/12/2009 10:45:30 AM
org.apache.uima.collection.impl.cpm.container.deployer.vns.LocalVNS initialize
INFO: The service port 9005 is available on localhost. (Thread Name:
BaseCPMImpl-Thread) 
04/12/2009 10:45:30 AM
org.apache.uima.collection.impl.cpm.container.deployer.vns.LocalVNS initialize
INFO: The CPM VNS activity started on port 9005. (Thread Name: BaseCPMImpl-
Thread)
04/12/2009 10:45:30 AM
org.apache.uima.collection.impl.cpm.container.deployer.vns.LocalVNS process
INFO: The CPM VNS thread started. (Thread Name: VNS-Thread) VNS Port: 9005 
04/12/2009 10:45:30 AM
org.apache.uima.collection.impl.cpm.container.deployer.vinci.VinciCasProcessorDe
ployer
initialize
INFO: The next port  was retrieved from the service port queue. (Thread Name:
BaseCPMImpl-Thread)
04/12/2009 10:45:30 AM
org.apache.uima.collection.impl.cpm.container.deployer.vinci.VinciCasProcessorDe
ployer
initialize
INFO: The service port is not available yet. There are 5000 retries left to
acquire the port. (Thread Name: BaseCPMImpl-Thread) 
04/12/2009 10:45:31 AM
org.apache.uima.collection.impl.cpm.container.deployer.vinci.VinciCasProcessorDe
ployer
initialize
INFO: The service port is not available yet. There are 4999 retries left to
acquire the port. (Thread Name: BaseCPMImpl-Thread) 
04/12/2009 10:45:31 AM
org.apache.uima.collection.impl.cpm.container.deployer.vinci.VinciCasProcessorDe
ployer
initialize
INFO: The service port is not available yet. There are 4998 retries left to
acquire the port. (Thread Name: BaseCPMImpl-Thread) 
04/12/2009 10:45:31 AM
org.apache.uima.collection.impl.cpm.container.deployer.vinci.VinciCasProcessorDe
ployer
initialize
...

Perhaps I haven't really understood how Vinci works and how it should be used to
deploy a CAS processor in managed mode, so I would like to clarify a few things:
When deploying a CAS processor in managed mode, the corresponding CAS processor
descriptor in a CPE descriptor has to reference a Vinci Service Deployment
Descriptor.  Then, what is the next step?
a. Can I now run "cpe.process()"?  Or
b. I need to manually start the VNS with "startVNS.bat", deploy my CAS processor
as a Vinci service with "startVinciService.bat", and then run "cpe.process()"?

My understanding is it is (a) because a managed deployment mode means that the
CPE will use its internal VNS to start the CAS processor.  Is this correct?  But
as I said, when I tried (a) the CPE was stuck in a retry loop because of not
being able to find the service port (as shown by the log messages above).

In case it's relevant, here is my Vinci service descriptor referenced in the CPE
descriptor:

<deployment name="JOD and TIKA Annotator Service">
  <service name="JodAndTika" provider="vinci">
    <parameter name="resourceSpecifierPath"
value="H:\ttsrc\javasoe\documentconversion\desc\JodAndTika.xml"/>
    <parameter name="numInstances" value="1"/>
  </service>
</deployment>

Thanks,
Hansen