Is it possible to add DB result set to WORDLIST instead of reading from file

[roopa ts]

Is there a way to add data from List to WORDLIST instead of reading from file 
in UIMA_RUTA ?
As I am reading data from database and  I want to my result list to be Added to 
WORDLIST .
Could please help me .
 
Thanks in advance.

Re: DUCC Web Server Service Visibility and Default Reservations

[Osborne, John David (Campus)]

Thanks Burn, looks like it is deployed but not healthy due to a refused RMI 
connection. The web services page is refreshed, in addition to displaying no 
services it does not display values for some other fields (Updated, 
Utilization) that are displayed on other web server pages.

Any info appreciated, I'm not seeing anything more in sm.log than I am seeing 
here from the ducc_services --query I ran. Both of the lines end at the number 
38 for the MetaPid.

 -John


[X]


Service: UIMA-AS:MRN_Document_Pull_Queue:tcp://localhost:61617
   Service Class : Registered as ID 33 Owner[ducc] instances[1] 
linger[30]
   Implementors  : 31.0
   References: None
   Dependencies  : none
   Service State : Available
   Ping Active   : true
   Start Mode: manual, Enabled
   Last Use  : N/A
   Last Ping : Wed Jul 19 15:02:54 CDT 2017
   Last Runnable : Wed Jul 19 15:03:18 CDT 2017
   Registration Date : Tue Jul 18 14:55:18 CDT 2017
   Service Statistics:
   Alive[true] Healthy[false] + Info: JMX Failure[Failed to retrieve 
RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is 
java.rmi.ConnectException: Connection refused to host: localhost; nested 
exception is:
java.net.ConnectException: Connection refused (Connection refused)]]] 
MetaNode[10.23.142.165] MetaPid[1988:38



From: Burn Lewis 
Sent: Wednesday, July 19, 2017 2:50:18 PM
To: user@uima.apache.org
Subject: Re: DUCC Web Server Service Visibility and Default Reservations

Did you refresh the Services page?  Ensure that the Users field is empty
(except for the hint)?  Also try $DUCC_HOME/bin/ducc_services --query

Reservations made by the "System" user are for internal use.

~Burn

On Wed, Jul 19, 2017 at 3:21 PM, Lou DeGenaro 
wrote:

> It should always be the case that if you successfully "ducc_services
> --register..." a service it should appear on the ducc-mon Services page.
> When you click on the Id for a Service you should see zero of more
> deployments, each Running instance corresponding to an O/S process.
>
> If you ever want to run DUCC Jobs you need to have the JobDriver
> Reservation.
>
> Lou.
>
> On Wed, Jul 19, 2017 at 11:53 AM, Osborne, John David (Campus) <
> ozb...@uab.edu> wrote:
>
> > I have (according the log files in $HOME/ducc/logs) started as registered
> > service successfully via ducc_services. I can see the process running via
> > the ps command, but it does not appear in the webserver under the
> services
> > section. Is this because I am running ducc anonymously using
> > active-ducc-unsecure.xml? I did not implement a pinger for this service,
> > but I assume that since it is an AS service a default pinger will be
> > provided for me. I'm guessing only services with pingers appear in the
> > service page on the ducc webserver...?
> >
> > I also noticed a reservation in DUCC, dating back to when I first
> > installed DUCC with an ID of 0. It is of class JobDriver, from the system
> > user, is in the state Assigned with 0 user processes and does not have
> the
> > option for termination. Is this some reservation I created errorenously
> or
> > is this standard on all ducc systems? I would like to cancel it if I
> don't
> > need it, it taking up 2 GBS of memory.
> >
> > Thanks for any help,
> >
> > -John
> >
>

Re: DUCC Web Server Service Visibility and Default Reservations

[Burn Lewis]

Did you refresh the Services page?  Ensure that the Users field is empty
(except for the hint)?  Also try $DUCC_HOME/bin/ducc_services --query

Reservations made by the "System" user are for internal use.

~Burn

On Wed, Jul 19, 2017 at 3:21 PM, Lou DeGenaro 
wrote:

> It should always be the case that if you successfully "ducc_services
> --register..." a service it should appear on the ducc-mon Services page.
> When you click on the Id for a Service you should see zero of more
> deployments, each Running instance corresponding to an O/S process.
>
> If you ever want to run DUCC Jobs you need to have the JobDriver
> Reservation.
>
> Lou.
>
> On Wed, Jul 19, 2017 at 11:53 AM, Osborne, John David (Campus) <
> ozb...@uab.edu> wrote:
>
> > I have (according the log files in $HOME/ducc/logs) started as registered
> > service successfully via ducc_services. I can see the process running via
> > the ps command, but it does not appear in the webserver under the
> services
> > section. Is this because I am running ducc anonymously using
> > active-ducc-unsecure.xml? I did not implement a pinger for this service,
> > but I assume that since it is an AS service a default pinger will be
> > provided for me. I'm guessing only services with pingers appear in the
> > service page on the ducc webserver...?
> >
> > I also noticed a reservation in DUCC, dating back to when I first
> > installed DUCC with an ID of 0. It is of class JobDriver, from the system
> > user, is in the state Assigned with 0 user processes and does not have
> the
> > option for termination. Is this some reservation I created errorenously
> or
> > is this standard on all ducc systems? I would like to cancel it if I
> don't
> > need it, it taking up 2 GBS of memory.
> >
> > Thanks for any help,
> >
> > -John
> >
>

Re: DUCC Web Server Service Visibility and Default Reservations

[Lou DeGenaro]

It should always be the case that if you successfully "ducc_services
--register..." a service it should appear on the ducc-mon Services page.
When you click on the Id for a Service you should see zero of more
deployments, each Running instance corresponding to an O/S process.

If you ever want to run DUCC Jobs you need to have the JobDriver
Reservation.

Lou.

On Wed, Jul 19, 2017 at 11:53 AM, Osborne, John David (Campus) <
ozb...@uab.edu> wrote:

> I have (according the log files in $HOME/ducc/logs) started as registered
> service successfully via ducc_services. I can see the process running via
> the ps command, but it does not appear in the webserver under the services
> section. Is this because I am running ducc anonymously using
> active-ducc-unsecure.xml? I did not implement a pinger for this service,
> but I assume that since it is an AS service a default pinger will be
> provided for me. I'm guessing only services with pingers appear in the
> service page on the ducc webserver...?
>
> I also noticed a reservation in DUCC, dating back to when I first
> installed DUCC with an ID of 0. It is of class JobDriver, from the system
> user, is in the state Assigned with 0 user processes and does not have the
> option for termination. Is this some reservation I created errorenously or
> is this standard on all ducc systems? I would like to cancel it if I don't
> need it, it taking up 2 GBS of memory.
>
> Thanks for any help,
>
> -John
>

Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?

[Jaroslaw Cwiklik]

Your application should not be calling connectionOpen() to test the
connection. The uima-as client has been designed to recover from connection
loss automatically. It looks like this method was made public by mistake.
Your application should use UimaAsynchronousEngine interface instead to
access documented API. Looks like we need to better document this and also
provide a factory to enforce UIMA-AS client contract.

Can you retest your app without calling connectionOpen().

Regarding the timeouts, the client code is designed to create new temp
queue for every uima-as client instance when a connection is recovered.
Need to do more testing to see if there is a bug in the code that deals
with recovery.

Jerry

On Wed, Jul 19, 2017 at 1:52 PM, nelson rivera 
wrote:

> Exactly, only one instance of all clients works after the broker is
> restarted. I don't know if this first client recovered and included
> correct temp queue for replie, what I do see is that this first client
> in my source code return "false" to the method connectionOpen()" and
> because of that, i initializes the client again (uimaEEEngine = new
> BaseUIMAAsynchronousEngine_impl() and
> uimaEEEngine.initialize(appCtx);).
>
> The rest of the clients return "true" to the method connectionOpen()
> because of that, i don't initializes again.
>
> The following logs are of one of the client failed, the first time
> that is initialized, processing the first request and  before the
> broker is stopped and restarted
>
> INFORMACIÓN: UIMA Version 2.9.0 UIMA-AS Version 2.9.1
> jul 19, 2017 1:31:32 PM
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
> initializeProducer
> INFORMACIÓN: Initializing JMS Message Producer. Broker:
> tcp://172.24.10.193:61616 Queue Name: XCharsetDetector
> jul 19, 2017 1:31:32 PM
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
> initializeConsumer
> INFORMACIÓN: Initializing JMS Message Consumer. Broker:
> tcp://172.24.10.193:61616 Queue Name:
> ID:nelson-XPS-8700-39640-1500485371575-1:1:2
> jul 19, 2017 1:31:32 PM
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
> initialize
> INFORMACIÓN: Asynchronous Client Has Been Initialized. Serialization
> Strategy: [SerializationStrategy] Ready To Process.
> jul 19, 2017 1:31:32 PM
> org.rp.platform.charset.business.CharsetBusiness
> getProcessingCharsetDetector
> INFORMACIÓN: Clase encargada de la detección de charset
> CharsetDetectorRemoteUIMAProcessing
> jul 19, 2017 1:32:54 PM
> org.rp.platform.charset.uima.CharsetDetectorRemoteUIMAProcessing
> process
> INFORMACIÓN: Inicio de procesamiento en detección de charset.
> jul 19, 2017 1:32:54 PM
> cu.datys.xinetica.uima.listener.StatusCalbackListenerPerformance
> onBeforeProcessCAS
> INFORMACIÓN: null
> jul 19, 2017 1:32:54 PM
> org.rp.platform.charset.uima.CharsetDetectorRemoteUIMAProcessing
> process
> INFORMACIÓN: Fin de procesamiento en detección de charset
>
>
>
>
> And this following logs are of the uima-as service that corresponds to
> the client, after the broker is stopped and processing the second
> request
>
> 01:34:43.215 - 27:
> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.
> handleListenerSetupFailure:
> WARNING: Uima AS Service:XCharsetDetector Listener Recovered
> Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again
> 01:34:43.255 - 25:
> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.
> handleListenerSetupFailure:
> WARNING: Uima AS Service:XCharsetDetector Listener Recovered
> Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again
> 01:38:50.709 - 1191:
> org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
> WARNING: Controller: XCharsetDetector Failed To Send Message to
> Delegates  Queue: null
> 01:38:50.710 - 17:
> org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
> Entrando al process
> 01:38:50.710 - 17:
> org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
> XCharsetDetector::Encontrado el objecto para detectar charset...
> 01:38:50.715 - 1191:
> org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.
> UimaAsAsyncCallbackListener.onException():
> INFO: Service:XCharsetDetector JMS unable to Deliver
> CAS:6e78005b:15d5be5c629:-7ff6 -
> Error:temp-queue://ID:nelson-XPS-8700-39640-1500485371575-1:1:2
> 01:38:50.715 - 1191:
> org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.
> UimaAsAsyncCallbackListener.onException():
> INFO: Controller: XCharsetDetector Handling Release CAS Request.
> Releasing CAS Reference Id: 6e78005b:15d5be5c629:-7ff6
>
>
> 2017-07-19 9:12 GMT-04:00, Jaroslaw Cwiklik :
> > Hi, can you include part of a client logging just before the broker is
> > stopped and restarted until timeouts start. When a connection is
> recovered,
> > the client creates a new temp queue and includes it in an outgoing
> messages
> > to services so that 

Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?

[nelson rivera]

Exactly, only one instance of all clients works after the broker is
restarted. I don't know if this first client recovered and included
correct temp queue for replie, what I do see is that this first client
in my source code return "false" to the method connectionOpen()" and
because of that, i initializes the client again (uimaEEEngine = new
BaseUIMAAsynchronousEngine_impl() and
uimaEEEngine.initialize(appCtx);).

The rest of the clients return "true" to the method connectionOpen()
because of that, i don't initializes again.

The following logs are of one of the client failed, the first time
that is initialized, processing the first request and  before the
broker is stopped and restarted

INFORMACIÓN: UIMA Version 2.9.0 UIMA-AS Version 2.9.1
jul 19, 2017 1:31:32 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeProducer
INFORMACIÓN: Initializing JMS Message Producer. Broker:
tcp://172.24.10.193:61616 Queue Name: XCharsetDetector
jul 19, 2017 1:31:32 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initializeConsumer
INFORMACIÓN: Initializing JMS Message Consumer. Broker:
tcp://172.24.10.193:61616 Queue Name:
ID:nelson-XPS-8700-39640-1500485371575-1:1:2
jul 19, 2017 1:31:32 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl
initialize
INFORMACIÓN: Asynchronous Client Has Been Initialized. Serialization
Strategy: [SerializationStrategy] Ready To Process.
jul 19, 2017 1:31:32 PM
org.rp.platform.charset.business.CharsetBusiness
getProcessingCharsetDetector
INFORMACIÓN: Clase encargada de la detección de charset
CharsetDetectorRemoteUIMAProcessing
jul 19, 2017 1:32:54 PM
org.rp.platform.charset.uima.CharsetDetectorRemoteUIMAProcessing
process
INFORMACIÓN: Inicio de procesamiento en detección de charset.
jul 19, 2017 1:32:54 PM
cu.datys.xinetica.uima.listener.StatusCalbackListenerPerformance
onBeforeProcessCAS
INFORMACIÓN: null
jul 19, 2017 1:32:54 PM
org.rp.platform.charset.uima.CharsetDetectorRemoteUIMAProcessing
process
INFORMACIÓN: Fin de procesamiento en detección de charset




And this following logs are of the uima-as service that corresponds to
the client, after the broker is stopped and processing the second
request

01:34:43.215 - 27:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure:
WARNING: Uima AS Service:XCharsetDetector Listener Recovered
Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again
01:34:43.255 - 25:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure:
WARNING: Uima AS Service:XCharsetDetector Listener Recovered
Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again
01:38:50.709 - 1191:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
WARNING: Controller: XCharsetDetector Failed To Send Message to
Delegates  Queue: null
01:38:50.710 - 17:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
Entrando al process
01:38:50.710 - 17:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
XCharsetDetector::Encontrado el objecto para detectar charset...
01:38:50.715 - 1191:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Service:XCharsetDetector JMS unable to Deliver
CAS:6e78005b:15d5be5c629:-7ff6 -
Error:temp-queue://ID:nelson-XPS-8700-39640-1500485371575-1:1:2
01:38:50.715 - 1191:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XCharsetDetector Handling Release CAS Request.
Releasing CAS Reference Id: 6e78005b:15d5be5c629:-7ff6


2017-07-19 9:12 GMT-04:00, Jaroslaw Cwiklik :
> Hi, can you include part of a client logging just before the broker is
> stopped and restarted until timeouts start. When a connection is recovered,
> the client creates a new temp queue and includes it in an outgoing messages
> to services so that replies can come back. Seems like the client outgoing
> messages contain a reference to an old temp queue which explain the
> timeouts. You say you have multiple clients in your app and only one
> instance works after the broker is restarted. The rest of the clients
> continuously fail after the broker restart (true?). All UIMA-AS clients
> share the same broker connection so the question is why only one of the
> clients recovered and included correct temp queue for replies and the
> others did not. Can yo confirm that you keep sending messages from your
> clients and only one of them succeeds with send and receive.
>
> Jerry
>
> On Tue, Jul 18, 2017 at 4:09 PM, nelson rivera 
> wrote:
>
>> i just tested the snapshot build from
>> https://svn.apache.org/repos/asf/uima/uima-as/trunk, i continue using
>> 8 service uima-as remote, 2 are used only for
>> aggregates services, and created 6 uima-as client instances in my
>> client application general.
>>

DUCC Web Server Service Visibility and Default Reservations

[Osborne, John David (Campus)]

I have (according the log files in $HOME/ducc/logs) started as registered 
service successfully via ducc_services. I can see the process running via the 
ps command, but it does not appear in the webserver under the services section. 
Is this because I am running ducc anonymously using active-ducc-unsecure.xml? I 
did not implement a pinger for this service, but I assume that since it is an 
AS service a default pinger will be provided for me. I'm guessing only services 
with pingers appear in the service page on the ducc webserver...?

I also noticed a reservation in DUCC, dating back to when I first installed 
DUCC with an ID of 0. It is of class JobDriver, from the system user, is in the 
state Assigned with 0 user processes and does not have the option for 
termination. Is this some reservation I created errorenously or is this 
standard on all ducc systems? I would like to cancel it if I don't need it, it 
taking up 2 GBS of memory.

Thanks for any help,

-John

Re: DUCC Security Model for Service Deployment

[Jaroslaw Cwiklik]

John, you can use the broker shipped with UIMA-AS installation for your
services.

Jerry

On Wed, Jul 19, 2017 at 10:55 AM, Osborne, John David (Campus) <
ozb...@uab.edu> wrote:

> Jerry, my services would span across multiple jobs so a service model is
> preferable for me.
>
> With regards to a secondary broker - I'm thinking to use a UIMA-AS
> installation on the same machine rather than download the full Apache AMQ
> runtime standalone. I'm worried about potential compatibility issues
> between DUCC broker and downloaded broker (unfounded concern?) and I am
> unfamiliar with AMQ in isolation.  It should also allow for comparison
> between AS and DUCC. Is this a reasonable approach?
>
> Thanks for all your help so far,
>
>  -John
>
>
> -Original Message-
> From: uim...@gmail.com [mailto:uim...@gmail.com] On Behalf Of Jaroslaw
> Cwiklik
> Sent: Tuesday, July 18, 2017 3:40 PM
> To: user@uima.apache.org
> Subject: Re: DUCC Security Model for Service Deployment
>
> John, services are typically long running and independent of jobs. They
> provide a specific function and may take a long time to initialize. They
> are meant to be reusable across multiple jobs. If your analytics are fast
> initializing and not meant to be shared you can just use jobs.
>
> We should probably modify the documentation to talk about recommending a
> secondary broker for services. My recommendation is to download and install
> the full AMQ runtime for your services. DUCC only bundles essential parts
> of AMQ distro.
>
> You decide about how secure your DUCC should be. We lock DUCC's broker by
> default to protect it from a malicious user code. If this is not your
> concern you can use DUCC's broker if you want. Keep in mind that if you use
> DUCC's broker for services its load will increase and if this is high
> enough it may effect how DUCC responds. Another benefit of having a
> secondary broker is that you can keep your services up while DUCC is being
> shutdown for update or maintenance. This is especially important if your
> services take hours to initialize.
>
> Jerry
>
> On Tue, Jul 18, 2017 at 4:07 PM, Osborne, John David (Campus) <
> ozb...@uab.edu> wrote:
>
> > Thanks Jerry!
> >
> > I can run it using the insecure option (just tried it - works great!)
> > - the broker port is closed to all but localhost as another
> > application feeds requests to DUCC. From a non-security operational
> > point of few though I am violating your recommendation to use a
> > secondary broker... I hope this won't get me into too much trouble...
> >
> > From the documentation, I had no idea there was a need for a secondary
> > broker to run services. If I wanted to do this, is this something that
> > can be set up in the current ducc distribution or would it be better
> > to go ahead and run my legacy services independently? To do this,  I'm
> > presuming I would instantiate a secondary broker (presumably still
> > 61616) but submit the deployment descriptor to the DUCC broker (61617)
> > but with the inputQueue brokerURL pointing to the secondary (61616)
> broker?
> >
> > I was hoping to make a clean migration to DUCC - maybe it would be
> > easier to get rid of services altogether and just submit jobs? Is this
> > the current trend or are a lot of folks running secondary brokers and
> services?
> >
> >  -John
> >
> >
> >
> > -Original Message-
> > From: uim...@gmail.com [mailto:uim...@gmail.com] On Behalf Of Jaroslaw
> > Cwiklik
> > Sent: Tuesday, July 18, 2017 2:19 PM
> > To: user@uima.apache.org
> > Subject: Re: DUCC Security Model for Service Deployment
> >
> > Hi, as Lou stated its recommended to use a secondary broker for
> > services to keep this separate from a DUCC broker. The DUCC broker is
> > protected by default as it is used for internal communication.
> >
> > If you want to run without broker credentials change this setting in
> > default.ducc.properties
> >
> > ducc.broker.configuration = conf/activemq-ducc-unsecure.xml
> >
> > Jerry
> >
> >
> >
> > On Tue, Jul 18, 2017 at 3:05 PM, Osborne, John David (Campus) <
> > ozb...@uab.edu> wrote:
> >
> > > Thanks Lou,
> > >
> > > I'm still not totally following.
> > >
> > > In UIMA-AS, I could deploy services (as the administrator) using:
> > > deployAsyncService.sh $SOME_DEPLOYMENT_DESCRIPTOR $BROKER_URL
> > >
> > > I thought the equivalent in DUCC was (for example):  ducc_services
> > > --register  --process_descriptor $SOME_DEPLOYMENT_DESCRIPTOR
> > > --classpath $CLASSPATH --autostart true
> > >
> > > In the first case, I don't recall worrying about passwords - I
> > > presume deployAsyncService was privileged and knew any broker
> > > credentials. Are you saying the command line utility ducc_services
> > > is unaware of ducc-broker-credentionals.properties and there is no
> > > other way for the ducc user to pass these credentionals to the
> > > broker when registering/auto-start services?
> > >
> > > Sorry for the confusion, new to DUCC. I can see the
> > > 

RE: DUCC Security Model for Service Deployment

[Osborne, John David (Campus)]

Jerry, my services would span across multiple jobs so a service model is 
preferable for me.

With regards to a secondary broker - I'm thinking to use a UIMA-AS installation 
on the same machine rather than download the full Apache AMQ runtime 
standalone. I'm worried about potential compatibility issues between DUCC 
broker and downloaded broker (unfounded concern?) and I am unfamiliar with AMQ 
in isolation.  It should also allow for comparison between AS and DUCC. Is this 
a reasonable approach? 

Thanks for all your help so far,

 -John


-Original Message-
From: uim...@gmail.com [mailto:uim...@gmail.com] On Behalf Of Jaroslaw Cwiklik
Sent: Tuesday, July 18, 2017 3:40 PM
To: user@uima.apache.org
Subject: Re: DUCC Security Model for Service Deployment

John, services are typically long running and independent of jobs. They provide 
a specific function and may take a long time to initialize. They are meant to 
be reusable across multiple jobs. If your analytics are fast initializing and 
not meant to be shared you can just use jobs.

We should probably modify the documentation to talk about recommending a 
secondary broker for services. My recommendation is to download and install the 
full AMQ runtime for your services. DUCC only bundles essential parts of AMQ 
distro.

You decide about how secure your DUCC should be. We lock DUCC's broker by 
default to protect it from a malicious user code. If this is not your concern 
you can use DUCC's broker if you want. Keep in mind that if you use DUCC's 
broker for services its load will increase and if this is high enough it may 
effect how DUCC responds. Another benefit of having a secondary broker is that 
you can keep your services up while DUCC is being shutdown for update or 
maintenance. This is especially important if your services take hours to 
initialize.

Jerry

On Tue, Jul 18, 2017 at 4:07 PM, Osborne, John David (Campus) < ozb...@uab.edu> 
wrote:

> Thanks Jerry!
>
> I can run it using the insecure option (just tried it - works great!) 
> - the broker port is closed to all but localhost as another 
> application feeds requests to DUCC. From a non-security operational 
> point of few though I am violating your recommendation to use a 
> secondary broker... I hope this won't get me into too much trouble...
>
> From the documentation, I had no idea there was a need for a secondary 
> broker to run services. If I wanted to do this, is this something that 
> can be set up in the current ducc distribution or would it be better 
> to go ahead and run my legacy services independently? To do this,  I'm 
> presuming I would instantiate a secondary broker (presumably still 
> 61616) but submit the deployment descriptor to the DUCC broker (61617) 
> but with the inputQueue brokerURL pointing to the secondary (61616) broker?
>
> I was hoping to make a clean migration to DUCC - maybe it would be 
> easier to get rid of services altogether and just submit jobs? Is this 
> the current trend or are a lot of folks running secondary brokers and 
> services?
>
>  -John
>
>
>
> -Original Message-
> From: uim...@gmail.com [mailto:uim...@gmail.com] On Behalf Of Jaroslaw 
> Cwiklik
> Sent: Tuesday, July 18, 2017 2:19 PM
> To: user@uima.apache.org
> Subject: Re: DUCC Security Model for Service Deployment
>
> Hi, as Lou stated its recommended to use a secondary broker for 
> services to keep this separate from a DUCC broker. The DUCC broker is 
> protected by default as it is used for internal communication.
>
> If you want to run without broker credentials change this setting in 
> default.ducc.properties
>
> ducc.broker.configuration = conf/activemq-ducc-unsecure.xml
>
> Jerry
>
>
>
> On Tue, Jul 18, 2017 at 3:05 PM, Osborne, John David (Campus) < 
> ozb...@uab.edu> wrote:
>
> > Thanks Lou,
> >
> > I'm still not totally following.
> >
> > In UIMA-AS, I could deploy services (as the administrator) using:
> > deployAsyncService.sh $SOME_DEPLOYMENT_DESCRIPTOR $BROKER_URL
> >
> > I thought the equivalent in DUCC was (for example):  ducc_services 
> > --register  --process_descriptor $SOME_DEPLOYMENT_DESCRIPTOR 
> > --classpath $CLASSPATH --autostart true
> >
> > In the first case, I don't recall worrying about passwords - I 
> > presume deployAsyncService was privileged and knew any broker 
> > credentials. Are you saying the command line utility ducc_services 
> > is unaware of ducc-broker-credentionals.properties and there is no 
> > other way for the ducc user to pass these credentionals to the 
> > broker when registering/auto-start services?
> >
> > Sorry for the confusion, new to DUCC. I can see the 
> > $DUCC_HOME/resources.private/ducc-broker-credentials.properties - I 
> > just don't know how to use them when deploying (same thing as 
> > registering and
> > starting?) a service.
> >
> >  -John
> >
> >
> >
> > -Original Message-
> > From: Lou DeGenaro [mailto:lou.degen...@gmail.com]
> > Sent: Tuesday, July 18, 2017 1:34 PM
> > To: 

Re: JCasGenMojo.newError(JCasGenMojo.java:239)

[Marshall Schor]

:-) -Marshall


On 7/17/2017 8:14 AM, Luca Toldo wrote:
> by upgrading to version 2.10 of the UIMA framework the error message 
> disappeared and instead I got a clear instruction on what is conflicting.
>
> Thank you !
>

Re: How know when "Session is closed" after establish connections between uima-as client and ActiveMQ?

[Jaroslaw Cwiklik]

Hi, can you include part of a client logging just before the broker is
stopped and restarted until timeouts start. When a connection is recovered,
the client creates a new temp queue and includes it in an outgoing messages
to services so that replies can come back. Seems like the client outgoing
messages contain a reference to an old temp queue which explain the
timeouts. You say you have multiple clients in your app and only one
instance works after the broker is restarted. The rest of the clients
continuously fail after the broker restart (true?). All UIMA-AS clients
share the same broker connection so the question is why only one of the
clients recovered and included correct temp queue for replies and the
others did not. Can yo confirm that you keep sending messages from your
clients and only one of them succeeds with send and receive.

Jerry

On Tue, Jul 18, 2017 at 4:09 PM, nelson rivera 
wrote:

> i just tested the snapshot build from
> https://svn.apache.org/repos/asf/uima/uima-as/trunk, i continue using
> 8 service uima-as remote, 2 are used only for
> aggregates services, and created 6 uima-as client instances in my
> client application general.
>
> Now the behavior is the follow:
>
> After restart the broker, the first uima-as client that is consumed
> (no matter which),
> has a correct behavior, the instruccion to uima-as client
> "BaseUIMAAsynchronousEngine_impl.connectionOpen()" return "false" and
> correctly initializes the client again and process the request.
>
> All next uima-as client to consume returns "true" to the instruccion
> "BaseUIMAAsynchronousEngine_impl.connectionOpen()", send the request,
> and then the uima-as service process the request but after shows lines
> similar to this in the log
>
> 03:24:52.338 - 1283:
> org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.
> UimaAsAsyncCallbackListener.onException():
> INFO: Service:XCharsetDetector JMS unable to Deliver
> CAS:46623412:15d57234659:-7fea -
> Error:temp-queue://ID:nelson-XPS-8700-40232-1500405516005-1:1:5
> 03:24:52.338 - 1283:
> org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.
> UimaAsAsyncCallbackListener.onException():
> INFO: Controller: XCharsetDetector Handling Release CAS Request.
> Releasing CAS Reference Id: 46623412:15d57234659:-7fea
>
>
> and then in my mechanism de timeout in client side, after 10 seconds
> without get any notification  on onBeforeProcessCAS() metod of uima-as
> client's UimaAsBaseCallbackListener y throws timeout exception.
>
>
>
>
>
> 2017-07-17 13:37 GMT-04:00, Jaroslaw Cwiklik :
> > Yes. the changes are in the svn so you prefer building from source just
> do
> > svn update to pickup the latest code.
> >
> > Jerry
> >
> > On Mon, Jul 17, 2017 at 1:18 PM, nelson rivera  >
> > wrote:
> >
> >> Sorry for the delay, I took holidays days, i will test the snapshot very
> >> now.
> >>
> >> I can build the snapshot from
> >> https://svn.apache.org/repos/asf/uima/uima-as/trunk?, the change is
> >> there?
> >>
> >> 2017-07-14 9:28 GMT-04:00, Jaroslaw Cwiklik :
> >> > Hi, please download a new snapshot
> >> >
> >> > https://repository.apache.org/content/repositories/
> >> snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/uima-
> >> as-2.9.1-20170714.131835-3.tgz
> >> > or
> >> > https://repository.apache.org/content/repositories/
> >> snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/uima-
> >> as-2.9.1-20170714.131915-4.zip
> >> >
> >> > You can check signatures of the above here:
> >> > https://repository.apache.org/content/repositories/
> >> snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/
> >> >
> >> > uima-as-2.9.1-20170714.131835-3.tgz.md5
> >> > uima-as-2.9.1-20170714.131835-3.tgz.sha1
> >> >
> >> > uima-as-2.9.1-20170714.131915-4.zip.md5
> >> > uima-as-2.9.1-20170714.131915-4.zip.sha1
> >> >
> >> >
> >> >
> >> > On Tue, Jul 11, 2017 at 10:17 AM, nelson rivera <
> >> nelsonriver...@gmail.com>
> >> > wrote:
> >> >
> >> >> Thanks very much, actually i have my application in production but
> >> >> with this bug as reported. i wait
> >> >>
> >> >> 2017-07-11 9:59 GMT-04:00, Jaroslaw Cwiklik :
> >> >> > Hi, I am investigating this issue now. Are you having this problem
> >> >> > in
> >> >> > production or testing? The multi-client recovery is quite
> >> >> > complicated
> >> >> > and
> >> >> > subject to race conditions. I need to first re-create the problem
> >> >> > and
> >> >> work
> >> >> > on a solution if this in fact is a bug. From what you sent it looks
> >> >> > like
> >> >> > there is a bug in client recovery. This may take some time to sort
> >> out.
> >> >> > Will let you know what I find.
> >> >> >
> >> >> > Jerry
> >> >> >
> >> >> > On Tue, Jul 11, 2017 at 9:02 AM, nelson rivera
> >> >> >  >> >> >
> >> >> > wrote:
> >> >> >
> >> >> >> analyzing more deep the issue, I have observed that after restart
> >> >> >> the
> >>