Re: Possible cause of nullPointerException in casmultiplier?

[Jaroslaw Cwiklik]

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 
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 :
> > 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 :
> >> > 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
> >> > 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 :
> >> >> 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.PrimitiveAnalysisEngineControl
> 

Re: Possible cause of nullPointerException in casmultiplier?

[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 :
> 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 
> 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 :
>> > 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
>> > 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 :
>> >> 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.PrimitiveAnalysisEngineControl
>> ler_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
>> >> 

Re: UIMA C++ in a Mac

[David Fox]

I tried this a couple of months back and got the same error.

Eventually I gave up on Mac OS X and got it working on linux.  In our
case, we use Mac OS X laptops for testing, but our production environment
is linux, so this wasn¹t a big deal and I didn¹t pursue it further.  If I
really did need to test on Mac OS X, my plan was to install virtual box
and run a linux VM on my Mac laptop.


David



On 11/25/16, 5:07 PM, "William Colen"  wrote:

>Hi,
>
>I need to execute a NLTK based POS Tagger. I was trying to create a C++ AE
>for that. Do you think it will work?
>
>I installed UIMA C++ 2.4.0 on top of UIMA 2.9.0.
>
>When I try to execute the installation instruction I get some compilation
>errors, like follows:
>
>$ make -f ExampleApplication.mak
>g++ -Wall -x c++ -DDEBUG -g -fno-inline -fPIC  -fno-default-inline
>-I/Users/user/programs/apache-uima/uimacpp/include
>-I/Users/user/programs/apache-uima/uimacpp/include/apr-1  -Wno-deprecated
>-c ExampleApplication.cpp
>clang: warning: optimization flag '-fno-default-inline' is not supported
>In file included from ExampleApplication.cpp:20:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/api.hpp:36:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/annotator_context.hp
>p:48:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/engine.hpp:47:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/exceptions.hpp:88:
>/Users/user/programs/apache-uima/uimacpp/include/uima/strtools.hpp:731:14:
>error: no member named 'operator void *' in
>'std::__1::basic_istream'
>  if (!i.operator void*())
>   ~ ^
>/Users/user/programs/apache-uima/uimacpp/include/uima/strtools.hpp:737:18:
>error: no member named 'operator void *' in
>'std::__1::basic_istream'
>  if (!i.operator void*())
>   ~ ^
>/Users/user/programs/apache-uima/uimacpp/include/uima/strtools.hpp:1674:19
>:
>warning: comparison of constant 18446744073709551615 with expression of
>type 'unsigned int' is always true
>[-Wtautological-constant-out-of-range-compare]
>if (envBegPos != STRING_NPOS) {
>~ ^  ~~~
>/Users/user/programs/apache-uima/uimacpp/include/uima/strtools.hpp:1676:21
>:
>warning: comparison of constant 18446744073709551615 with expression of
>type 'unsigned int' is always true
>[-Wtautological-constant-out-of-range-compare]
>  if (envEndPos != STRING_NPOS) {
>  ~ ^  ~~~
>In file included from ExampleApplication.cpp:20:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/api.hpp:36:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/annotator_context.hp
>p:48:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/engine.hpp:50:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/casiterator.hpp:37:
>/Users/user/programs/apache-uima/uimacpp/include/uima/cas.hpp:1252:84:
>error: default argument references parameter 'enAmbiguous'
>ANIterator subIterator( Type const & crType, EnIteratorAmbiguity
>enAmbiguous = enAmbiguous ) const;
>
>   ^~~
>/Users/user/programs/apache-uima/uimacpp/include/uima/cas.hpp:1376:88:
>error: default argument references parameter 'enAmbiguous'
>ANIterator subIterator( AnnotationFS const & an, EnIteratorAmbiguity
>enAmbiguous = enAmbiguous ) const;
>
>   ^~~
>ExampleApplication.cpp:207:12: warning: unused variable 'numread'
>[-Wunused-variable]
>size_t numread = fread(pBuffer,1,filesize,pFile);
>   ^
>In file included from ExampleApplication.cpp:20:
>In file included from
>/Users/user/programs/apache-uima/uimacpp/include/uima/api.hpp:59:
>/Users/user/programs/apache-uima/uimacpp/include/uima/annotator_abase.hpp:
>138:24:
>warning: private field 'iv_typeSystem' is not used
>[-Wunused-private-field]
>TypeSystem const * iv_typeSystem;
>   ^
>4 warnings and 4 errors generated.
>make: *** [ExampleApplication.o] Error 1
>
>
>
>
>What I am missing?
>
>Thank you,
>William

Re: Possible cause of nullPointerException in casmultiplier?

[Jaroslaw Cwiklik]

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 
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 :
> > 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
> > 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 :
> >> 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.PrimitiveAnalysisEngineControl
> ler_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(
> 

RE: XmiCasSerializer omits namespace prefixes in XML elements

[Oliver Ferschke]

Hi Mashall,
We switched from UIMA 2.6.0 right to 2.9.0 when it came out, but I haven't 
tried this particular scenario with older UIMA versions.
Worth to give it a shot.
I can confirm that SAXON is on the classpath and it's probably not easy to 
remove since other components require it.
But it's good to know what the possible cause of this issue might be.

-Oliver

-Original Message-
From: Marshall Schor [mailto:m...@schor.com] 
Sent: Wednesday, November 23, 2016 4:49 PM
To: user@uima.apache.org
Subject: Re: XmiCasSerializer omits namespace prefixes in XML elements

Do you see failures in UIMA 2.9.0, but no failures for earlier versions of UIMA?
(in other words, can you tell if this is a 2.9.0 issue, or is more general)?

-Marshall


On 11/23/2016 1:24 PM, Oliver Ferschke wrote:
> Hi all,
> I'm experiencing some odd behavior of the XmiCasSerializer (UIMA 2.9.0).
> When I pass a CAS to the static "serialize(CAS aCAS, 
> java.io.OutputStream aStream)" method within our runtime environment, it 
> produces an XMI with XML-Elements without namespace prefixes, e.g.
>  ..
> instead of
>  hidden="false"
>
> This also happens if I use the non-static methods.
> In a minimal example that doesn't use our pipeline deployment environment, 
> this does not happen.
> It seems like there is something in the classpath that changes the behavior 
> of the serializer but I haven't been able to pinpoint what this could be.
>
> Has anyone ever experienced a behavior like this or knows what else I could 
> look into?
>
> Thanks a lot.
> Oliver
>
>

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

[Jaroslaw Cwiklik]

Nelson, the fix for this is in the UIMA-AS RC1 announced last week on
uima-dev.
Jerry

On Fri, Nov 25, 2016 at 10:33 AM, nelson rivera 
wrote:

> Hi, i want to know if you have worked in issue of JIRA UIMA-5189 which
> addresses error handling when a serializer throws an exception.
>
> 2016-11-21 16:32 GMT-05:00, Jaroslaw Cwiklik :
> > Nelson, a fix for this is part of JIRA UIMA-5189 which addresses error
> > handing when a serializer throws an exception.
> > I will post UIMA-AS 2.9.0 release candidate tomorrow so you can test your
> > use case. Watch for an email on uima dev list.
> > Jerry
> >
> > On Mon, Nov 21, 2016 at 4:17 PM, nelson rivera  >
> > wrote:
> >
> >> 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.AggregateAnalysisEngineControl
> >> ler_impl.replyToClient:
> >> WARNING: Service: XDataFileExtractorAggregate Runtime Exception
> >> 03:50:03.579 - 22:
> >> org.apache.uima.aae.controller.AggregateAnalysisEngineControl
> >> ler_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.
> AggregateAnalysisEngineControl
> >> ler_impl.sendReplyToRemoteClient(AggregateAnalysisEngineControl
> >> ler_impl.java:2166)
> >> at org.apache.uima.aae.controller.
> AggregateAnalysisEngineControl
> >> ler_impl.replyToClient(AggregateAnalysisEngineControl
> ler_impl.java:2335)
> >> at org.apache.uima.aae.controller.
> AggregateAnalysisEngineControl
> >> ler_impl.finalStep(AggregateAnalysisEngineController_impl.java:1855)
> >> at org.apache.uima.aae.controller.
> AggregateAnalysisEngineControl
> >> ler_impl.executeFlowStep(AggregateAnalysisEngineControl
> ler_impl.java:2482)
> >> at org.apache.uima.aae.controller.
> AggregateAnalysisEngineControl
> >> ler_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$
> >>