Re: Possible cause of nullPointerException in casmultiplier?

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

Re: Possible cause of nullPointerException in casmultiplier?

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

Re: UIMA C++ in a Mac

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

Re: Possible cause of nullPointerException in casmultiplier?

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

RE: XmiCasSerializer omits namespace prefixes in XML elements

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

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

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