from:"nelson rivera"

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

2017-08-30 Thread nelson rivera

jerry , i tested the new snapshot of uima-as that you pushed into
apache snapshot repo to fix problem with the type priorities, and the
problem is solved. I tested with uima as service with priority
configuration in the aggregate's descriptor and every things is ok.
thanks for your quick attention

2017-08-25 16:47 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
> Nelson, I just pushed a new snapshot of uima-as to apache snapshot repo.
> This is a trunk level code not a release. Please deploy it and see if the
> problem with the type priorites is fixed. I did test it with a simple type
> priority configuration.
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/uima-as-2.9.1-20170825.204106-5.tar.gz
>
> Jerry
>
>
> On Fri, Aug 25, 2017 at 8:25 AM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> Thanks for your attention Jerry, i wait the solution to integrate it
>> in production
>>
>> 2017-08-24 14:27 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>> > Nelson, I was able to recreate this problem and am working on a fix
>> > now.
>> > Jerry
>> >
>> > On Wed, Aug 16, 2017 at 3:39 PM, nelson rivera
>> > <nelsonriver...@gmail.com
>> >
>> > wrote:
>> >
>> >> Jerry, i understand and wait. Thanks for your attention.
>> >>
>> >> 2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>> >> > Nelson, I need more time to look into this. Quite busy at a moment.
>> >> Unless
>> >> > someone else wants to jump in here I will address the problem when I
>> am
>> >> > done with current work load,
>> >> >
>> >> > Jerry
>> >> >
>> >> > On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik
>> >> > <cwik...@apache.org
>> >
>> >> > wrote:
>> >> >
>> >> >> Thanks, I will try to test this scenario and get back to ya.
>> >> >>
>> >> >> Jerry
>> >> >>
>> >> >> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera <
>> >> nelsonriver...@gmail.com>
>> >> >> wrote:
>> >> >>
>> >> >>> Yes, that is happening
>> >> >>>
>> >> >>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>> >> >>> > Please confirm that this is happening:
>> >> >>> >
>> >> >>> > 1) You deploy an aggregate and specify TypePriorities in
>> >> >>> > aggregate
>> >> >>> analysis
>> >> >>> > engine descriptor.
>> >> >>> > 2) After uima-as client initilizes, you call client's
>> >> >>> > public ProcessingResourceMetaData getMetaData();
>> >> >>> > 3) You check the returned meta and the type priorities are
>> >> >>> > missing
>> >> >>> >
>> >> >>> > You are observing correct behavior when you declare type
>> priorities
>> >> in
>> >> >>> > a delegate analysis engine descriptor of the aggregate
>> >> >>> >
>> >> >>> > Jerry
>> >> >>> >
>> >> >>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
>> >> >>> nelsonriver...@gmail.com>
>> >> >>> > wrote:
>> >> >>> >
>> >> >>> >> i have configured a priorityList in the descriptor of my
>> aggregate
>> >> >>> >> engine, with the objetive of use correctly subiterator()
>> >> >>> >> function
>> >> >>> >> in
>> >> >>> >> my client code over the result CAS.
>> >> >>> >>
>> >> >>> >> After deploy the aggregate in uima-as, in my client code that
>> >> >>> >> consumes
>> >> >>> >> de uima-as service aggregate to check the priorityList
>> >> >>> >> configured
>> >> >>> >> i
>> >> >>> >> use the instruccion
>> >> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and
>> not
>> >> >>> >> appear the priority configured. This does that the use of
>> >> subiterator
>> >> >>> >> not have the expected behavior in the uima-as client.
>> >> >>> >>
>> >> >>> >> If the configuration of priorityList is made in the descriptor
>> >> >>> >> of
>> >> one
>> >> >>> >> of the delegate of the aggregate, then if the instruccion
>> >> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in
>> >> client
>> >> >>> >> code shows the priorityList configured and then the  behavior
>> >> >>> >> is
>> >> >>> >> the
>> >> >>> >> expected.
>> >> >>> >>
>> >> >>> >
>> >> >>>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >
>>
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

2017-08-25 Thread nelson rivera

Thanks for your attention Jerry, i wait the solution to integrate it
in production

2017-08-24 14:27 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
> Nelson, I was able to recreate this problem and am working on a fix now.
> Jerry
>
> On Wed, Aug 16, 2017 at 3:39 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> Jerry, i understand and wait. Thanks for your attention.
>>
>> 2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>> > Nelson, I need more time to look into this. Quite busy at a moment.
>> Unless
>> > someone else wants to jump in here I will address the problem when I am
>> > done with current work load,
>> >
>> > Jerry
>> >
>> > On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik <cwik...@apache.org>
>> > wrote:
>> >
>> >> Thanks, I will try to test this scenario and get back to ya.
>> >>
>> >> Jerry
>> >>
>> >> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera <
>> nelsonriver...@gmail.com>
>> >> wrote:
>> >>
>> >>> Yes, that is happening
>> >>>
>> >>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>> >>> > Please confirm that this is happening:
>> >>> >
>> >>> > 1) You deploy an aggregate and specify TypePriorities in aggregate
>> >>> analysis
>> >>> > engine descriptor.
>> >>> > 2) After uima-as client initilizes, you call client's
>> >>> > public ProcessingResourceMetaData getMetaData();
>> >>> > 3) You check the returned meta and the type priorities are missing
>> >>> >
>> >>> > You are observing correct behavior when you declare type priorities
>> in
>> >>> > a delegate analysis engine descriptor of the aggregate
>> >>> >
>> >>> > Jerry
>> >>> >
>> >>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
>> >>> nelsonriver...@gmail.com>
>> >>> > wrote:
>> >>> >
>> >>> >> i have configured a priorityList in the descriptor of my aggregate
>> >>> >> engine, with the objetive of use correctly subiterator() function
>> >>> >> in
>> >>> >> my client code over the result CAS.
>> >>> >>
>> >>> >> After deploy the aggregate in uima-as, in my client code that
>> >>> >> consumes
>> >>> >> de uima-as service aggregate to check the priorityList configured
>> >>> >> i
>> >>> >> use the instruccion
>> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
>> >>> >> appear the priority configured. This does that the use of
>> subiterator
>> >>> >> not have the expected behavior in the uima-as client.
>> >>> >>
>> >>> >> If the configuration of priorityList is made in the descriptor of
>> one
>> >>> >> of the delegate of the aggregate, then if the instruccion
>> >>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in
>> client
>> >>> >> code shows the priorityList configured and then the  behavior is
>> >>> >> the
>> >>> >> expected.
>> >>> >>
>> >>> >
>> >>>
>> >>
>> >>
>> >
>>
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

2017-08-16 Thread nelson rivera

Jerry, i understand and wait. Thanks for your attention.

2017-08-16 15:09 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
> Nelson, I need more time to look into this. Quite busy at a moment. Unless
> someone else wants to jump in here I will address the problem when I am
> done with current work load,
>
> Jerry
>
> On Mon, Aug 14, 2017 at 4:36 PM, Jaroslaw Cwiklik <cwik...@apache.org>
> wrote:
>
>> Thanks, I will try to test this scenario and get back to ya.
>>
>> Jerry
>>
>> On Mon, Aug 14, 2017 at 4:27 PM, nelson rivera <nelsonriver...@gmail.com>
>> wrote:
>>
>>> Yes, that is happening
>>>
>>> 2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>>> > Please confirm that this is happening:
>>> >
>>> > 1) You deploy an aggregate and specify TypePriorities in aggregate
>>> analysis
>>> > engine descriptor.
>>> > 2) After uima-as client initilizes, you call client's
>>> > public ProcessingResourceMetaData getMetaData();
>>> > 3) You check the returned meta and the type priorities are missing
>>> >
>>> > You are observing correct behavior when you declare type priorities in
>>> > a delegate analysis engine descriptor of the aggregate
>>> >
>>> > Jerry
>>> >
>>> > On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <
>>> nelsonriver...@gmail.com>
>>> > wrote:
>>> >
>>> >> i have configured a priorityList in the descriptor of my aggregate
>>> >> engine, with the objetive of use correctly subiterator() function in
>>> >> my client code over the result CAS.
>>> >>
>>> >> After deploy the aggregate in uima-as, in my client code that
>>> >> consumes
>>> >> de uima-as service aggregate to check the priorityList configured i
>>> >> use the instruccion
>>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
>>> >> appear the priority configured. This does that the use of subiterator
>>> >> not have the expected behavior in the uima-as client.
>>> >>
>>> >> If the configuration of priorityList is made in the descriptor of one
>>> >> of the delegate of the aggregate, then if the instruccion
>>> >> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in client
>>> >> code shows the priorityList configured and then the  behavior is the
>>> >> expected.
>>> >>
>>> >
>>>
>>
>>
>

Re: TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

2017-08-14 Thread nelson rivera

Yes, that is happening

2017-08-14 15:40 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
> Please confirm that this is happening:
>
> 1) You deploy an aggregate and specify TypePriorities in aggregate analysis
> engine descriptor.
> 2) After uima-as client initilizes, you call client's
> public ProcessingResourceMetaData getMetaData();
> 3) You check the returned meta and the type priorities are missing
>
> You are observing correct behavior when you declare type priorities in
> a delegate analysis engine descriptor of the aggregate
>
> Jerry
>
> On Fri, Aug 11, 2017 at 12:12 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> i have configured a priorityList in the descriptor of my aggregate
>> engine, with the objetive of use correctly subiterator() function in
>> my client code over the result CAS.
>>
>> After deploy the aggregate in uima-as, in my client code that consumes
>> de uima-as service aggregate to check the priorityList configured i
>> use the instruccion
>> uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
>> appear the priority configured. This does that the use of subiterator
>> not have the expected behavior in the uima-as client.
>>
>> If the configuration of priorityList is made in the descriptor of one
>> of the delegate of the aggregate, then if the instruccion
>> uimaAsynchronousEngine.getMetaData().getTypePriorities()   in client
>> code shows the priorityList configured and then the  behavior is the
>> expected.
>>
>

TypePriorities configured in the descriptor of an aggregate engine are not added in uima-as

2017-08-11 Thread nelson rivera

i have configured a priorityList in the descriptor of my aggregate
engine, with the objetive of use correctly subiterator() function in
my client code over the result CAS.

After deploy the aggregate in uima-as, in my client code that consumes
de uima-as service aggregate to check the priorityList configured i
use the instruccion
uimaAsynchronousEngine.getMetaData().getTypePriorities(); and not
appear the priority configured. This does that the use of subiterator
not have the expected behavior in the uima-as client.

If the configuration of priorityList is made in the descriptor of one
of the delegate of the aggregate, then if the instruccion
uimaAsynchronousEngine.getMetaData().getTypePriorities()   in client
code shows the priorityList configured and then the  behavior is the
expected.

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

2017-07-20 Thread nelson rivera

)
at 
org.apache.uima.adapter.jms.client.ActiveMQMessageSender.createSession(ActiveMQMessageSender.java:119)
at 
org.apache.uima.adapter.jms.client.ActiveMQMessageSender.getMessageProducer(ActiveMQMessageSender.java:84)
at 
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.getMessageProducer(BaseUIMAAsynchronousEngine_impl.java:1268)
at 
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.handleProcessReplyFromCasMultiplier(BaseUIMAAsynchronousEngineCommon_impl.java:1519)
at 
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.handleProcessReply(BaseUIMAAsynchronousEngineCommon_impl.java:1485)
at 
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$2.run(BaseUIMAAsynchronousEngineCommon_impl.java:2079)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)

jul 20, 2017 3:12:09 PM
cu.datys.xinetica.uima.listener.StatusCalbackListenerPerformance
entityProcessComplete
INFORMACIÓN: null
Terminada ejecución de CAS original : 1c2940e4:15d6161f9a6:-7ff2



2017-07-19 14:22 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
> 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 <nelsonriver...@gmail.com>
> 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

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

2017-07-19 Thread 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 <cwik...@apache.org>:
> 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 <nelsonriver...@gmail.com>
> 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 use

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

2017-07-18 Thread nelson rivera

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 <cwik...@apache.org>:
> 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 <nelsonriver...@gmail.com>
> 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 <cwik...@apache.org>:
>> > 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 <cwik...@apache.org>:
>> >> > 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
>> >> > <nelsonriver...@gmail.com
>> >> >
>> >> > wrote:
>> >> >
>> >> >> analyzing more deep the issue, I have observed that 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

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

2017-07-17 Thread nelson rivera

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 <cwik...@apache.org>:
> 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 <cwik...@apache.org>:
>> > 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
>> > <nelsonriver...@gmail.com
>> >
>> > wrote:
>> >
>> >> analyzing more deep the issue, I have observed that 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()" and them get the
>> >> error:
>> >>
>> >> jul 11, 2017 8:11:52 AM
>> >> org.apache.uima.adapter.jms.client.ActiveMQMessageSender createSession
>> >> INFORMACIÓN: UIMA AS Client Failed Creating Session To Destination:
>> >> XCharsetDetector Managed By Broker: tcp://nelson-XPS-8700:61616
>> >> jul 11, 2017 8:11:52 AM
>> >> org.apache.uima.adapter.jms.client.ActiveMQMessageSender createSession
>> >> INFORMACIÓN: UIMA AS Client Connection To Destination:
>> >> XCharsetDetector Managed By Broker: tcp://nelson-XPS-8700:61616 Is
>> >> Closed
>> >> jul 11, 2017 8:11:52 AM
>> >> org.apache.uima.adapter.jms.client.ActiveMQMessageSender run
>> >> ADVERTENCIA:
>> >> org.apache.activemq.ConnectionClosedException: The connection is
>> already
>> >> closed
>> >> at org.apache.activemq.ActiveMQConnection.checkClosed(
>> >> ActiveMQConnection.java:1459)
>> >> at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(
>> >> ActiveMQConnection.java:1446)
>> >> at org.apache.activemq.ActiveMQConnection.createSession(
>> >> ActiveMQConnection.java:328)
>> >> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> >> createSession(ActiveMQMessageSender.java:108)
>> >> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> >> initializeProducer(ActiveMQMessageSender.java:143)
>> >> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> >> createTextMessage(ActiveMQMessageSender.java:191)
>> >> at org.apache.uima.adapter.jms.client.BaseMessageSender.run(
>> >> BaseMessageSender.java:330)
>> >> at java.lang.Thread.run(Thread.java:748)
>> >>
>> >> 2017-07-11 8:50 GMT-04:00, nelson rivera <nelsonriver...@gmail.com>:
>> >> > My client application not receive any exception in any time. I use
>> >> > both, in some uima-as client  use sendAndReceive() and in others use
>> >> >

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

2017-07-11 Thread nelson rivera

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 <cwik...@apache.org>:
> 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 <nelsonriver...@gmail.com>
> wrote:
>
>> analyzing more deep the issue, I have observed that 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()" and them get the
>> error:
>>
>> jul 11, 2017 8:11:52 AM
>> org.apache.uima.adapter.jms.client.ActiveMQMessageSender createSession
>> INFORMACIÓN: UIMA AS Client Failed Creating Session To Destination:
>> XCharsetDetector Managed By Broker: tcp://nelson-XPS-8700:61616
>> jul 11, 2017 8:11:52 AM
>> org.apache.uima.adapter.jms.client.ActiveMQMessageSender createSession
>> INFORMACIÓN: UIMA AS Client Connection To Destination:
>> XCharsetDetector Managed By Broker: tcp://nelson-XPS-8700:61616 Is
>> Closed
>> jul 11, 2017 8:11:52 AM
>> org.apache.uima.adapter.jms.client.ActiveMQMessageSender run
>> ADVERTENCIA:
>> org.apache.activemq.ConnectionClosedException: The connection is already
>> closed
>> at org.apache.activemq.ActiveMQConnection.checkClosed(
>> ActiveMQConnection.java:1459)
>> at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(
>> ActiveMQConnection.java:1446)
>> at org.apache.activemq.ActiveMQConnection.createSession(
>> ActiveMQConnection.java:328)
>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> createSession(ActiveMQMessageSender.java:108)
>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> initializeProducer(ActiveMQMessageSender.java:143)
>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> createTextMessage(ActiveMQMessageSender.java:191)
>> at org.apache.uima.adapter.jms.client.BaseMessageSender.run(
>> BaseMessageSender.java:330)
>> at java.lang.Thread.run(Thread.java:748)
>>
>> 2017-07-11 8:50 GMT-04:00, nelson rivera <nelsonriver...@gmail.com>:
>> > My client application not receive any exception in any time. I use
>> > both, in some uima-as client  use sendAndReceive() and in others use
>> > send(), each uima-as client has try-catch and none of them receive a
>> > exception, the following lines are printed in the console output,but
>> > the uima-as client is not notified and keeps waiting.
>> >
>> > 2017-07-10 16:48 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
>> >> it looks like the UIMA-AS client is setup to throw an exception back
>> >> to
>> >> the
>> >> application in this case. Did your application receive an exception?
>> >> Are
>> >> you using sendAndReceive() or send()? The UIMA-AS client rejects
>> requests
>> >> while a connection is down.
>> >>
>> >> Jerry
>> >>
>> >> On Mon, Jul 10, 2017 at 4:19 PM, Jaroslaw Cwiklik <cwik...@apache.org>
>> >> wrote:
>> >>
>> >>> Hmm, this is a different exception from Session closed. This time it
>> >>> is
>> >>> a
>> >>> Connection is closed. Seems like a race condition. How many UIMA-AS
>> >>> clients
>> >>> do you have running in this process?
>> >>>
>> >>> Jerry
>> >>>
>> >>> On Mon, Jul 10, 2017 at 3:51 PM, nelson rivera
>> >>> <nelsonriver...@gmail.com>
>> >>> wrote:
>> >>>
>> >>>> i just tested the snapshot build from
>> >>>> https://svn.apache.org/repos/asf/uima/uima-as/trunk, and the
>> >>>> behavior
>> >>&

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

2017-07-11 Thread nelson rivera

My client application not receive any exception in any time. I use
both, in some uima-as client  use sendAndReceive() and in others use
send(), each uima-as client has try-catch and none of them receive a
exception, the following lines are printed in the console output,but
the uima-as client is not notified and keeps waiting.

2017-07-10 16:48 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> it looks like the UIMA-AS client is setup to throw an exception back to the
> application in this case. Did your application receive an exception? Are
> you using sendAndReceive() or send()? The UIMA-AS client rejects requests
> while a connection is down.
>
> Jerry
>
> On Mon, Jul 10, 2017 at 4:19 PM, Jaroslaw Cwiklik <cwik...@apache.org>
> wrote:
>
>> Hmm, this is a different exception from Session closed. This time it is a
>> Connection is closed. Seems like a race condition. How many UIMA-AS
>> clients
>> do you have running in this process?
>>
>> Jerry
>>
>> On Mon, Jul 10, 2017 at 3:51 PM, nelson rivera <nelsonriver...@gmail.com>
>> wrote:
>>
>>> i just tested the snapshot build from
>>> https://svn.apache.org/repos/asf/uima/uima-as/trunk, and the behavior
>>> still are similar for many uima-as client, end in a exception, but now
>>> show this stacktrace:
>>>
>>> org.apache.activemq.ConnectionClosedException: The connection is already
>>> closed
>>> at org.apache.activemq.ActiveMQConnection.checkClosed(ActiveMQC
>>> onnection.java:1459)
>>> at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(A
>>> ctiveMQConnection.java:1446)
>>> at org.apache.activemq.ActiveMQConnection.createSession(ActiveM
>>> QConnection.java:328)
>>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.cre
>>> ateSession(ActiveMQMessageSender.java:108)
>>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.ini
>>> tializeProducer(ActiveMQMessageSender.java:143)
>>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.cre
>>> ateTextMessage(ActiveMQMessageSender.java:191)
>>> at org.apache.uima.adapter.jms.client.BaseMessageSender.run(Bas
>>> eMessageSender.java:330)
>>> at java.lang.Thread.run(Thread.java:748)
>>>
>>> 2017-07-07 15:33 GMT-04:00, nelson rivera <nelsonriver...@gmail.com>:
>>> > Sorry for the delay, i am building the framework from the source at
>>> > https://svn.apache.org/repos/asf/uima/uima-as/trunk, when test the
>>> > issue, i will comment the result.
>>> >
>>> > 2017-07-06 10:04 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>>> >> Hello, the snapshot binaries (zip + tar) are here:
>>> >>
>>> >> https://repository.apache.org/content/repositories/snapshots
>>> /org/apache/uima/uima-as/2.9.1-SNAPSHOT/
>>> >>
>>> >> Jerry
>>> >>
>>> >> On Thu, Jul 6, 2017 at 8:51 AM, Jaroslaw Cwiklik <cwik...@apache.org>
>>> >> wrote:
>>> >>
>>> >>> Hi, instructions how to build from source are here:
>>> >>> https://uima.apache.org/building-uima.html
>>> >>>
>>> >>> It's a bit involved process so I will try to post a snapshot of
>>> uima-as
>>> >>> to
>>> >>> Apache snapshot repository and will provide you with a link later
>>> today.
>>> >>>
>>> >>> Jerry
>>> >>>
>>> >>> On Wed, Jul 5, 2017 at 4:32 PM, nelson rivera <
>>> nelsonriver...@gmail.com>
>>> >>> wrote:
>>> >>>
>>> >>>> Please can you give me the url to source code with the changes, to
>>> >>>> test.
>>> >>>>
>>> >>>> 2017-07-05 16:19 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>>> >>>> > Just delivered a few changes to deal with a stale Session. Can
>>> >>>> > you
>>> >>>> > build
>>> >>>> > from source and test.
>>> >>>> > Jerry
>>> >>>> >
>>> >>>> > On Wed, Jul 5, 2017 at 2:21 PM, Jaroslaw Cwiklik <
>>> cwik...@apache.org>
>>> >>>> > wrote:
>>> >>>> >
>>> >>>> >> Thanks. Will check the code and work on a fix
>>> >&

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

2017-07-10 Thread nelson rivera

For this test i used 8 service uima-as remote, 2 are used only for
aggregates services, and created 6 uima-as client instances in my
client application general

2017-07-10 16:19 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
> Hmm, this is a different exception from Session closed. This time it is a
> Connection is closed. Seems like a race condition. How many UIMA-AS clients
> do you have running in this process?
>
> Jerry
>
> On Mon, Jul 10, 2017 at 3:51 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> i just tested the snapshot build from
>> https://svn.apache.org/repos/asf/uima/uima-as/trunk, and the behavior
>> still are similar for many uima-as client, end in a exception, but now
>> show this stacktrace:
>>
>> org.apache.activemq.ConnectionClosedException: The connection is already
>> closed
>> at org.apache.activemq.ActiveMQConnection.checkClosed(
>> ActiveMQConnection.java:1459)
>> at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(
>> ActiveMQConnection.java:1446)
>> at org.apache.activemq.ActiveMQConnection.createSession(
>> ActiveMQConnection.java:328)
>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> createSession(ActiveMQMessageSender.java:108)
>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> initializeProducer(ActiveMQMessageSender.java:143)
>> at org.apache.uima.adapter.jms.client.ActiveMQMessageSender.
>> createTextMessage(ActiveMQMessageSender.java:191)
>> at org.apache.uima.adapter.jms.client.BaseMessageSender.run(
>> BaseMessageSender.java:330)
>> at java.lang.Thread.run(Thread.java:748)
>>
>> 2017-07-07 15:33 GMT-04:00, nelson rivera <nelsonriver...@gmail.com>:
>> > Sorry for the delay, i am building the framework from the source at
>> > https://svn.apache.org/repos/asf/uima/uima-as/trunk, when test the
>> > issue, i will comment the result.
>> >
>> > 2017-07-06 10:04 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>> >> Hello, the snapshot binaries (zip + tar) are here:
>> >>
>> >> https://repository.apache.org/content/repositories/
>> snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/
>> >>
>> >> Jerry
>> >>
>> >> On Thu, Jul 6, 2017 at 8:51 AM, Jaroslaw Cwiklik <cwik...@apache.org>
>> >> wrote:
>> >>
>> >>> Hi, instructions how to build from source are here:
>> >>> https://uima.apache.org/building-uima.html
>> >>>
>> >>> It's a bit involved process so I will try to post a snapshot of
>> >>> uima-as
>> >>> to
>> >>> Apache snapshot repository and will provide you with a link later
>> today.
>> >>>
>> >>> Jerry
>> >>>
>> >>> On Wed, Jul 5, 2017 at 4:32 PM, nelson rivera <
>> nelsonriver...@gmail.com>
>> >>> wrote:
>> >>>
>> >>>> Please can you give me the url to source code with the changes, to
>> >>>> test.
>> >>>>
>> >>>> 2017-07-05 16:19 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>> >>>> > Just delivered a few changes to deal with a stale Session. Can you
>> >>>> > build
>> >>>> > from source and test.
>> >>>> > Jerry
>> >>>> >
>> >>>> > On Wed, Jul 5, 2017 at 2:21 PM, Jaroslaw Cwiklik <
>> cwik...@apache.org>
>> >>>> > wrote:
>> >>>> >
>> >>>> >> Thanks. Will check the code and work on a fix
>> >>>> >>
>> >>>> >> Jerry
>> >>>> >>
>> >>>> >> On Wed, Jul 5, 2017 at 2:10 PM, nelson rivera <
>> >>>> nelsonriver...@gmail.com>
>> >>>> >> wrote:
>> >>>> >>
>> >>>> >>> Here the stack trace for the error that asked me:
>> >>>> >>> jul 05, 2017 2:08:50 PM
>> >>>> >>> org.apache.uima.adapter.jms.client.ActiveMQMessageSender run
>> >>>> >>> ADVERTENCIA:
>> >>>> >>> javax.jms.IllegalStateException: The Session is closed
>> >>>> >>> at org.apache.activemq.ActiveMQSe
>> >>>> ssion.checkClosed(ActiveMQSess
>> >>>> >>> ion.java:771)
>> >>>

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

2017-07-07 Thread nelson rivera

Sorry for the delay, i am building the framework from the source at
https://svn.apache.org/repos/asf/uima/uima-as/trunk, when test the
issue, i will comment the result.

2017-07-06 10:04 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
> Hello, the snapshot binaries (zip + tar) are here:
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/uima/uima-as/2.9.1-SNAPSHOT/
>
> Jerry
>
> On Thu, Jul 6, 2017 at 8:51 AM, Jaroslaw Cwiklik <cwik...@apache.org>
> wrote:
>
>> Hi, instructions how to build from source are here:
>> https://uima.apache.org/building-uima.html
>>
>> It's a bit involved process so I will try to post a snapshot of uima-as
>> to
>> Apache snapshot repository and will provide you with a link later today.
>>
>> Jerry
>>
>> On Wed, Jul 5, 2017 at 4:32 PM, nelson rivera <nelsonriver...@gmail.com>
>> wrote:
>>
>>> Please can you give me the url to source code with the changes, to test.
>>>
>>> 2017-07-05 16:19 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
>>> > Just delivered a few changes to deal with a stale Session. Can you
>>> > build
>>> > from source and test.
>>> > Jerry
>>> >
>>> > On Wed, Jul 5, 2017 at 2:21 PM, Jaroslaw Cwiklik <cwik...@apache.org>
>>> > wrote:
>>> >
>>> >> Thanks. Will check the code and work on a fix
>>> >>
>>> >> Jerry
>>> >>
>>> >> On Wed, Jul 5, 2017 at 2:10 PM, nelson rivera <
>>> nelsonriver...@gmail.com>
>>> >> wrote:
>>> >>
>>> >>> Here the stack trace for the error that asked me:
>>> >>> jul 05, 2017 2:08:50 PM
>>> >>> org.apache.uima.adapter.jms.client.ActiveMQMessageSender run
>>> >>> ADVERTENCIA:
>>> >>> javax.jms.IllegalStateException: The Session is closed
>>> >>> at org.apache.activemq.ActiveMQSe
>>> ssion.checkClosed(ActiveMQSess
>>> >>> ion.java:771)
>>> >>> at org.apache.activemq.ActiveMQSe
>>> ssion.configureMessage(ActiveM
>>> >>> QSession.java:759)
>>> >>> at org.apache.activemq.ActiveMQSe
>>> ssion.createTextMessage(Active
>>> >>> MQSession.java:440)
>>> >>> at org.apache.uima.adapter.jms.cl
>>> ient.ActiveMQMessageSender.cre
>>> >>> ateTextMessage(ActiveMQMessageSender.java:184)
>>> >>> at org.apache.uima.adapter.jms.cl
>>> ient.BaseMessageSender.run(Bas
>>> >>> eMessageSender.java:307)
>>> >>> at java.lang.Thread.run(Thread.java:748)
>>> >>>
>>> >>> 2017-07-05 12:16 GMT-04:00, nelson rivera
>>> >>> <nelsonriver...@gmail.com>:
>>> >>> > This behavior is random, not occurs always. In the most of the
>>> simple
>>> >>> > programs and simple test case tested, after restart the UIMA-AS
>>> Broker
>>> >>> > without restart service uima-as, the instruccion to uima-as client
>>> >>> > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" return "false"
>>> and
>>> >>> > correctly i initialize the client again.
>>> >>> >
>>> >>> > The incorrect behavior is most frequently with many uima-as client
>>> >>> > instances. Is the case of my general application in which i have
>>> many
>>> >>> > service uima-as, and for each one creates one instace of uima-as
>>> >>> > client (BaseUIMAAsynchronousEngine_impl) and keep it alive to
>>> process
>>> >>> > all requests of the service uima-as.
>>> >>> >
>>> >>> > Is in this scenario with many instancies of uima-as client
>>> >>> > (BaseUIMAAsynchronousEngine_impl) in the same program (a
>>> >>> > monolithic
>>> >>> > application web in tomcat) where after restart the UIMA-AS Broker
>>> >>> > without restart any service uima-as, many uima-as client returns
>>> >>> > "true" to the instruccion
>>> >>> > "BaseUIMAAsynchronousEngine_impl.connectionOpen()" but them throw
>>> >>> > "javax.jms.IllegalStateException: The Session is closed"
>>> >>> > when proces the reques

Re: Broken conections after ACTIVEMQ restart with service uima-as CasMultiplier and delegate remote

2017-07-05 Thread nelson rivera

7.635 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XLangDetector Handling Release CAS Request.
Releasing CAS Reference Id: -7a178caa:15d13c3484d:-7874
01:33:17.635 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
WARNING: Controller: XLangDetector Failed To Send Message to Delegates
 Queue: null
01:33:17.635 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Service:XLangDetector JMS unable to Deliver
CAS:-7a178caa:15d13c3484d:-7875 -
Error:temp-queue://ID:nelson-XPS-8700-37197-1499275152544-13:1:1
01:33:17.635 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XLangDetector Handling Release CAS Request.
Releasing CAS Reference Id: -7a178caa:15d13c3484d:-7875
01:33:17.642 - 20:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
Begin -> XLangDetector::process --- OK
01:33:17.642 - 18:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
Begin -> XLangDetector::process --- OK
01:33:17.644 - 18:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End
-> XLangDetector::process --- OK
01:33:17.646 - 20:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End
-> XLangDetector::process --- OK
01:33:17.648 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
WARNING: Controller: XLangDetector Failed To Send Message to Delegates
 Queue: null
01:33:17.648 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
WARNING: Controller: XLangDetector Failed To Send Message to Delegates
 Queue: null
01:33:17.648 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Service:XLangDetector JMS unable to Deliver
CAS:-7a178caa:15d13c3484d:-7872 -
Error:temp-queue://ID:nelson-XPS-8700-37197-1499275152544-13:1:1
01:33:17.648 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XLangDetector Handling Release CAS Request.
Releasing CAS Reference Id: -7a178caa:15d13c3484d:-7872
01:33:17.649 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Service:XLangDetector JMS unable to Deliver
CAS:-7a178caa:15d13c3484d:-7873 -
Error:temp-queue://ID:nelson-XPS-8700-37197-1499275152544-13:1:1
01:33:17.649 - 8783:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XLangDetector Handling Release CAS Request.
Releasing CAS Reference Id: -7a178caa:15d13c3484d:-7873



2017-07-05 10:32 GMT-04:00, Jaroslaw Cwiklik <cwik...@apache.org>:
> Hi, the above problem is a different issue from the Session Closed reported
> earlier which occurs in the uima-as client. Please provide a stack trace
> for that.
>
> The issue you are reporting above is an expected behavior. The remote is
> trying to deliver msgs to a temp reply queue which no longer exists due to
> a broker restart. JMS temp queues are transient and not recoverable. If a
> broker is restarted while uima-as service is processing a CAS, that service
> will not be able to reply. Any new CASes (sent after broker restart) will
> have a valid temp queue and replies will succeed.
>
> Jerry
>
> On Wed, Jul 5, 2017 at 9:55 AM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> i have a aggregate service uima-as that it contains a CasMultiplier,
>> after this casmultiplier in the flow one of the delegates is remote.
>> The delegate remote is a primitive annotator implented in c++,but is
>> deployed with de deployAsyncService.sh de uima-as directly.
>>
>> With these step i get the error that shows
>>
>> 1- Start all components (broker , agregate service, remote service).
>> 2- First request, process ok
>> 3- Restart broker (without restart services uima-as). //Logs shows
>> Ready to Process Again
>> 4- Second request, process ok
>> 5- Restart broker, second (without restart services uima-as). //Logs
>> show Ready to Process Again
>> 6- I get a error, shows following lines in the log of the delegate
>> sevice uima-as remote.
>> Attachs images of the queues created at all time in case it is of
>> help. The remote service delegate is XLangdetector and service
>> agregate casmultiplier is XClusterAnalyzerAggregate.
>>
>> Errors Lines:
>> Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process
>> Again
>> 09:27:19.705 - 18:
>> org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
>> Begin -> XLangDetector::process --- OK
>> 09:27:19.707 - 18:
>> o

Broken conections after ACTIVEMQ restart with service uima-as CasMultiplier and delegate remote

2017-07-05 Thread nelson rivera

i have a aggregate service uima-as that it contains a CasMultiplier,
after this casmultiplier in the flow one of the delegates is remote.
The delegate remote is a primitive annotator implented in c++,but is
deployed with de deployAsyncService.sh de uima-as directly.

With these step i get the error that shows

1- Start all components (broker , agregate service, remote service).
2- First request, process ok
3- Restart broker (without restart services uima-as). //Logs shows
Ready to Process Again
4- Second request, process ok
5- Restart broker, second (without restart services uima-as). //Logs
show Ready to Process Again
6- I get a error, shows following lines in the log of the delegate
sevice uima-as remote.
Attachs images of the queues created at all time in case it is of
help. The remote service delegate is XLangdetector and service
agregate casmultiplier is XClusterAnalyzerAggregate.

Errors Lines:
Recovered Connection to Broker: tcp://127.0.0.1:61616 - Ready to Process Again
09:27:19.705 - 18:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
Begin -> XLangDetector::process --- OK
09:27:19.707 - 18:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End
-> XLangDetector::process --- OK
09:27:19.710 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
WARNING: Controller: XLangDetector Failed To Send Message to Delegates
 Queue: null
09:27:19.721 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Service:XLangDetector JMS unable to Deliver
CAS:-4f7adbed:15d12e82d61:-7fc7 -
Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1
09:27:19.721 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XLangDetector Handling Release CAS Request.
Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc7
09:27:19.722 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
WARNING: Controller: XLangDetector Failed To Send Message to Delegates
 Queue: null
09:27:19.722 - 19:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
Begin -> XLangDetector::process --- OK
09:27:19.723 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
WARNING: Controller: XLangDetector Failed To Send Message to Delegates
 Queue: null
09:27:19.724 - 17:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
Begin -> XLangDetector::process --- OK
09:27:19.725 - 17:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End
-> XLangDetector::process --- OK
09:27:19.727 - 19:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End
-> XLangDetector::process --- OK
09:27:19.732 - 20:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
Begin -> XLangDetector::process --- OK
09:27:19.734 - 20:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: : End
-> XLangDetector::process --- OK
09:27:19.737 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.send:
WARNING: Controller: XLangDetector Failed To Send Message to Delegates
 Queue: null
09:27:19.738 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Service:XLangDetector JMS unable to Deliver
CAS:-4f7adbed:15d12e82d61:-7fc8 -
Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1
09:27:19.738 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XLangDetector Handling Release CAS Request.
Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc8
09:27:19.738 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Service:XLangDetector JMS unable to Deliver
CAS:-4f7adbed:15d12e82d61:-7fc5 -
Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1
09:27:19.739 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XLangDetector Handling Release CAS Request.
Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc5
09:27:19.739 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Service:XLangDetector JMS unable to Deliver
CAS:-4f7adbed:15d12e82d61:-7fc6 -
Error:temp-queue://ID:nelson-XPS-8700-46518-1499260793324-13:1:1
09:27:19.739 - 3645:
org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.UimaAsAsyncCallbackListener.onException():
INFO: Controller: XLangDetector Handling Release CAS Request.
Releasing CAS Reference Id: -4f7adbed:15d12e82d61:-7fc6.

Re: Many views in the cas to serialize cause java.lang.NullPointerException in service uima-as

2017-02-16 Thread nelson rivera

I tested the solution that proposes, add processParentLast="true" to
the  Cas Multiplier delegate's configuration. The behavior is the
same. The other alternative that you say, is that i have a bug
somewhere in my code which allows a CAS to be accessed in two separate
threads, but i not have idea,because the cas generated in the second
cas multipler is composed of all views and then this cas go to the end
annotator that have only 1 instance, and here finish the flow.

2017-02-15 16:31 GMT-05:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Nelson, change Cas Multiplier in your deployment descriptor as follows:
>
> 
>  processParentLast="true"/>
> 
>
> Note: processParentLast="true".
>
> In UIMA-AS async aggregate its possible for a child CAS and its parent CAS
> to flow through the pipeline at the same time and the parent CAS may reach
> the end before its child(ren). The above setting will ensure the parent CAS
> does not flow ahead of its children. From UIMA-AS documentation:
>
> "The processParentLast attribute on the  element is
> optional, and specifies processing order of an input CAS relative to its
> children. If true, a flow of an input CAS will be suspended after it is
> returned from a Cas Multiplier delegate until all its child CASes have
> finished processing. If false, an input CAS can be processed in parallel
> with its children."
>
>
> If the above change does not fix the NPE, I suspect you may have a bug
> somewhere in your code which allows a CAS to be accessed in two separate
> threads.
>
> -jerry
>
> On Wed, Feb 15, 2017 at 12:43 PM, Jaroslaw Cwiklik <uim...@gmail.com>
> wrote:
>
>> Nelson, I can try to setup a simple pipeline with one AE which will add
>> 20
>> views and than test serialization. Not sure if I get to it today. If not
>> this will have to wait till Monday next week. I've already mentioned this
>> before, don't operate on a CAS once it leaves an AE. The contract is
>> CAS-In
>> CAS-out. A CAS instance can only be operated on by one AE at a time.
>>
>> -jerry
>>
>> On Wed, Feb 15, 2017 at 11:06 AM, Marshall Schor <m...@schor.com> wrote:
>>
>>> On 2/15/2017 9:51 AM, Jaroslaw Cwiklik wrote:
>>> > Not exactly sure how to debug this.
>>>
>>> a small-ish test case we could run would enable debugging...
>>>
>>> > The UIMA-AS does not touch contents of
>>> > a CAS directly. Are there any other errors in the log besides NPE? The
>>> > UIMA-AS uses uima-sdk to serialize CASes. Since you are getting null
>>> from
>>> > getView(N), this view must have been deleted somehow.
>>> >
>>> > -jerry
>>> >
>>> > On Mon, Feb 13, 2017 at 11:43 AM, nelson rivera <
>>> nelsonriver...@gmail.com>
>>> > wrote:
>>> >
>>> >> I was able to check your email just today. The agregegate is async,
>>> >> but only process one input CAS at the same time,default
>>> >> numberOfCASes.
>>> >> I read your possible explanation but i have no idea that another
>>> >> thread can modificate the cas, because the last annotator's execution
>>> >> is correct and only missing that the framework uima-as serializes the
>>> >> cas.
>>> >>
>>> >> This is the configuration of deploy of the aggregate:
>>> >>
>>> >> 
>>> >> >> >> xmlns="http://uima.apache.org/resourceSpecifier;>
>>> >>
>>> >> XClusterAnalyzerAE Deploy Descriptor
>>> >> Deploys XClusterAnalyzerAE
>>> >>
>>> >> 
>>> >>
>>> >> 
>>> >> >> >> brokerURL="${defaultBrokerURL}"/>
>>> >> 
>>> >> 
>>> >> 
>>> >> 
>>> >> >> >> internalReplyQueueScaleout="3">
>>> >> 
>>> >> 
>>> >> 
>>> >> 
>>> >> 
>>> >> 
>>> >> 
>>> >> >> >> continu

Re: Many views in the cas to serialize cause java.lang.NullPointerException in service uima-as

2017-02-13 Thread nelson rivera

I was able to check your email just today. The agregegate is async,
but only process one input CAS at the same time,default numberOfCASes.
I read your possible explanation but i have no idea that another
thread can modificate the cas, because the last annotator's execution
is correct and only missing that the framework uima-as serializes the
cas.

This is the configuration of deploy of the aggregate:


http://uima.apache.org/resourceSpecifier;>

XClusterAnalyzerAE Deploy Descriptor
Deploys XClusterAnalyzerAE





























































2017-02-10 16:43 GMT-05:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Just a bit more evidence. The caller of the gerSofaAddr()
>
> public void writeViewsCommons() throws Exception {
>   // Get indexes for each SofaFS in the CAS
>   int numViews = cas.getBaseSofaCount();
>
>   for (int sofaNum = 1; sofaNum <= numViews; sofaNum++) {
> FSIndexRepositoryImpl loopIR = (FSIndexRepositoryImpl)
>  cas.getBaseCAS().getSofaIndexRepository(sofaNum);
> final int sofaAddr = getSofaAddr(sofaNum);
>
> Not an expert of this code, but it smells like another thread is changing a
> CAS which is being serialized.
>
> -jerry
>
> On Fri, Feb 10, 2017 at 4:31 PM, Jaroslaw Cwiklik <uim...@gmail.com> wrote:
>
>> Is this a primitive (single-threaded) aggregate or async
>> (multi-threaded)?
>> If async, try to simplify and run primitive aggregate with scaleout=1.
>>
>> The CAS does not seem to be null in this case. The caller of the
>> getSerializedCas()
>> checks for null.
>>
>> The code dies here:
>> Caused by: java.lang.NullPointerException
>> at org.apache.uima.cas.impl.CasSerializerSupport$CasDocSerializ
>> er.getSofaAddr(CasSerializerSupport.java:454)
>>
>>public int getSofaAddr(int sofaNum) {
>>   if (sofaNum != 1 || cas.isInitialSofaCreated()) { //skip if initial
>> view && no Sofa yet
>> // all
>> non-initial-views must have a sofa
>>* return ((CASImpl)cas.getView(sofaNum)).getSofaRef();*
>>   }
>>   return 0;
>> }
>>
>> Looks to me that getView(sofaNum) is returning null. Is it possible that
>> two threads are operating on the same CAS maybe? One removing a view
>> while
>> another trying to serialize. Have no idea what else could it be.
>>
>> -jerry
>>
>>
>>
>> On Fri, Feb 10, 2017 at 8:45 AM, nelson rivera <nelsonriver...@gmail.com>
>> wrote:
>>
>>> Hi,  The first thing I did was these tests,i made a simple test case
>>> that create a Cas with 17 views and then serialize using
>>> XmiCasSerializer.serialize(newJCas.getCas(), fis) and serializes
>>> correctly.
>>> Also i made other test, initialize the same AE but of local way with
>>> UIMA API and process the same input documents and the processing is
>>> correct and then serialize the CAS, without problem.
>>>
>>> The error is with AE deployed in uima-as and consuming it.
>>>
>>> 2017-02-09 17:30 GMT-05:00, Marshall Schor <m...@schor.com>:
>>> > one thing that would help track this down is a small isolated test
>>> > case.
>>> >
>>> > Do you think uima-as is needed? I'm wondering if a simple test case
>>> which
>>> > generated 17 views and then tried to serialize would show the
>>> > failure...
>>> >
>>> > If you could supply a small test case that showed the failur

Re: Many views in the cas to serialize cause java.lang.NullPointerException in service uima-as

2017-02-10 Thread nelson rivera

Hi,  The first thing I did was these tests,i made a simple test case
that create a Cas with 17 views and then serialize using
XmiCasSerializer.serialize(newJCas.getCas(), fis) and serializes
correctly.
Also i made other test, initialize the same AE but of local way with
UIMA API and process the same input documents and the processing is
correct and then serialize the CAS, without problem.

The error is with AE deployed in uima-as and consuming it.

2017-02-09 17:30 GMT-05:00, Marshall Schor <m...@schor.com>:
> one thing that would help track this down is a small isolated test case.
>
> Do you think uima-as is needed? I'm wondering if a simple test case which
> generated 17 views and then tried to serialize would show the failure...
>
> If you could supply a small test case that showed the failure so we could
> reproduce it, that would enable a rapid resolution.
>
> -Marshall
>
>
> On 2/9/2017 3:58 PM, Marshall Schor wrote:
>>  The line throwing the null pointer exception is :
>>
>> cas.getView(sofaNum).getSofaRef()
>>
>> So the NPE is either the cas is null, or the getView(sofaNum) is returning
>> null.
>>
>> I'm not sure what the best way is to debug this...
>>
>> -Marshall
>>
>>
>>
>>
>> On 2/9/2017 12:42 PM, nelson rivera wrote:
>>> I have a aggregate service uima-as, at the end of aggregate the cas to
>>> return is composed of as many views as the number of input files, each
>>> view with annotations of processing.
>>> With a number of input documents less than 15 the processing is
>>> successful always,
>>> but if the number of documents is greater than 15, i get a
>>> NullPointerException at the aggregate service trying to serialize the
>>> cas, not in the processing of AE aggregate.
>>> the logs of aggregate service:
>>>
>>> 11:51:38.815 - 42:
>>> cu.datys.xinetica.uima.core.MergerInViewCasMultipler.hasNext(285):
>>> INFO: HasNext false
>>> 11:51:38.875 - 44:
>>> org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
>>> XClusterAnalyzer::process --- OK
>>> 11:51:39.145 - 45:
>>> org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient:
>>> WARNING: Service: XClusterAnalyzerAggregate Runtime Exception
>>> 11:51:39.145 - 45:
>>> org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient:
>>> WARNING:
>>> org.apache.uima.aae.error.AsynchAEException:
>>> org.apache.uima.UIMARuntimeException
>>> at
>>> org.apache.uima.adapter.jms.activemq.JmsOutputChannel.getSerializedCas(JmsOutputChannel.java:1265)
>>> at
>>> org.apache.uima.adapter.jms.activemq.JmsOutputChannel.sendReply(JmsOutputChannel.java:800)
>>> at
>>> org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.sendReplyToRemoteClient(AggregateAnalysisEngineController_impl.java:2173)
>>> at
>>> org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient(AggregateAnalysisEngineController_impl.java:2342)
>>> at
>>> org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.finalStep(AggregateAnalysisEngineController_impl.java:1862)
>>> at
>>> org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.executeFlowStep(AggregateAnalysisEngineController_impl.java:2489)
>>> at
>>> org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.process(AggregateAnalysisEngineController_impl.java:1271)
>>> at
>>> org.apache.uima.aae.handler.HandlerBase.invokeProcess(HandlerBase.java:118)
>>> at
>>> org.apache.uima.aae.handler.input.ProcessResponseHandler.cancelTimerAndProcess(ProcessResponseHandler.java:117)
>>> at
>>> org.apache.uima.aae.handler.input.ProcessResponseHandler.handleProcessResponseWithCASReference(ProcessResponseHandler.java:485)
>>> at
>>> org.apache.uima.aae.handler.input.ProcessResponseHandler.handle(ProcessResponseHandler.java:767)
>>> at
>>> org.apache.uima.aae.handler.HandlerBase.delegate(HandlerBase.java:149)
>>> at
>>> org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handle(ProcessRequestHandler_impl.java:1113)
>>> at
>>> org.apache.uima.aae.spi.transport.vm.UimaVmMessageListener.onMessage(UimaVmMessageListener.java:107)
>>> at
>>> org.apache.uima.aae.spi.transport.vm.UimaVmMessageDispatcher$1.run(UimaVmM

Many views in the cas to serialize cause java.lang.NullPointerException in service uima-as

2017-02-09 Thread nelson rivera

I have a aggregate service uima-as, at the end of aggregate the cas to
return is composed of as many views as the number of input files, each
view with annotations of processing.
With a number of input documents less than 15 the processing is
successful always,
but if the number of documents is greater than 15, i get a
NullPointerException at the aggregate service trying to serialize the
cas, not in the processing of AE aggregate.
the logs of aggregate service:

11:51:38.815 - 42:
cu.datys.xinetica.uima.core.MergerInViewCasMultipler.hasNext(285):
INFO: HasNext false
11:51:38.875 - 44:
org.apache.uima.uimacpp.UimacppAnalysisComponent.log(396): INFO: :
XClusterAnalyzer::process --- OK
11:51:39.145 - 45:
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient:
WARNING: Service: XClusterAnalyzerAggregate Runtime Exception
11:51:39.145 - 45:
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient:
WARNING:
org.apache.uima.aae.error.AsynchAEException:
org.apache.uima.UIMARuntimeException
at 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.getSerializedCas(JmsOutputChannel.java:1265)
at 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.sendReply(JmsOutputChannel.java:800)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.sendReplyToRemoteClient(AggregateAnalysisEngineController_impl.java:2173)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient(AggregateAnalysisEngineController_impl.java:2342)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.finalStep(AggregateAnalysisEngineController_impl.java:1862)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.executeFlowStep(AggregateAnalysisEngineController_impl.java:2489)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.process(AggregateAnalysisEngineController_impl.java:1271)
at 
org.apache.uima.aae.handler.HandlerBase.invokeProcess(HandlerBase.java:118)
at 
org.apache.uima.aae.handler.input.ProcessResponseHandler.cancelTimerAndProcess(ProcessResponseHandler.java:117)
at 
org.apache.uima.aae.handler.input.ProcessResponseHandler.handleProcessResponseWithCASReference(ProcessResponseHandler.java:485)
at 
org.apache.uima.aae.handler.input.ProcessResponseHandler.handle(ProcessResponseHandler.java:767)
at 
org.apache.uima.aae.handler.HandlerBase.delegate(HandlerBase.java:149)
at 
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handle(ProcessRequestHandler_impl.java:1113)
at 
org.apache.uima.aae.spi.transport.vm.UimaVmMessageListener.onMessage(UimaVmMessageListener.java:107)
at 
org.apache.uima.aae.spi.transport.vm.UimaVmMessageDispatcher$1.run(UimaVmMessageDispatcher.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at 
org.apache.uima.aae.UimaAsThreadFactory$1.run(UimaAsThreadFactory.java:132)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.uima.UIMARuntimeException
at 
org.apache.uima.cas.impl.XmiCasSerializer.serialize(XmiCasSerializer.java:420)
at 
org.apache.uima.cas.impl.XmiCasSerializer.serialize(XmiCasSerializer.java:385)
at 
org.apache.uima.aae.UimaSerializer.serializeCasToXmi(UimaSerializer.java:145)
at 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.serializeCAS(JmsOutputChannel.java:251)
at 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.getSerializedCas(JmsOutputChannel.java:1250)
... 18 more
Caused by: java.lang.NullPointerException
at 
org.apache.uima.cas.impl.CasSerializerSupport$CasDocSerializer.getSofaAddr(CasSerializerSupport.java:454)
at 
org.apache.uima.cas.impl.CasSerializerSupport$CasDocSerializer.writeViewsCommons(CasSerializerSupport.java:465)
at 
org.apache.uima.cas.impl.XmiCasSerializer$XmiDocSerializer.writeViews(XmiCasSerializer.java:572)
at 
org.apache.uima.cas.impl.CasSerializerSupport$CasDocSerializer.serialize(CasSerializerSupport.java:441)
at 
org.apache.uima.cas.impl.XmiCasSerializer.serialize(XmiCasSerializer.java:415)
... 22 more

Re: Proccesing Bamun characters

2016-12-27 Thread nelson rivera

After time of investigation, i found the root cause. The reason was
that i had Xalan library in my classpath and according
javax.xml.transform.newInstance() and ordered lookup procedure, uses
this Xalan implementation of  TransformerFactory. XmiCasSerializer
mechanism also use the SAXTransformerFactory that extends of
TransformerFactory.
Change to system-default implementation, specifying
"javax.xml.transform.TransformerFactory" system property, get the
expected results, the complete entities of the  unicode supplementary
characters when the input CAS is serialized, instead of the entities
of the two surrogates code units  that represents it, and of this way
not occurs any problem of deserialize in uima-as service.
At the end it seem be a bug of the XML transform engine that is used.




2016-12-19 10:03 GMT-05:00, nelson rivera <nelsonriver...@gmail.com>:
> I understand, and yes, these characters should not appear in the
> serialized cas, but they appear using
> XmiCasSerializer.serialize(cas.getCas(), outStream):
>
> ... mimeType="text" sofaString="�
> �"/>...
>
> In my application not use FileSystemCollectionReader.
> The user introduces the text, the text is stored in string java
> (utf-16) and it set to the cas that will be processing, using
> setDocumentLanguage, then i send the cas.
>
> 2016-12-18 23:06 GMT-05:00, Burn Lewis <burnle...@gmail.com>:
>> Since these characters are above the basic UTF-16 limit they are
>> represented as 2 UTF-16 characters with high & low surrogate prefixes.
>> So
>> 55322 + 56704 are xD81A + xDD80 and after removing the 6-bit surrogate
>> prefixes of D8 & DC we have 2 10-bit numbers 1A + 180 which combine as
>> 6980, and after adding 2*16 (since only characters above this need
>> surrogate pairs) we have the expected x16980.
>> So one mystery is: their appearance in the CAS with the 
<

Using optional argument -Duima.as.enable.jmx=false

2016-12-22 Thread nelson rivera

I am testing recent uima-as 2.9.0 release. I try deploy a service
uima-as, with the new argument uima.as.enable.jmx with value "false",
i expected that the UIMA-AS will start with no JMX support and no port
will not be opened, but a port continue opening and Providing JMX
statistics of processing.

What should be the behavior of this argument?

This is the complete set of arguments JMX configured in the uima-as
service start:

-Duima.as.enable.jmx=false
-Duima.as.enable.jmx=false -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=$PORT
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

Re: Proccesing Bamun characters

2016-12-19 Thread nelson rivera

I understand, and yes, these characters should not appear in the
serialized cas, but they appear using
XmiCasSerializer.serialize(cas.getCas(), outStream):

..

In my application not use FileSystemCollectionReader.
The user introduces the text, the text is stored in string java
(utf-16) and it set to the cas that will be processing, using
setDocumentLanguage, then i send the cas.

2016-12-18 23:06 GMT-05:00, Burn Lewis :
> Since these characters are above the basic UTF-16 limit they are
> represented as 2 UTF-16 characters with high & low surrogate prefixes.  So
> 55322 + 56704 are xD81A + xDD80 and after removing the 6-bit surrogate
> prefixes of D8 & DC we have 2 10-bit numbers 1A + 180 which combine as
> 6980, and after adding 2*16 (since only characters above this need
> surrogate pairs) we have the expected x16980.
> So one mystery is: their appearance in the CAS with the

Re: Proccesing Bamun characters

2016-12-16 Thread nelson rivera

This is the cas serialize to xmi before send to uima-as service,
serialize with  XmiCasSerializer.serialize(cas.getCas(), outStream).
The representation of the characters In this serialization does not
match with the representation of characters with problems. It's being
serialized the code points escape sequences corresponding to the Bamum
characters, two code point by each character.
Why can this happen? Any suggestions

http:///uima/cas.ecore; xmlns:xmi="http://www.omg.org/XMI;
xmlns:pln="http:///cu/datys/xinetica/uima/api/pln.ecore;
xmlns:tcas="http:///uima/tcas.ecore;
xmlns:api="http:///cu/datys/xinetica/uima/api.ecore;
xmi:version="2.0">


2016-12-16 14:06 GMT-05:00, Burn Lewis <burnle...@gmail.com>:
> Sorry, I missed the supplement set.  So the tests I did with x16980 &
> x16990 are valid.  runRemoteAsyncAE uses the same
> FileSystemCollectionReader as runAE does ... did you use a different
> collection reader?  If a custom one perhaps you could serialize the cas to
> a file as XMI and verify that the XMI is legal.
>
> On Fri, Dec 16, 2016 at 8:37 AM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> In Wikipedia the Bamum
>> Script(https://en.wikipedia.org/wiki/Bamum_script) contain another
>> valid range is U+16800–U+16A3F, any of theses characters generate the
>> same log trace. I will continue to test the  Marshall Schor
>> suggestion.
>>
>> 2016-12-14 18:07 GMT-05:00, Burn Lewis <burnle...@gmail.com>:
>> > I think there's another problem ... the characters we have tested with
>> are
>> > not in the Bamum unicode set.  The first 2 that Marshall listed in
>> > utf-8
>> > (F0 96 A6 80 & F0 96 A6 90) are in hex x16980 & x16990 and the 3rd (EF
>> > BF
>> > BD) is xFFFD.  This last one is the "replacement character" used when
>> > an
>> > illegal character is encountered.  According to Wikipedia the 88 Bamum
>> > characters are in the range xA6A0 - xA6F7.
>> >
>> > In order to reproduce your problem we need to yse the same codepoints.
>> Can
>> > you tell us what the hex value of the failing characters are, in UTF-8
>> > or
>> > UTF-!6?
>> >
>> > By the way, the test I ran was using UIMA-AS's runRemoteAsyncAE, not
>> runAE,
>> > following the quick test described in the UIMA-AS README.
>> >
>> > On Wed, Dec 14, 2016 at 4:15 PM, Marshall Schor <m...@schor.com> wrote:
>> >
>> >> Maybe we've been on the wrong line of thinking.
>> >>
>> >> Perhaps the translation between UTF-8 (during transportation) and the
>> >> string
>> >> characters is fine, but the XML parsing is restricting the character
>> >> set
>> >> it uses.
>> >>
>> >> See https://en.wikipedia.org/wiki/Valid_characters_in_XML
>> >>
>> >> where it says valid xml characters exclude the "surrogates", which
>> >> your
>> >> characters I think are.
>> >>
>> >> So, perhaps it's XML parsing which is complaining (and it appears this
>> is
>> >> so,
>> >> from the stack trace).
>> >>
>> >> We should point out that UIMA's character offsets (like begin an end)
>> >> were
>> >> designed with Java String character offsets, and will perhaps not work
>> >> correctly
>> >> when surrogates are being used.
>> >>
>> >> A possible workaround for this particular issue may be to switch to
>> >> binary
>> >> serialization, instead of xmi serialization. This has a restriction in
>> >> that the
>> >> type systems much be identical (between the client and server).
>> >>
>> >> We could possibly get more confirmation of this hypothesis if you
>> >> could
>> >> say what
>> >> the stack trace was, beyond the first bit which you stated in your
>> >> original
>> >> note.  There should be more stack trace information, further down,
>> >> starting with
>> >> "caused by ..." which may provide more helpful information.
>> >>
>> >> -Marshall
>> >>
>> >>
>> >> On 12/14/2016 9:38 AM, nelson rivera wrote:
>> >> > We also did that test with uima framework and RunAE tool and
>> >> > thecharacters in a file as you, and effectively not exist problem.
>> >> > The
>> >> > problem is use uima-as,  sendCAS() with UimaAsynchronousEngine and
>> >> > when trying to deserialize the cas deserializeCasFromXmi() in remote
>> >> > uima-as service, that  i get the mentioned exception
>> >> > "org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 571;
>> >> > Character reference "
<

Re: Proccesing Bamun characters

2016-12-16 Thread nelson rivera

In Wikipedia the Bamum
Script(https://en.wikipedia.org/wiki/Bamum_script) contain another
valid range is U+16800–U+16A3F, any of theses characters generate the
same log trace. I will continue to test the  Marshall Schor
suggestion.

2016-12-14 18:07 GMT-05:00, Burn Lewis <burnle...@gmail.com>:
> I think there's another problem ... the characters we have tested with are
> not in the Bamum unicode set.  The first 2 that Marshall listed in utf-8
> (F0 96 A6 80 & F0 96 A6 90) are in hex x16980 & x16990 and the 3rd (EF BF
> BD) is xFFFD.  This last one is the "replacement character" used when an
> illegal character is encountered.  According to Wikipedia the 88 Bamum
> characters are in the range xA6A0 - xA6F7.
>
> In order to reproduce your problem we need to yse the same codepoints.  Can
> you tell us what the hex value of the failing characters are, in UTF-8 or
> UTF-!6?
>
> By the way, the test I ran was using UIMA-AS's runRemoteAsyncAE, not runAE,
> following the quick test described in the UIMA-AS README.
>
> On Wed, Dec 14, 2016 at 4:15 PM, Marshall Schor <m...@schor.com> wrote:
>
>> Maybe we've been on the wrong line of thinking.
>>
>> Perhaps the translation between UTF-8 (during transportation) and the
>> string
>> characters is fine, but the XML parsing is restricting the character set
>> it uses.
>>
>> See https://en.wikipedia.org/wiki/Valid_characters_in_XML
>>
>> where it says valid xml characters exclude the "surrogates", which your
>> characters I think are.
>>
>> So, perhaps it's XML parsing which is complaining (and it appears this is
>> so,
>> from the stack trace).
>>
>> We should point out that UIMA's character offsets (like begin an end)
>> were
>> designed with Java String character offsets, and will perhaps not work
>> correctly
>> when surrogates are being used.
>>
>> A possible workaround for this particular issue may be to switch to
>> binary
>> serialization, instead of xmi serialization. This has a restriction in
>> that the
>> type systems much be identical (between the client and server).
>>
>> We could possibly get more confirmation of this hypothesis if you could
>> say what
>> the stack trace was, beyond the first bit which you stated in your
>> original
>> note.  There should be more stack trace information, further down,
>> starting with
>> "caused by ..." which may provide more helpful information.
>>
>> -Marshall
>>
>>
>> On 12/14/2016 9:38 AM, nelson rivera wrote:
>> > We also did that test with uima framework and RunAE tool and
>> > thecharacters in a file as you, and effectively not exist problem. The
>> > problem is use uima-as,  sendCAS() with UimaAsynchronousEngine and
>> > when trying to deserialize the cas deserializeCasFromXmi() in remote
>> > uima-as service, that  i get the mentioned exception
>> > "org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 571;
>> > Character reference "
<

Re: Proccesing Bamun characters

2016-12-14 Thread nelson rivera

We also did that test with uima framework and RunAE tool and
thecharacters in a file as you, and effectively not exist problem. The
problem is use uima-as,  sendCAS() with UimaAsynchronousEngine and
when trying to deserialize the cas deserializeCasFromXmi() in remote
uima-as service, that  i get the mentioned exception
"org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 571;
Character reference "

Re: Proccesing Bamun characters

2016-12-12 Thread nelson rivera

Yes these are the values of the troublesome characters, using
Integer.toHexString() to print out each byte, shows

fff0 ff96 ffa6 ff80

fff0 ff96 ffa6 ff90

ffef ffbf ffbd

ffef ffbf ffbd

2016-12-12 11:35 GMT-05:00, Marshall Schor <m...@schor.com>:
> Hi Nelson,
>
> Looking into this... Can you please confirm that the UTF-8 coding of the
> troublesome characters, in hexadecimal, is:
>
> F0 96 A6 80
>
> F0 96 A6 90
>
> EF BF BD
>
> EF BF BD
>
> If you have the string in Java, please try converting it to a UTF-8 string
> using
> something like:
>   byte[] theBytes = myTestString.getBytes("UTF-8");
>
>   and then print out theBytes in hex; they should look like the above.  If
> not,
> please let us know what the values is instead.
>
>
> Thanks. -Marshall
>
>
> On 12/9/2016 9:02 AM, nelson rivera wrote:
>> Hi i was read your explication and saw the link, but in my case, i
>> don't read any xml file. Just i copy the text, get a new input cas
>> from UimaAsynchronousEngine with getCAS(), set the text in the cas and
>> send the request whit sendCAS(). I use uima-as API 2.9.0 in the client
>> side. Apparently the characters are changed for its entities
>> corresponding when serialize the cas to send it, but i get the
>> mentioned exception "org.xml.sax.SAXParseException; lineNumber: 1;
>> columnNumber: 571; Character reference "
<

Re: Proccesing Bamun characters

2016-12-09 Thread nelson rivera

Hi i was read your explication and saw the link, but in my case, i
don't read any xml file. Just i copy the text, get a new input cas
from UimaAsynchronousEngine with getCAS(), set the text in the cas and
send the request whit sendCAS(). I use uima-as API 2.9.0 in the client
side. Apparently the characters are changed for its entities
corresponding when serialize the cas to send it, but i get the
mentioned exception "org.xml.sax.SAXParseException; lineNumber: 1;
columnNumber: 571; Character reference "

Proccesing Bamun characters

2016-12-08 Thread nelson rivera

i tried to proccess the following text in a service deploy in uima-as,
because is input of my application. This is the text : 榀  榐  �  �.
These characters correspond to the bamun language, and apparently are
not  invalid xml characters because tools such as browsers interpret
it and show it. After get a new input cas to proccesing, set the text
and send the request, i get  the exception that i show below in
uima-as, the framework uima-as work and recovers correctly, just not
process this characters.
Could you tell me what happens with these characters, one of these is
invalid characters for framework uima-as?



04:00:31.606 - 14:
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestFromRemoteClient:
WARNING:
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 571;
Character reference

Re: Possible cause of nullPointerException in casmultiplier?

2016-11-29 Thread nelson rivera

You are absolutely right, I should not release the input CAS in my AE.
This was apparently the cause of the error. thank you very much

2016-11-28 13:09 GMT-05:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> An input CAS should not be released in the AE (user code). The Flow
> Controller should be used
> to prevent a CAS from flowing downstream. UIMA-AS will try to release a CAS
> in a Final Step
> of processing and this may cause an error like
>
> "The system tried to return a common analysis structure to the pool from
> which it was not checked out."
>
> Jerry
>
>
> On Mon, Nov 28, 2016 at 12:40 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> I have deployed the aggregate of asynchronous way.
>>  And i configure this aggregate to processing one request at the same
>> time(numberOfCASes=1,default), because as i commented on previous
>> email, in my flow: The first casmultiplier receive a annotation with
>> the path of a folder and creates a new child cas for each file in the
>> folder, the child cas
>> continue the flow in the other primitive annotators and at the end it
>> go to the second casmultipler, in the second casmultipler can or not
>> create new child cas, in the case of not i release the cas. I am
>> assuming (numberOfCASes=1,default) that until all child has finished
>> its processing, the aggregate not going processing other input cas of
>> other request, it is correct?.
>>
>>
>>
>> 2016-11-28 12:00 GMT-05:00, Jaroslaw Cwiklik <uim...@gmail.com>:
>> > Nelson, this error:
>> >
>> > "The system tried to return a common analysis structure to the pool
>> > from
>> > which it was not checked out."
>> >
>> > I think this is caused if you try to release a CAS that has been
>> previously
>> > released. Sure you
>> > are not trying to release it twice? I think releasing an input CAS in
>> > AE
>> > code is not a good idea. I am assuming
>> > you have an asynchronous aggregate (queue in front of each AE). In such
>> > deployments, the UIMA-AS is
>> > responsible for releasing a CAS once it reaches a Final state. Within a
>> > synchronous aggregate I am not sure
>> > if you are allowed to release a CAS in your code. Perhaps others can
>> chime
>> > in. Can you confirm which
>> > deployment you chose for this aggregate (synch or asynch)
>> > Jerry
>> >
>> > On Fri, Nov 25, 2016 at 11:14 AM, nelson rivera <
>> nelsonriver...@gmail.com>
>> > wrote:
>> >
>> >> The errores related are very random. I found a patron of error ( don't
>> >> know if it's the only one): The caspool of the first casmultipler
>> >> have size of 8, if i send a request to the aggregate in which the
>> >> first casmultipler have to generate more than 8 child cas, i get
>> >> random errors, the childs cas generated after the number 8, sometimes
>> >> is empty, sometimes have less annotations than it should have (I see
>> >> this with a own XCasSerializer annotator) or get nullPointerException.
>> >> I don't know why can happen, because in the method "process()" of the
>> >> second casmultipler i release the incoming cas (aJCas.release();)
>> >> directly in my source code, for that the caspool of the first
>> >> casmultipler will not empty. There is something taht i am not doing
>> >> well?
>> >>
>> >> I don't have idea what may be going on?, i will appreciate the help
>> >>
>> >> 2016-11-24 19:24 GMT-05:00, nelson rivera <nelsonriver...@gmail.com>:
>> >> > I continued investigating  and according to the stacktrace and
>> >> > source
>> >> > code of of FSIndexRepositoryImpl.ll_addFS_common() the exception is
>> >> > from line 2805 , in this part
>> >> >
>> >> > final ArrayList<IndexIteratorCachePair>
>> >> > indexes = this.indexArray[typeCode];
>> >> > // Add fsRef to all indexes.
>> >> > boolean noIndexOrOnlySetindexes = true;
>> >> > for (IndexIteratorCachePair iicp :
>> >> > indexes) {} //here
>> >> >
>> >> > apparently loop on a null value, any idea of why can happen this
>> >> exception?
>> >> >
>> >> > 2016-11-24 16:27 GMT-05:00, nelson rivera
>> >> > <nelsonriver...@gmail.com>:
>

Re: Possible cause of nullPointerException in casmultiplier?

2016-11-28 Thread nelson rivera

I have deployed the aggregate of asynchronous way.
 And i configure this aggregate to processing one request at the same
time(numberOfCASes=1,default), because as i commented on previous
email, in my flow: The first casmultiplier receive a annotation with
the path of a folder and creates a new child cas for each file in the
folder, the child cas
continue the flow in the other primitive annotators and at the end it
go to the second casmultipler, in the second casmultipler can or not
create new child cas, in the case of not i release the cas. I am
assuming (numberOfCASes=1,default) that until all child has finished
its processing, the aggregate not going processing other input cas of
other request, it is correct?.



2016-11-28 12:00 GMT-05:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Nelson, this error:
>
> "The system tried to return a common analysis structure to the pool from
> which it was not checked out."
>
> I think this is caused if you try to release a CAS that has been previously
> released. Sure you
> are not trying to release it twice? I think releasing an input CAS in AE
> code is not a good idea. I am assuming
> you have an asynchronous aggregate (queue in front of each AE). In such
> deployments, the UIMA-AS is
> responsible for releasing a CAS once it reaches a Final state. Within a
> synchronous aggregate I am not sure
> if you are allowed to release a CAS in your code. Perhaps others can chime
> in. Can you confirm which
> deployment you chose for this aggregate (synch or asynch)
> Jerry
>
> On Fri, Nov 25, 2016 at 11:14 AM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> The errores related are very random. I found a patron of error ( don't
>> know if it's the only one): The caspool of the first casmultipler
>> have size of 8, if i send a request to the aggregate in which the
>> first casmultipler have to generate more than 8 child cas, i get
>> random errors, the childs cas generated after the number 8, sometimes
>> is empty, sometimes have less annotations than it should have (I see
>> this with a own XCasSerializer annotator) or get nullPointerException.
>> I don't know why can happen, because in the method "process()" of the
>> second casmultipler i release the incoming cas (aJCas.release();)
>> directly in my source code, for that the caspool of the first
>> casmultipler will not empty. There is something taht i am not doing
>> well?
>>
>> I don't have idea what may be going on?, i will appreciate the help
>>
>> 2016-11-24 19:24 GMT-05:00, nelson rivera <nelsonriver...@gmail.com>:
>> > I continued investigating  and according to the stacktrace and source
>> > code of of FSIndexRepositoryImpl.ll_addFS_common() the exception is
>> > from line 2805 , in this part
>> >
>> > final ArrayList<IndexIteratorCachePair>
>> > indexes = this.indexArray[typeCode];
>> > // Add fsRef to all indexes.
>> > boolean noIndexOrOnlySetindexes = true;
>> > for (IndexIteratorCachePair iicp :
>> > indexes) {} //here
>> >
>> > apparently loop on a null value, any idea of why can happen this
>> exception?
>> >
>> > 2016-11-24 16:27 GMT-05:00, nelson rivera <nelsonriver...@gmail.com>:
>> >> the error continue ocurring , this is the log, my casmultiplier is
>> >> FileSystemMultiplerCas
>> >>
>> >> 04:04:17.520 - 23:
>> >> cu.datys.xinetica.uima.core.FileSystemMultiplerCas.next(334): INFO:
>> >> Adicionando annotation tipo cu.datys.xinetica.uima.ContinueOnFailure
>> >> 04:04:17.522 - 23: org.apache.uima.util.CasPool.releaseCas: WARNING:
>> >> The system tried to return a common analysis structure to the pool
>> >> from which it was not checked out.
>> >> 04:04:17.523 - 23:
>> >> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.
>> callAnalysisComponentNext(549):
>> >> SEVERE: Exception occurred
>> >> org.apache.uima.analysis_engine.AnalysisEngineProcessException
>> >>  at
>> >> cu.datys.xinetica.uima.core.FileSystemMultiplerCas.next(
>> FileSystemMultiplerCas.java:351)
>> >>  at
>> >> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.
>> callAnalysisComponentNext(PrimitiveAnalysisEngine_impl.java:526)
>> >>  at
>> >> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl$
>> AnalysisComponentCasIterator.next(PrimitiveAnalysisEngine_impl.java:647)
>> >>  at
>> >> org.apache.uima.aae.contro

Re: Possible cause of nullPointerException in casmultiplier?

2016-11-24 Thread nelson rivera

I continued investigating  and according to the stacktrace and source
code of of FSIndexRepositoryImpl.ll_addFS_common() the exception is
from line 2805 , in this part

final ArrayList<IndexIteratorCachePair>
indexes = this.indexArray[typeCode];
// Add fsRef to all indexes.
boolean noIndexOrOnlySetindexes = true;
for (IndexIteratorCachePair iicp :
indexes) {} //here

apparently loop on a null value, any idea of why can happen this exception?

2016-11-24 16:27 GMT-05:00, nelson rivera <nelsonriver...@gmail.com>:
> the error continue ocurring , this is the log, my casmultiplier is
> FileSystemMultiplerCas
>
> 04:04:17.520 - 23:
> cu.datys.xinetica.uima.core.FileSystemMultiplerCas.next(334): INFO:
> Adicionando annotation tipo cu.datys.xinetica.uima.ContinueOnFailure
> 04:04:17.522 - 23: org.apache.uima.util.CasPool.releaseCas: WARNING:
> The system tried to return a common analysis structure to the pool
> from which it was not checked out.
> 04:04:17.523 - 23:
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentNext(549):
> SEVERE: Exception occurred
> org.apache.uima.analysis_engine.AnalysisEngineProcessException
>   at
> cu.datys.xinetica.uima.core.FileSystemMultiplerCas.next(FileSystemMultiplerCas.java:351)
>   at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentNext(PrimitiveAnalysisEngine_impl.java:526)
>   at
> org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl$AnalysisComponentCasIterator.next(PrimitiveAnalysisEngine_impl.java:647)
>   at
> org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl.process(PrimitiveAnalysisEngineController_impl.java:860)
>   at
> org.apache.uima.aae.handler.HandlerBase.invokeProcess(HandlerBase.java:121)
>   at
> org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestWithCASReference(ProcessRequestHandler_impl.java:795)
>   at
> org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handle(ProcessRequestHandler_impl.java:1055)
>   at
> org.apache.uima.aae.spi.transport.vm.UimaVmMessageListener.onMessage(UimaVmMessageListener.java:107)
>   at
> org.apache.uima.aae.spi.transport.vm.UimaVmMessageDispatcher$1.run(UimaVmMessageDispatcher.java:70)
>   at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at
> org.apache.uima.aae.UimaAsThreadFactory$1.run(UimaAsThreadFactory.java:132)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
>   at
> org.apache.uima.cas.impl.FSIndexRepositoryImpl.ll_addFS_common(FSIndexRepositoryImpl.java:2805)
>   at
> org.apache.uima.cas.impl.FSIndexRepositoryImpl.ll_addFS(FSIndexRepositoryImpl.java:2763)
>   at
> org.apache.uima.cas.impl.FSIndexRepositoryImpl.addFS(FSIndexRepositoryImpl.java:2068)
>   at
> org.apache.uima.cas.impl.FSIndexRepositoryImpl.addFS(FSIndexRepositoryImpl.java:2674)
>   at org.apache.uima.cas.impl.CASImpl.addFsToIndexes(CASImpl.java:5023)
>   at org.apache.uima.jcas.impl.JCasImpl.addFsToIndexes(JCasImpl.java:1525)
>   at
> cu.datys.xinetica.uima.core.FileSystemMultiplerCas.next(FileSystemMultiplerCas.java:337)
>
>
> 2016-11-23 16:14 GMT-05:00, nelson rivera <nelsonriver...@gmail.com>:
>> I have a aggregate service that contains in the flow in this order : 1
>> casmultiplier, then 2 primitive annotators and at the end other
>> casmultiplier.
>> The first casmultiplier receive a annotation with the path of a folder
>> and creates a new child cas for each file in the folder, the child cas
>> continue the flow in the other primitive annotators and at the end it
>> go to the second casmultipler, in the second casmultipler can or not
>> create new child cas, in the case of not, in the  method process() i
>> release de cas (aJCas.release();) directly in my source code.
>>
>> This aggregate service is deploys in uima-as and configure for
>> processing only one request at the same time > numberOfCASes="1"/>.  For any reason, sometimes and of aleatorie way ,
>> making many requests to the service from many thread concurrent, in
>> the first casmultiplier in method next() after get the new cas (JCas
>> jcas = getEmptyJCas()) and while populate the cas , apparently some
>> external component in another parallel thread modifys this obtained
>> cas, and i get a NullPointerException adding a annotation
>> (jcas.addFsToIndexes(copyOfFs);) in method next().
>>
>&g

Re: Possible cause of nullPointerException in casmultiplier?

2016-11-24 Thread nelson rivera

the error continue ocurring , this is the log, my casmultiplier is
FileSystemMultiplerCas

04:04:17.520 - 23:
cu.datys.xinetica.uima.core.FileSystemMultiplerCas.next(334): INFO:
Adicionando annotation tipo cu.datys.xinetica.uima.ContinueOnFailure
04:04:17.522 - 23: org.apache.uima.util.CasPool.releaseCas: WARNING:
The system tried to return a common analysis structure to the pool
from which it was not checked out.
04:04:17.523 - 23:
org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentNext(549):
SEVERE: Exception occurred
org.apache.uima.analysis_engine.AnalysisEngineProcessException
at 
cu.datys.xinetica.uima.core.FileSystemMultiplerCas.next(FileSystemMultiplerCas.java:351)
at 
org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentNext(PrimitiveAnalysisEngine_impl.java:526)
at 
org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl$AnalysisComponentCasIterator.next(PrimitiveAnalysisEngine_impl.java:647)
at 
org.apache.uima.aae.controller.PrimitiveAnalysisEngineController_impl.process(PrimitiveAnalysisEngineController_impl.java:860)
at 
org.apache.uima.aae.handler.HandlerBase.invokeProcess(HandlerBase.java:121)
at 
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestWithCASReference(ProcessRequestHandler_impl.java:795)
at 
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handle(ProcessRequestHandler_impl.java:1055)
at 
org.apache.uima.aae.spi.transport.vm.UimaVmMessageListener.onMessage(UimaVmMessageListener.java:107)
at 
org.apache.uima.aae.spi.transport.vm.UimaVmMessageDispatcher$1.run(UimaVmMessageDispatcher.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at 
org.apache.uima.aae.UimaAsThreadFactory$1.run(UimaAsThreadFactory.java:132)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at 
org.apache.uima.cas.impl.FSIndexRepositoryImpl.ll_addFS_common(FSIndexRepositoryImpl.java:2805)
at 
org.apache.uima.cas.impl.FSIndexRepositoryImpl.ll_addFS(FSIndexRepositoryImpl.java:2763)
at 
org.apache.uima.cas.impl.FSIndexRepositoryImpl.addFS(FSIndexRepositoryImpl.java:2068)
at 
org.apache.uima.cas.impl.FSIndexRepositoryImpl.addFS(FSIndexRepositoryImpl.java:2674)
at org.apache.uima.cas.impl.CASImpl.addFsToIndexes(CASImpl.java:5023)
at org.apache.uima.jcas.impl.JCasImpl.addFsToIndexes(JCasImpl.java:1525)
at 
cu.datys.xinetica.uima.core.FileSystemMultiplerCas.next(FileSystemMultiplerCas.java:337)


2016-11-23 16:14 GMT-05:00, nelson rivera <nelsonriver...@gmail.com>:
> I have a aggregate service that contains in the flow in this order : 1
> casmultiplier, then 2 primitive annotators and at the end other
> casmultiplier.
> The first casmultiplier receive a annotation with the path of a folder
> and creates a new child cas for each file in the folder, the child cas
> continue the flow in the other primitive annotators and at the end it
> go to the second casmultipler, in the second casmultipler can or not
> create new child cas, in the case of not, in the  method process() i
> release de cas (aJCas.release();) directly in my source code.
>
> This aggregate service is deploys in uima-as and configure for
> processing only one request at the same time  numberOfCASes="1"/>.  For any reason, sometimes and of aleatorie way ,
> making many requests to the service from many thread concurrent, in
> the first casmultiplier in method next() after get the new cas (JCas
> jcas = getEmptyJCas()) and while populate the cas , apparently some
> external component in another parallel thread modifys this obtained
> cas, and i get a NullPointerException adding a annotation
> (jcas.addFsToIndexes(copyOfFs);) in method next().
>
> Any idea of what may be going on?
>
> this is the descriptor uima-as:
>
>
> 
>  xmlns="http://uima.apache.org/resourceSpecifier;>
>
> XPlagiarismCheckerAggregateAE Deploy Descriptor
> Deploys XPlagiarismCheckerAggregateAE
>
> 
> 
>  brokerURL="${defaultBrokerURL}"/>
> 
> 
> 
>  internalReplyQueueScaleout="3">
> 
> 
> 
> 
> 
> 
> 
>  continueOnRetryFailure="t

Possible cause of nullPointerException in casmultiplier?

2016-11-23 Thread nelson rivera

I have a aggregate service that contains in the flow in this order : 1
casmultiplier, then 2 primitive annotators and at the end other
casmultiplier.
The first casmultiplier receive a annotation with the path of a folder
and creates a new child cas for each file in the folder, the child cas
continue the flow in the other primitive annotators and at the end it
go to the second casmultipler, in the second casmultipler can or not
create new child cas, in the case of not, in the  method process() i
release de cas (aJCas.release();) directly in my source code.

This aggregate service is deploys in uima-as and configure for
processing only one request at the same time .  For any reason, sometimes and of aleatorie way ,
making many requests to the service from many thread concurrent, in
the first casmultiplier in method next() after get the new cas (JCas
jcas = getEmptyJCas()) and while populate the cas , apparently some
external component in another parallel thread modifys this obtained
cas, and i get a NullPointerException adding a annotation
(jcas.addFsToIndexes(copyOfFs);) in method next().

Any idea of what may be going on?

this is the descriptor uima-as:



http://uima.apache.org/resourceSpecifier;>

XPlagiarismCheckerAggregateAE Deploy Descriptor
Deploys XPlagiarismCheckerAggregateAE

Re: What should happen with the original input cas and child cas when a excption occurs

2016-11-22 Thread nelson rivera

Exactly, my application it hang due to that the cas pool is depleted,
and in the uima-as log i see exceptions in the casmultiplier, but i
was not sure of wich should be the behaivior. I will check my
application and let know if the error is not in my source. thank you

2016-11-22 16:54 GMT-05:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Nelson, in a scenario where there is a CM failure all child CASes are auto
> released back to
> a pool and an input CAS is returned with an exception. Are you observing a
> hang due to
> depleted cas pool on subsequent input CAS?
>
> Jerry
>
> On Tue, Nov 22, 2016 at 4:15 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> I have a service aggregate deployed in uima-as, the first annotator in
>> the aggregate is a casmultipler y then more primitive annotator in the
>> flow. When in the middle of processing (Have been generated various
>> child cas from the casmultipler and are being processed in other
>> anotators in the flow) occurs an exception in casmultipler's method
>> next (Ex NullPointerException), what should happen with the original
>> input cas and child cas that were being processed?
>>
>> In practice when this happens, and i get in the listener associated
>> method entityComplete, a status of exception and a reference to the
>> original input cas, but, what happen with child cas that were being
>> processed?. Are release to the casmultipler's caspool automatically?
>>
>> I would appreciate the explanation
>>
>

What should happen with the original input cas and child cas when a excption occurs

2016-11-22 Thread nelson rivera

I have a service aggregate deployed in uima-as, the first annotator in
the aggregate is a casmultipler y then more primitive annotator in the
flow. When in the middle of processing (Have been generated various
child cas from the casmultipler and are being processed in other
anotators in the flow) occurs an exception in casmultipler's method
next (Ex NullPointerException), what should happen with the original
input cas and child cas that were being processed?

In practice when this happens, and i get in the listener associated
method entityComplete, a status of exception and a reference to the
original input cas, but, what happen with child cas that were being
processed?. Are release to the casmultipler's caspool automatically?

I would appreciate the explanation

No service reply, after org.xml.sax.SAXParseException; Trying to serialize non-XML 1.0 character:

2016-11-21 Thread nelson rivera

I tried to process a input cas in service aggregate deployed in
uima-as. The annotations produced for annotators contains apparently
invalid character, after finalize the processing , when the framework
tries to send the reply, shows a org.xml.sax.SAXParseException error
serializing the cas and in the client side i get not any reply, the
listener associate it is not notified of the error, and the client
program stays waiting

the log of service aggregate error:

03:50:03.578 - 22:
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient:
WARNING: Service: XDataFileExtractorAggregate Runtime Exception
03:50:03.579 - 22:
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient:
WARNING:
org.apache.uima.aae.error.AsynchAEException:
org.xml.sax.SAXParseException; Trying to serialize non-XML 1.0
character: , 0x1 at offset 0 in string starting with
at 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.getSerializedCas(JmsOutputChannel.java:1258)
at 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.sendReply(JmsOutputChannel.java:793)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.sendReplyToRemoteClient(AggregateAnalysisEngineController_impl.java:2166)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient(AggregateAnalysisEngineController_impl.java:2335)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.finalStep(AggregateAnalysisEngineController_impl.java:1855)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.executeFlowStep(AggregateAnalysisEngineController_impl.java:2482)
at 
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.process(AggregateAnalysisEngineController_impl.java:1264)
at 
org.apache.uima.aae.handler.HandlerBase.invokeProcess(HandlerBase.java:118)
at 
org.apache.uima.aae.handler.input.ProcessResponseHandler.cancelTimerAndProcess(ProcessResponseHandler.java:117)
at 
org.apache.uima.aae.handler.input.ProcessResponseHandler.handleProcessResponseWithCASReference(ProcessResponseHandler.java:485)
at 
org.apache.uima.aae.handler.input.ProcessResponseHandler.handle(ProcessResponseHandler.java:767)
at 
org.apache.uima.aae.handler.HandlerBase.delegate(HandlerBase.java:149)
at 
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handle(ProcessRequestHandler_impl.java:1085)
at 
org.apache.uima.aae.spi.transport.vm.UimaVmMessageListener.onMessage(UimaVmMessageListener.java:107)
at 
org.apache.uima.aae.spi.transport.vm.UimaVmMessageDispatcher$1.run(UimaVmMessageDispatcher.java:70)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at 
org.apache.uima.aae.UimaAsThreadFactory$1.run(UimaAsThreadFactory.java:132)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.xml.sax.SAXParseException; Trying to serialize non-XML
1.0 character: , 0x1 at offset 0 in string starting with
at 
org.apache.uima.util.XMLSerializer$CharacterValidatingContentHandler.checkForInvalidXmlChars(XMLSerializer.java:374)
at 
org.apache.uima.util.XMLSerializer$CharacterValidatingContentHandler.startElement(XMLSerializer.java:275)
at 
org.apache.uima.cas.impl.XmiCasSerializer$XmiDocSerializer.startElement(XmiCasSerializer.java:1197)
at 
org.apache.uima.cas.impl.XmiCasSerializer$XmiDocSerializer.writeFsOrLists(XmiCasSerializer.java:711)
at 
org.apache.uima.cas.impl.XmiCasSerializer$XmiDocSerializer.writeFs(XmiCasSerializer.java:697)
at 
org.apache.uima.cas.impl.CasSerializerSupport$CasDocSerializer.encodeFS(CasSerializerSupport.java:)
at 
org.apache.uima.cas.impl.CasSerializerSupport$CasDocSerializer.encodeQueued(CasSerializerSupport.java:1015)
at 
org.apache.uima.cas.impl.XmiCasSerializer$XmiDocSerializer.writeFeatureStructures(XmiCasSerializer.java:563)
at 
org.apache.uima.cas.impl.CasSerializerSupport$CasDocSerializer.serialize(CasSerializerSupport.java:439)
at 
org.apache.uima.cas.impl.XmiCasSerializer.serialize(XmiCasSerializer.java:415)
at 
org.apache.uima.cas.impl.XmiCasSerializer.serialize(XmiCasSerializer.java:385)
at 
org.apache.uima.aae.UimaSerializer.serializeCasToXmi(UimaSerializer.java:145)
at 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.serializeCAS(JmsOutputChannel.java:244)
at 
org.apache.uima.adapter.jms.activemq.JmsOutputChannel.getSerializedCas(JmsOutputChannel.java:1243)
... 18 more

TERMINATE Action with org.xml.sax.SAXParseException in deserializeCasFromXmi function

2016-11-18 Thread nelson rivera

I have a service aggregate deploys in uima-as. When i send a input cas
with a text that contains apparently invalid character, occurs an
error deserializing the cas and the framework stops the aggregate
service

this is the complete stacktrace:

09:54:38.24 - 1:
org.apache.uima.adapter.jms.activemq.SpringContainerDeployer.doStartListeners:
INFO: Controller: XTokenizerAggregate Trying to Start Listener on
Endpoint: queue://XTokenizerAggregate Selector: Command=2000 OR
Command=2002 Broker: tcp://localhost:61616
09:54:38.193 - 1:
org.apache.uima.adapter.jms.activemq.SpringContainerDeployer.doStartListeners:
INFO: Controller: XTokenizerAggregate Trying to Start Listener on
Endpoint: queue://XTokenizerAggregate Selector: Command=2001 Broker:
tcp://localhost:61616
09:55:11.411 - 16:
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestFromRemoteClient:
WARNING: Service: XTokenizerAggregate Runtime Exception
09:55:11.411 - 16:
org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.handleProcessRequestFromRemoteClient:
WARNING:
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 585;
Character reference "

Re: Free instance of agreggate with cas multiplier in MultiprocessingAnalysisEngine

2016-11-18 Thread nelson rivera

yes I will do that with pleasure of cooperate with this great project

2016-11-09 16:18 GMT-05:00, Eddie Epstein <eaepst...@gmail.com>:
> Sounds like a bug in MultiprocessingAnalysisEngine_impl. Any chance you
> could simplify your scenario and attach it to a Jira issue against UIMA?
>
> On Wed, Nov 9, 2016 at 1:24 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> Not, for only one instance, the behavior is correct, and generate all
>> child cas required.
>>
>> 2016-11-09 9:40 GMT-05:00, Eddie Epstein <eaepst...@gmail.com>:
>> > Is behavior the same for single-threaded AnalysisEngine instantiation?
>> >
>> > On Tue, Nov 8, 2016 at 10:00 AM, nelson rivera
>> > <nelsonriver...@gmail.com
>> >
>> > wrote:
>> >
>> >> I have a aggregate analysis engine that contains a casmultiplier
>> >> annotator. I instantiate this aggregate with the interface
>> >> UIMAFramework.produceAnalysisEngine(specifier, 1, 0) for multithreaded
>> >> processing. The casmultiplier generate more than one cas for each
>> >> input CAS. The issue is that after first cas child, that i get with
>> >>
>> >>  JCasIterator casIterator =
>> >> analysisEngine.processAndOutputNewCASes(jcas);
>> >> while (casIterator.hasNext()) {
>> >>JCas outCas = casIterator.next();
>> >>...
>> >> outCas.release();
>> >> }
>> >>
>> >> after this first cas child, the MultiprocessingAnalysisEngine_impl
>> >> assumes that the instance of
>> >> AggregateAnalysisEngine that processes the request has ended, Y
>> >> entonces esta instancia es libre para procesar otra solicitud de otro
>> >> hilo, and it is not true, because missing child cas, producing
>> >> concurrency errors.
>> >>
>> >> What is the condition of a instance of MultiprocessingAnalysisEngine
>> >> that contains cas multiplier that generate many cas child for each
>> >> input Cas, for determine that it finish and is free?
>> >>
>> >
>>
>

Re: Free instance of agreggate with cas multiplier in MultiprocessingAnalysisEngine

2016-11-09 Thread nelson rivera

Not, for only one instance, the behavior is correct, and generate all
child cas required.

2016-11-09 9:40 GMT-05:00, Eddie Epstein <eaepst...@gmail.com>:
> Is behavior the same for single-threaded AnalysisEngine instantiation?
>
> On Tue, Nov 8, 2016 at 10:00 AM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> I have a aggregate analysis engine that contains a casmultiplier
>> annotator. I instantiate this aggregate with the interface
>> UIMAFramework.produceAnalysisEngine(specifier, 1, 0) for multithreaded
>> processing. The casmultiplier generate more than one cas for each
>> input CAS. The issue is that after first cas child, that i get with
>>
>>  JCasIterator casIterator =
>> analysisEngine.processAndOutputNewCASes(jcas);
>> while (casIterator.hasNext()) {
>>JCas outCas = casIterator.next();
>>...
>> outCas.release();
>> }
>>
>> after this first cas child, the MultiprocessingAnalysisEngine_impl
>> assumes that the instance of
>> AggregateAnalysisEngine that processes the request has ended, Y
>> entonces esta instancia es libre para procesar otra solicitud de otro
>> hilo, and it is not true, because missing child cas, producing
>> concurrency errors.
>>
>> What is the condition of a instance of MultiprocessingAnalysisEngine
>> that contains cas multiplier that generate many cas child for each
>> input Cas, for determine that it finish and is free?
>>
>

Free instance of agreggate with cas multiplier in MultiprocessingAnalysisEngine

2016-11-08 Thread nelson rivera

I have a aggregate analysis engine that contains a casmultiplier
annotator. I instantiate this aggregate with the interface
UIMAFramework.produceAnalysisEngine(specifier, 1, 0) for multithreaded
processing. The casmultiplier generate more than one cas for each
input CAS. The issue is that after first cas child, that i get with

 JCasIterator casIterator = analysisEngine.processAndOutputNewCASes(jcas);
while (casIterator.hasNext()) {
   JCas outCas = casIterator.next();
   ...
outCas.release();
}

after this first cas child, the MultiprocessingAnalysisEngine_impl
assumes that the instance of
AggregateAnalysisEngine that processes the request has ended, Y
entonces esta instancia es libre para procesar otra solicitud de otro
hilo, and it is not true, because missing child cas, producing
concurrency errors.

What is the condition of a instance of MultiprocessingAnalysisEngine
that contains cas multiplier that generate many cas child for each
input Cas, for determine that it finish and is free?

Re: java.lang.ClassCastException with binary SerializationStrategy

2016-11-03 Thread nelson rivera

Yes with xmiCas serialization everything works fine. The client and
the input Cas have identical type system definitions, because i get
the cas from  UimaAsynchronousEngine with the line
"asynchronousEngine.getCAS()", any idea of problem

2016-11-03 16:49 GMT-04:00, Eddie Epstein <eaepst...@gmail.com>:
> Hi,
>
> Binary serialization for a service call only works if the client and
> service have identical type system definitions. Have you confirmed
> everything works with the default XmiCas serialization?
>
> Eddie
>
> On Thu, Nov 3, 2016 at 3:51 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> I want to consume a service uima-as aggregate, the service have all
>> delegates co-located, with format binary for serialization, I set
>> SerializationStrategy as "binary" in the cliente side to the
>> application context map used to pass initialization parameters. But
>> when process i get this exception in te service uima-as:
>>
>>
>> 01:42:00.679 - 14:
>> org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.
>> handleProcessRequestFromRemoteClient:
>> WARNING:
>> java.lang.ClassCastException: org.apache.uima.cas.impl.AnnotationImpl
>> cannot be cast to org.apache.uima.cas.SofaFS
>> at org.apache.uima.cas.impl.CASImpl.getSofa(CASImpl.java:834)
>> at
>> org.apache.uima.cas.impl.FSIndexRepositoryImpl.ll_addFS_common(
>> FSIndexRepositoryImpl.java:2786)
>> at org.apache.uima.cas.impl.FSIndexRepositoryImpl.ll_
>> addFS(FSIndexRepositoryImpl.java:2763)
>> at org.apache.uima.cas.impl.FSIndexRepositoryImpl.addFS(
>> FSIndexRepositoryImpl.java:2068)
>> at org.apache.uima.cas.impl.CASImpl.reinitIndexedFSs(
>> CASImpl.java:1916)
>> at org.apache.uima.cas.impl.CASImpl.reinit(CASImpl.java:1640)
>> at org.apache.uima.cas.impl.CASImpl.reinit(CASImpl.java:1393)
>> at org.apache.uima.cas.impl.CASImpl.reinit(CASImpl.java:1386)
>> at org.apache.uima.cas.impl.Serialization.deserializeCAS(
>> Serialization.java:187)
>> at org.apache.uima.aae.UimaSerializer.deserializeCasFromBinary(
>> UimaSerializer.java:223)
>> at org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.
>> deserializeCASandRegisterWithCache(ProcessRequestHandler_impl.java:229)
>> at org.apache.uima.aae.handler.input.ProcessRequestHandler_impl.
>> handleProcessRequestFromRemoteClient(ProcessRequestHandler_impl.java:531)
>> at org.apache.uima.aae.handler.input.ProcessRequestHandler_
>> impl.handle(ProcessRequestHandler_impl.java:1062)
>> at org.apache.uima.aae.handler.input.MetadataRequestHandler_
>> impl.handle(MetadataRequestHandler_impl.java:78)
>> at org.apache.uima.adapter.jms.activemq.JmsInputChannel.
>> onMessage(JmsInputChannel.java:731)
>> at
>> org.springframework.jms.listener.AbstractMessageListenerContain
>> er.doInvokeListener(AbstractMessageListenerContainer.java:689)
>> at
>> org.springframework.jms.listener.AbstractMessageListenerContain
>> er.invokeListener(AbstractMessageListenerContainer.java:649)
>> at
>> org.springframework.jms.listener.AbstractMessageListenerContain
>> er.doExecuteListener(AbstractMessageListenerContainer.java:619)
>> at
>> org.springframework.jms.listener.AbstractPollingMessageListener
>> Container.doReceiveAndExecute(AbstractPollingMessageListener
>> Container.java:307)
>> at
>> org.springframework.jms.listener.AbstractPollingMessageListener
>> Container.receiveAndExecute(AbstractPollingMessageListener
>> Container.java:245)
>> at
>> org.springframework.jms.listener.DefaultMessageListenerContaine
>> r$AsyncMessageListenerInvoker.invokeListener(
>> DefaultMessageListenerContainer.java:1144)
>> at
>> org.springframework.jms.listener.DefaultMessageListenerContaine
>> r$AsyncMessageListenerInvoker.executeOngoingLoop(
>> DefaultMessageListenerContainer.java:1136)
>> at
>> org.springframework.jms.listener.DefaultMessageListenerContaine
>> r$AsyncMessageListenerInvoker.run(DefaultMessageListenerContaine
>> r.java:1033)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(
>> ThreadPoolExecutor.java:1145)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
>> ThreadPoolExecutor.java:615)
>> at org.apache.uima.aae.UimaAsThreadFactory$1.run(
>> UimaAsThreadFactory.java:132)
>> at java.lang.Thread.run(Thread.java:745)
>>
>

Re: Broken conections after ACTIVEMQ restart

2016-11-01 Thread nelson rivera

 not refresh JMS Connection for destination
'queue://XClusterAnalyzerAggregate' - silently retrying in 5 ms.
Cause: Could not connect to broker URL: tcp://localhost:61616. Reason:
java.net.ConnectException: Connection refused

2016-10-27 14:29 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Nelson, try this fix:
> https://repository.apache.org/content/repositories/snapshots/org/apache/uima/uima-as/2.9.0-SNAPSHOT/uima-as-2.9.0-20161027.181519-7.tar.gz
>
> Keep in mind that if you bounce a broker while a CAS is being processed in
> a service, the client  will not be able to get the input CAS back nor will
> it get child CASes. Both the input and child CAS will be thrown away by the
> service due to undeliverable destination (old temp queue). The code will
> actually stop the Cas Multiplier from producing child CASes if it detects
> an undeliverable destination.  You need a process timeout on the client
> side to deal with that. When a broker is bounced, both the client and a
> service will detect a new broker instance, kill its old temp queue
> listeners and create new ones so that subsequent processing can take place.
>
> Jerry
>
> On Thu, Oct 27, 2016 at 1:19 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> Hi, I would like know if you have worked in the solution of this
>> theme, related with recovered of queues in service cas multiplier,
>> after restart uima-as broker, specifically temp queue. If you have a
>> snapshot with this. Thanks
>>
>> 2016-09-28 10:34 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
>> > Nelson, yes I think there is a problem in the UIMA-AS. First, there is
>> > evidence that a service
>> > is trying to use a stale temp queue:
>> >
>> > tcp://localhost:61616 Reason: javax.jms.InvalidDestinationException:
>> > Cannot use a Temporary destination from another Connection.
>> >
>> >
>> > Also, I think there is another problem related to recovery of temp
>> > queues
>> > in the service.
>> > The service cas multiplier uses multiple queues:
>> > 1) input queue - receives GetMeta and Process requests from a client
>> > 2) temp queue - receives FreeCas requests from a client. This is only
>> > created when a service
>> > is a Cas Multiplier. This is used to free CASes in a cas
>> > multiplier.
>> >
>> > The input queue listener recovers the connection since it received an
>> input
>> > CAS. I think the
>> > temp queue is not recovered and this leads to repeated retries.
>> >
>> > I will work on fixing this today and let you know when this is ready. I
>> > will also create a new
>> > snapshot for you to try.
>> >
>> > Thanks for finding these problems.
>> >
>> > - jerry
>> >
>> >
>> > On Wed, Sep 28, 2016 at 10:12 AM, nelson rivera <
>> nelsonriver...@gmail.com>
>> > wrote:
>> >
>> >> ok, only show you the result of last test.
>> >> Now in my test  with uima-as-2.9.0, after complete restart of the
>> >> Broker UIMA-AS log show
>> >>
>> >> 09:51:01.731 - 19:
>> >> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.
>> >> handleListenerSetupFailure:
>> >> WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
>> >> Connection to Broker: tcp://localhost:61616 - Ready to Process Again
>> >> 09:51:01.740 - 46:
>> >> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.
>> >> handleListenerSetupFailure:
>> >> WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
>> >> Connection to Broker: tcp://localhost:61616 - Ready to Process Again
>> >> 09:51:01.747 - 15:
>> >> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.
>> >> handleListenerSetupFailure:
>> >> WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
>> >> Connection to Broker: tcp://localhost:61616 - Ready to Process Again
>> >> 09:51:01.773 - 14:
>> >> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> >> ainer.onException:
>> >> WARNING: Service: Aggregate Cluster Analyzer Runtime Exception
>> >> 09:51:01.773 - 14:
>> >> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> >> ainer.onException:
>> >> WARNING: Service: Aggregate Cluster Analyzer Runtime Exception
>> >> 09:51:01.774 - 1

Re: Broken conections after ACTIVEMQ restart

2016-10-27 Thread nelson rivera

Hi, I would like know if you have worked in the solution of this
theme, related with recovered of queues in service cas multiplier,
after restart uima-as broker, specifically temp queue. If you have a
snapshot with this. Thanks

2016-09-28 10:34 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Nelson, yes I think there is a problem in the UIMA-AS. First, there is
> evidence that a service
> is trying to use a stale temp queue:
>
> tcp://localhost:61616 Reason: javax.jms.InvalidDestinationException:
> Cannot use a Temporary destination from another Connection.
>
>
> Also, I think there is another problem related to recovery of temp queues
> in the service.
> The service cas multiplier uses multiple queues:
> 1) input queue - receives GetMeta and Process requests from a client
> 2) temp queue - receives FreeCas requests from a client. This is only
> created when a service
> is a Cas Multiplier. This is used to free CASes in a cas multiplier.
>
> The input queue listener recovers the connection since it received an input
> CAS. I think the
> temp queue is not recovered and this leads to repeated retries.
>
> I will work on fixing this today and let you know when this is ready. I
> will also create a new
> snapshot for you to try.
>
> Thanks for finding these problems.
>
> - jerry
>
>
> On Wed, Sep 28, 2016 at 10:12 AM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> ok, only show you the result of last test.
>> Now in my test  with uima-as-2.9.0, after complete restart of the
>> Broker UIMA-AS log show
>>
>> 09:51:01.731 - 19:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.
>> handleListenerSetupFailure:
>> WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
>> Connection to Broker: tcp://localhost:61616 - Ready to Process Again
>> 09:51:01.740 - 46:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.
>> handleListenerSetupFailure:
>> WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
>> Connection to Broker: tcp://localhost:61616 - Ready to Process Again
>> 09:51:01.747 - 15:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.
>> handleListenerSetupFailure:
>> WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
>> Connection to Broker: tcp://localhost:61616 - Ready to Process Again
>> 09:51:01.773 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> WARNING: Service: Aggregate Cluster Analyzer Runtime Exception
>> 09:51:01.773 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> WARNING: Service: Aggregate Cluster Analyzer Runtime Exception
>> 09:51:01.774 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> WARNING: Jms Listener Failed. Endpoint: XClusterAnalyzerAggregate
>> Managed By: tcp://localhost:61616 Reason: javax.jms.JMSException:
>> java.io.EOFException
>> 09:51:01.774 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.
>> handleListenerSetupFailure:
>> WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Unable To
>> Connect To Broker: tcp://localhost:61616 Retrying Until Successful ...
>> 09:51:01.777 - 19:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> WARNING: Service: Aggregate Cluster Analyzer Runtime Exception
>> 09:51:01.777 - 19:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> WARNING: Jms Listener Failed. Endpoint:
>> ID:nelson-H81-M1-43454-1475070490428-1:1:1 Managed By:
>> tcp://localhost:61616 Reason: javax.jms.InvalidDestinationException:
>> Cannot use a Temporary destination from another Connection.
>>
>> this lines are continue to repeat in the log indefinitely. And after
>> this have the same problem when send input Cas at the service
>>
>> 2016-09-28 9:27 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
>> > Nelson, I will investigate your use case and let you know.
>> >
>> > -jerry
>> >
>> > On Wed, Sep 28, 2016 at 9:01 AM, nelson rivera
>> > <nelsonriver...@gmail.com
>> >
>> > wrote:
>> >
>> >> Thank you for describe  how UIMA-AS works, it is very helpful. But my
>> >> scenario is not restart the broker while the uima-as service works on
>> >> input CAS
>> >>
>> >> my scena

Re: Broken conections after ACTIVEMQ restart

2016-09-28 Thread nelson rivera

ok, only show you the result of last test.
Now in my test  with uima-as-2.9.0, after complete restart of the
Broker UIMA-AS log show

09:51:01.731 - 19:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure:
WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
Connection to Broker: tcp://localhost:61616 - Ready to Process Again
09:51:01.740 - 46:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure:
WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
Connection to Broker: tcp://localhost:61616 - Ready to Process Again
09:51:01.747 - 15:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure:
WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Recovered
Connection to Broker: tcp://localhost:61616 - Ready to Process Again
09:51:01.773 - 14:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException:
WARNING: Service: Aggregate Cluster Analyzer Runtime Exception
09:51:01.773 - 14:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException:
WARNING: Service: Aggregate Cluster Analyzer Runtime Exception
09:51:01.774 - 14:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException:
WARNING: Jms Listener Failed. Endpoint: XClusterAnalyzerAggregate
Managed By: tcp://localhost:61616 Reason: javax.jms.JMSException:
java.io.EOFException
09:51:01.774 - 14:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.handleListenerSetupFailure:
WARNING: Uima AS Service:Aggregate Cluster Analyzer Listener Unable To
Connect To Broker: tcp://localhost:61616 Retrying Until Successful ...
09:51:01.777 - 19:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException:
WARNING: Service: Aggregate Cluster Analyzer Runtime Exception
09:51:01.777 - 19:
org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.onException:
WARNING: Jms Listener Failed. Endpoint:
ID:nelson-H81-M1-43454-1475070490428-1:1:1 Managed By:
tcp://localhost:61616 Reason: javax.jms.InvalidDestinationException:
Cannot use a Temporary destination from another Connection.

this lines are continue to repeat in the log indefinitely. And after
this have the same problem when send input Cas at the service

2016-09-28 9:27 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Nelson, I will investigate your use case and let you know.
>
> -jerry
>
> On Wed, Sep 28, 2016 at 9:01 AM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> Thank you for describe  how UIMA-AS works, it is very helpful. But my
>> scenario is not restart the broker while the uima-as service works on
>> input CAS
>>
>> my scenario is
>> 1- Start Broker and UIMA-AS aggregate service
>>
>> 2- Complete Restart of the Broker  (without restart the service).
>> UIMA-AS log show the lines that previously i said you:
>> "Jms Listener Failed." 
>> "The Session is closed." ...
>> "The Consumer is closed." ...
>>
>> I do not see in my uima-as log the lines that you say in your test
>> after broker is bounced:
>> Listeners reconnect:
>>  INFO | Successfully refreshed JMS Connection
>>  INFO | Successfully refreshed JMS Connection
>> In my case (uima-as 2.8.1) seems to be a problem with reestablishing
>> the connection to the broker after restart.
>>
>> 4- Then in this point, after the broker was restarted completely,
>> uima-as client sends a CAS to UIMA-AS aggregate service. And for this
>> petition UIMA-AS client receive the parent CAS, but not child CAS.
>>
>> In this moment i will trys with uima-as-2.9.0 snapshot
>>
>>
>> 2016-09-27 15:33 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
>> > Nelson, in my scenario I do have a Cas Multiplier which produces a
>> > child
>> > CAS for each input CAS. For the purpose of this
>> > test its not important how many internal delegates there are in a
>> pipeline.
>> > The service is configured as a Cas Multiplier
>> > and it does send child CASes when a broker is running.
>> >
>> > The problem is that once the input CAS is received, its reply queue is
>> > bound to a specific temp reply queue. When a broker is
>> > bounced, that queue is not valid anymore and cant be used to return
>> > child
>> > CASes nor the input CAS. To guard against such
>> > cases you need to use timeouts on the client side.
>> >
>> > Like I said in my previous email I dont get how an input CAS can be
>> > returned back to the client after a broker bounce. This should
>> > no

Re: Broken conections after ACTIVEMQ restart

2016-09-28 Thread nelson rivera

Thank you for describe  how UIMA-AS works, it is very helpful. But my
scenario is not restart the broker while the uima-as service works on
input CAS

my scenario is
1- Start Broker and UIMA-AS aggregate service

2- Complete Restart of the Broker  (without restart the service).
UIMA-AS log show the lines that previously i said you:
"Jms Listener Failed." 
"The Session is closed." ...
"The Consumer is closed." ...

I do not see in my uima-as log the lines that you say in your test
after broker is bounced:
Listeners reconnect:
 INFO | Successfully refreshed JMS Connection
 INFO | Successfully refreshed JMS Connection
In my case (uima-as 2.8.1) seems to be a problem with reestablishing
the connection to the broker after restart.

4- Then in this point, after the broker was restarted completely,
uima-as client sends a CAS to UIMA-AS aggregate service. And for this
petition UIMA-AS client receive the parent CAS, but not child CAS.

In this moment i will trys with uima-as-2.9.0 snapshot


2016-09-27 15:33 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Nelson, in my scenario I do have a Cas Multiplier which produces a child
> CAS for each input CAS. For the purpose of this
> test its not important how many internal delegates there are in a pipeline.
> The service is configured as a Cas Multiplier
> and it does send child CASes when a broker is running.
>
> The problem is that once the input CAS is received, its reply queue is
> bound to a specific temp reply queue. When a broker is
> bounced, that queue is not valid anymore and cant be used to return child
> CASes nor the input CAS. To guard against such
> cases you need to use timeouts on the client side.
>
> Like I said in my previous email I dont get how an input CAS can be
> returned back to the client after a broker bounce. This should
> not happen since its temp queue does not exist in a new broker.
>
> I am still looking at this scenario as I don't like what I see in the
> service log. I think there might be a bug in the UIMA-AS but I am
> still investigating. Bug or not, what I described above is how UIMA-AS
> works. You should not expect any replies from a service
> working on a CAS that was sent through a broker that is bounced before a
> reply.
>
> -jerry
>
>
> On Tue, Sep 27, 2016 at 3:18 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> My service  is a aggregate analysis engine that receives input CAS
>> with the direcction of a directory of documents, the first component
>> is a MultiplerCas that for each document generate a child CAS, each
>> child CAS continues the flow that are other primitive annotators
>> (primitive annotators in c++ that can throw exceptions), then exists
>> other MultiplerCas that acts as Merger, waiting  the complete
>> processing of each child CAS and finally generate a child CAS where
>> each child CAS previously processed is a view of CAS, this a child CAS
>> that is composed of view continúa el flujo a otro AE, que espera un
>> CAS de esta manera.
>> I will send you my uima-as descriptor,  to understand better my
>> service. All delegates are co-located.
>>
>> i will trys with uima-as-2.9.0 snapshot how you say, to see how it
>> behaves
>>
>> 2016-09-27 14:27 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
>> > I was able to stage this scenario in which an aggregate service cas
>> > multiplier receives a single input CAS and
>> > produces a child CAS.
>> >
>> > Scenario:
>> > 1) Service receives input CAS
>> > 2) CasMultiplier generates a child CAS
>> > 3) AE.process() is called (child CAS) and it sleeps for awhile
>> > 4) Broker is shutdown
>> > 5) AE.process() awakes from sleep
>> > 6) Uima-AS tries to deliver child CAS to a remote client
>> > 7) Connection is invalid so the child CAS is dropped
>> > 8) Broker is restarted
>> > 9) Listeners reconnect:
>> >  INFO | Successfully refreshed JMS Connection
>> >  INFO | Successfully refreshed JMS Connection
>> > 10) Broker log shows:
>> > WARN  Service- Async error occurred:
>> > org.apache.activemq.DestinationDoesNotExistException: The destination
>> > temp-queue://ID:bluejws65-53920-1474997439574-8:1:1 does not exist.
>> > WARN  Service- Async error occurred:
>> > org.apache.activemq.DestinationDoesNotExistException: The destination
>> > temp-queue://ID:bluejws65-53920-1474997439574-8:1:1 does not exist.
>> >
>> > The service failed to send a reply.Nothing is delivered to a client as
>> > expected. This is the confusing part since you see a p

Re: Broken conections after ACTIVEMQ restart

2016-09-27 Thread nelson rivera

My service  is a aggregate analysis engine that receives input CAS
with the direcction of a directory of documents, the first component
is a MultiplerCas that for each document generate a child CAS, each
child CAS continues the flow that are other primitive annotators
(primitive annotators in c++ that can throw exceptions), then exists
other MultiplerCas that acts as Merger, waiting  the complete
processing of each child CAS and finally generate a child CAS where
each child CAS previously processed is a view of CAS, this a child CAS
that is composed of view continúa el flujo a otro AE, que espera un
CAS de esta manera.
I will send you my uima-as descriptor,  to understand better my
service. All delegates are co-located.

i will trys with uima-as-2.9.0 snapshot how you say, to see how it behaves

http://uima.apache.org/resourceSpecifier;>
  
AnalyzerAE Deploy Descriptor
Deploys AnalyzerAE

Re: Broken conections after ACTIVEMQ restart

2016-09-27 Thread nelson rivera

My service  is a aggregate analysis engine that receives input CAS
with the direcction of a directory of documents, the first component
is a MultiplerCas that for each document generate a child CAS, each
child CAS continues the flow that are other primitive annotators
(primitive annotators in c++ that can throw exceptions), then exists
other MultiplerCas that acts as Merger, waiting  the complete
processing of each child CAS and finally generate a child CAS where
each child CAS previously processed is a view of CAS, this a child CAS
that is composed of view continúa el flujo a otro AE, que espera un
CAS de esta manera.
I will send you my uima-as descriptor,  to understand better my
service. All delegates are co-located.

i will trys with uima-as-2.9.0 snapshot how you say, to see how it behaves

2016-09-27 14:27 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> I was able to stage this scenario in which an aggregate service cas
> multiplier receives a single input CAS and
> produces a child CAS.
>
> Scenario:
> 1) Service receives input CAS
> 2) CasMultiplier generates a child CAS
> 3) AE.process() is called (child CAS) and it sleeps for awhile
> 4) Broker is shutdown
> 5) AE.process() awakes from sleep
> 6) Uima-AS tries to deliver child CAS to a remote client
> 7) Connection is invalid so the child CAS is dropped
> 8) Broker is restarted
> 9) Listeners reconnect:
>  INFO | Successfully refreshed JMS Connection
>  INFO | Successfully refreshed JMS Connection
> 10) Broker log shows:
> WARN  Service- Async error occurred:
> org.apache.activemq.DestinationDoesNotExistException: The destination
> temp-queue://ID:bluejws65-53920-1474997439574-8:1:1 does not exist.
> WARN  Service- Async error occurred:
> org.apache.activemq.DestinationDoesNotExistException: The destination
> temp-queue://ID:bluejws65-53920-1474997439574-8:1:1 does not exist.
>
> The service failed to send a reply.Nothing is delivered to a client as
> expected. This is the confusing part since you see a parent CAS being sent
> to a client. I just cant imagine how this is possible.
>
> When a service receives an input CAS in a message, it extracts a JMS
> replyTo object which is a JMS temp queue and stores in an internal cache
> until it is time to send a reply. Temp queues are transient and unique each
> time one is created.
>
> If the broker dies and subsequently restarts, the cached replyTo queue
> object is invalid (temp queue no longer exist) which leads to
> "Async error occurred:
> org.apache.activemq.DestinationDoesNotExistException" as shows above.
>
> In the service log I see a bunch of these exceptions:
>
> 02:05:46.574 - 56:
> org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.openChannel:
> WARNING: Service: Test Aggregate TAE Unable to Open Connection To Broker:
> tcp://localhost:61616?wireFormat.maxInactivityDuration=0 - Silently
> Retrying ...
> 02:05:46.574 - 56:
> org.apache.uima.adapter.jms.activemq.JmsEndpointConnection_impl.openChannel:
> WARNING:
> javax.jms.JMSException: Could not connect to broker URL:
> tcp://localhost:61616?wireFormat.maxInactivityDuration=0. Reason:
> java.net.ConnectException: Connection refused
>
> This is *after* the service is restarted so there seems to be a problem
> with reestablishing the connection to a new broker.
> I am still investigating that part. I just am confused how you are able to
> see a reply in the client.
>
> -Jerry
>
>
> On Tue, Sep 27, 2016 at 1:13 PM, Jaroslaw Cwiklik <uim...@gmail.com> wrote:
>
>> From what I understand there are two issues:
>>
>> 1) Why service JMS listeners are not reconnecting when a broker is
>> bounced. This
>> should be done by default. The 2.9.0 snapshot may address this since
>> a
>> listener
>> uses newer AMQ jars (5.14.0)
>>
>> 2) What happens to a child CAS when a Broker disappears and the service
>> wants
>> to deliver it to a client that is not reachable. I need to
>> investigate
>> this part. I think
>> such CAS is dropped but that should be reflected in a log and also
>> the
>> input CAS
>> should be marked as failed. Again something for me to investigate.
>>
>> I will try to set up a test to see if I can create the scenario.It will
>> take me a bit of time
>> to set this up but I will let you know what happens.
>>
>> -jerry
>>
>> On Tue, Sep 27, 2016 at 12:42 PM, Jaroslaw Cwiklik <uim...@gmail.com>
>> wrote:
>>
>>> Here is the uima-as 2.9.0-SNAPSHOT to try:
>>> https://repository.apache.org/content/repositories/snapshots
>>> /org/apache/uima/uima-as/2.9.0-SNAPSH

Re: Broken conections after ACTIVEMQ restart

2016-09-27 Thread nelson rivera

I was testing with AMQ broker 5.14.0 and i get the same error. not
appears to be broker
issues, appears to be uima-as issues. Any other idea, i am stagnant at work

2016-09-22 13:04 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Can you install AMQ broker 5.14.0 to see if this is related to broker
> issues.
>
> -jerry
>
> On Thu, Sep 22, 2016 at 11:29 AM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> just like that, the parent CAS comes back but the child CAS doesnt.
>>
>> And the child CAS if processed, because  the  uima-as log shows the
>> lines of the other annotators primitive of the flow processing the
>> child CAS, but not comes back to UIMA-AS client.
>>
>> uima-as log only shows
>> "Jms Listener Failed. Endpoint:
>> temp-queue://ID:localhsot-H81-M1-33610-1474481197190-1:1:1 Managed By:
>> tcp://localhost:61616 Reason: javax.jms.JMSException:
>> java.io.EOFException" 
>> ADVERTENCIA: Jms Listener Failed. Endpoint: XClusterAnalyzerAggregate
>> Managed By: tcp://localhost:61616 Reason:
>> javax.jms.IllegalStateException: The Consumer is closed..
>>
>> The CAS is send to service after restart the Broker, and how say
>> parent CAS comes back but the child CAS doesnt. And if i try quiesce
>> the Aggregate Service console shows : "Quiescing UIMA-AS Service.
>> Remaining Number of CASes to Process:1".  I suppose that is the child
>> CAS.
>>
>> the client if can send more CASes to the service, but not receive
>> response, for each CAS send after the one CAS that was send after
>> restart broker (for which  parent CAS comes back but the child CAS
>> doesnt)  not comes back parent CAS or child CAS.
>>
>> More specific:
>> scenario 1:
>> 1- Start Broker and UIMA-AS aggregate service. Everything is fine.
>>
>> 2- Restart Broker (without restart the service).  UIMA-AS log show  :
>> "Jms Listener Failed." 
>> 3- Client sends a CAS to UIMA-AS aggregate service.(The parent CAS
>> comes back but the child CAS doesnt, to the uima-as client.)
>> If i try quiesce the Aggregate Service console shows : "Quiescing
>> UIMA-AS Service. Remaining Number of CASes to Process:1"
>>
>> scenario 2:
>> 1- Start Broker and UIMA-AS aggregate service. Everything is fine.
>>
>> 2- Restart Broker (without restart the service).  UIMA-AS log show  :
>> "Jms Listener Failed." 
>> 3- Client sends a CAS to UIMA-AS aggregate service.(The parent CAS
>> comes back but the child CAS doesnt, to the uima-as client)
>> 4- Client  sends another CAS to UIMA-AS aggregate service.(not comes
>> back parent CAS or child CAS , to the uima-as client)
>> 5- Client  sends another CAS to UIMA-AS aggregate service.(not comes
>> back parent CAS or child CAS , to the uima-as client)
>>  If i try quiesce the Aggregate Service  console shows: "Quiescing
>> UIMA-AS Service. Remaining Number of CASes to Process:5"
>>
>>
>>
>>
>>
>> 2016-09-22 10:50 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
>> > When a parent CAS comes back (after broker is restored), can the client
>> > send more CASes to the service and receive responses? I am trying to
>> > determine what the real problem is here.
>> >
>> > 1) JMS Listener not recovering connection
>> > 2) UIMA-AS is not handling CAS reply failures when broker connection is
>> > stale
>> >
>> > -jerry
>> >
>> > On Thu, Sep 22, 2016 at 10:38 AM, Jaroslaw Cwiklik <uim...@gmail.com>
>> > wrote:
>> >
>> >> Strange. You say that the parent CAS comes back but the child CAS
>> doesnt.
>> >> Are there any exceptions in the service log? Perhaps the service is
>> >> unable
>> >> to send the child CAS due to missing broker. There should be something
>> in
>> >> the uima-as log about this.
>> >>
>> >> -jerry
>> >>
>> >> On Thu, Sep 22, 2016 at 10:19 AM, nelson rivera
>> >> <nelsonriver...@gmail.com>
>> >> wrote:
>> >>
>> >>> Yes, it is supposed to do the service, given a
>> >>> CAS it produces a child CAS and and this CAS continue in the flow,
>> >>> that are other primitive annotators. And I expected that the child
>> >>> CAS
>> >>> will sent to  UIMA-AS client, but not do.
>> >>>
>> >>> the scenario:
>> >>> 1- Start Broker and UIMA-AS aggregate service
>>

Re: Broken conections after ACTIVEMQ restart

2016-09-22 Thread nelson rivera

just like that, the parent CAS comes back but the child CAS doesnt.

And the child CAS if processed, because  the  uima-as log shows the
lines of the other annotators primitive of the flow processing the
child CAS, but not comes back to UIMA-AS client.

uima-as log only shows
"Jms Listener Failed. Endpoint:
temp-queue://ID:localhsot-H81-M1-33610-1474481197190-1:1:1 Managed By:
tcp://localhost:61616 Reason: javax.jms.JMSException:
java.io.EOFException" 
ADVERTENCIA: Jms Listener Failed. Endpoint: XClusterAnalyzerAggregate
Managed By: tcp://localhost:61616 Reason:
javax.jms.IllegalStateException: The Consumer is closed..

The CAS is send to service after restart the Broker, and how say
parent CAS comes back but the child CAS doesnt. And if i try quiesce
the Aggregate Service console shows : "Quiescing UIMA-AS Service.
Remaining Number of CASes to Process:1".  I suppose that is the child
CAS.

the client if can send more CASes to the service, but not receive
response, for each CAS send after the one CAS that was send after
restart broker (for which  parent CAS comes back but the child CAS
doesnt)  not comes back parent CAS or child CAS.

More specific:
scenario 1:
1- Start Broker and UIMA-AS aggregate service. Everything is fine.

2- Restart Broker (without restart the service).  UIMA-AS log show  :
"Jms Listener Failed." 
3- Client sends a CAS to UIMA-AS aggregate service.(The parent CAS
comes back but the child CAS doesnt, to the uima-as client.)
If i try quiesce the Aggregate Service console shows : "Quiescing
UIMA-AS Service. Remaining Number of CASes to Process:1"

scenario 2:
1- Start Broker and UIMA-AS aggregate service. Everything is fine.

2- Restart Broker (without restart the service).  UIMA-AS log show  :
"Jms Listener Failed." 
3- Client sends a CAS to UIMA-AS aggregate service.(The parent CAS
comes back but the child CAS doesnt, to the uima-as client)
4- Client  sends another CAS to UIMA-AS aggregate service.(not comes
back parent CAS or child CAS , to the uima-as client)
5- Client  sends another CAS to UIMA-AS aggregate service.(not comes
back parent CAS or child CAS , to the uima-as client)
 If i try quiesce the Aggregate Service  console shows: "Quiescing
UIMA-AS Service. Remaining Number of CASes to Process:5"

2016-09-22 10:50 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> When a parent CAS comes back (after broker is restored), can the client
> send more CASes to the service and receive responses? I am trying to
> determine what the real problem is here.
>
> 1) JMS Listener not recovering connection
> 2) UIMA-AS is not handling CAS reply failures when broker connection is
> stale
>
> -jerry
>
> On Thu, Sep 22, 2016 at 10:38 AM, Jaroslaw Cwiklik <uim...@gmail.com>
> wrote:
>
>> Strange. You say that the parent CAS comes back but the child CAS doesnt.
>> Are there any exceptions in the service log? Perhaps the service is
>> unable
>> to send the child CAS due to missing broker. There should be something in
>> the uima-as log about this.
>>
>> -jerry
>>
>> On Thu, Sep 22, 2016 at 10:19 AM, nelson rivera
>> <nelsonriver...@gmail.com>
>> wrote:
>>
>>> Yes, it is supposed to do the service, given a
>>> CAS it produces a child CAS and and this CAS continue in the flow,
>>> that are other primitive annotators. And I expected that the child CAS
>>> will sent to  UIMA-AS client, but not do.
>>>
>>> the scenario:
>>> 1- Start Broker and UIMA-AS aggregate service
>>> 2- Client sends a CAS to UIMA-AS aggregate service to verify
>>> everything is fine. The process is correct.
>>>
>>> 3- Restart Broker (without restart the service).  UIMA-AS log show  :
>>> "Jms Listener Failed." 
>>> 4- Client sends a CAS to UIMA-AS aggregate service
>>>
>>> UIMA-AS client receive the parent CAS, but not child CAS.
>>>
>>> Thank  for you quick reply
>>>
>>> 2016-09-22 9:48 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
>>> > Can you clarify if the UIMA-AS service is a Cas Multiplier. Meaning
>>> given a
>>> > CAS it produces child CASes
>>> > which are then sent to UIMA-AS client. Is this what this service is
>>> > supposed to do if the broker is running?
>>> >
>>> > Can you confirm the scenario:
>>> > 1) Client sends a CAS to UIMA-AS aggregate service
>>> > 2) Service receives the CAS
>>> > 3) Broker dies
>>> > 4) Broker is restarted
>>> >
>>> > Does the UIMA-AS client receive the CAS back in a reply when a broker
>>> > is
>>> > res

Re: Broken conections after ACTIVEMQ restart

2016-09-21 Thread nelson rivera

I'm using UIMA-AS 2.8.1, any idea that what happen?

2016-09-21 16:09 GMT-04:00, Jaroslaw Cwiklik <uim...@gmail.com>:
> Which version of UIMA-AS are you using?
>
> -Jerry
>
> On Wed, Sep 21, 2016 at 3:42 PM, nelson rivera <nelsonriver...@gmail.com>
> wrote:
>
>> When start ActiveMQ and deploys an annotator as service, processing is
>> executed correctly, but  when the broker is stopped and subsequently
>> restarted. UIMA-AS log show the lines below  and after this the api
>> client uima-as is not notified in the listener when a cas is
>> processed, any more.
>> can help me?:
>>
>> 02:08:25.570 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> ADVERTENCIA: Service: Aggregate Cluster Analyzer Runtime Exception
>> 02:08:25.570 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> ADVERTENCIA: Jms Listener Failed. Endpoint: XClusterAnalyzerAggregate
>> Managed By: tcp://localhost:61616 Reason: javax.jms.JMSException:
>> java.io.EOFException
>> 02:08:25.570 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.
>> handleListenerSetupFailure:
>> ADVERTENCIA: Uima AS Service:Aggregate Cluster Analyzer Listener
>> Unable To Connect To Broker: tcp://localhost:61616 Retrying ...
>> QueueFailure: ADVERTENCIA: Jms Listener Failed. Endpoint:
>> temp-queue://ID:localhost-H81-M1-33610-1474481197190-1:1:1 Managed By:
>> tcp://localhost:61616 Reason: javax.jms.JMSException:
>> java.io.EOFException
>> 02:09:02.222 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerContainer.
>> handleListenerSetupFailure:
>> ADVERTENCIA: Uima AS Service:Aggregate Cluster Analyzer Listener
>> Established Connection to Broker: tcp://localhost:61616
>>
>> 02:09:02.317 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> ADVERTENCIA: Service: Aggregate Cluster Analyzer Runtime Exception
>> 02:09:02.317 - 14:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> ADVERTENCIA: Jms Listener Failed. Endpoint: XClusterAnalyzerAggregate
>> Managed By: tcp://localhost:61616 Reason:
>> org.apache.activemq.ConnectionClosedException: The connection is
>> already closed02:09:02.356 - 15:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> ADVERTENCIA: Service: Aggregate Cluster Analyzer Runtime Exception
>> 02:09:02.357 - 15:
>> org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
>> ainer.onException:
>> ADVERTENCIA: Jms Listener Failed. Endpoint: XClusterAnalyzerAggregate
>> Managed By: tcp://localhost:61616 Reason:
>> javax.jms.IllegalStateException: The Consumer is closed.
>>
>

50 matches

Mail list logo