Re: Regarding Apached cTakes

2018-06-01 Thread Peter Abramowitsch
Hi Ankit It looks like your answer is near the bottom of the stacktrace you sent. The machine is out of memory. In general with these traces the root cause of an error will be near the bottom, but as it is propagated up the many layers of the application, the messages become more generic.

Re: Regarding Apached cTakes

2018-06-01 Thread Peter Abramowitsch
The best thing would be for you to look at some of the other launch scripts in the bin directory of a release. There you’ll find examples of passing both memory and UMLS parameters. Sent from my iPad > On Jun 1, 2018, at 18:36, Ankit Bisht wrote: > > Thanks Peter. I have not done that

Re: Could not find or load main class org.apache.uima.tools.cpm.CpmFrame

2018-06-01 Thread Barbara Moloney
I found the solution at https://stackoverflow.com/questions/30386833/uima-example-in-eclipse-not-working with some modification. I needed to create a UIMA user library in Eclipse for each ctakes run confiiguration by adding external Jars from UIMA_HOME\lib. Barbara On 1 May 2018 at 11:28,

Re: Regarding Apached cTakes

2018-06-01 Thread Ankit Bisht
Hello Peter, Thanks for showing your concern on this issue. The machine on which I am running cTakes has 32 GB of Ram and 100 GB of Memory left. -Ankit On Fri, Jun 1, 2018 at 2:31 AM, Peter Abramowitsch wrote: > Hi Ankit > > It looks like your answer is near the bottom of the stacktrace you

Re: Regarding Apached cTakes

2018-06-01 Thread Peter Abramowitsch
That's good. But the fact that the stack trace shows you're out of memory, probably indicates that the JVM memory related args are not successfully being passed. They should be set to -Xms512M -Xmx3g or greater. Peter On Fri, Jun 1, 2018 at 5:03 PM, Ankit Bisht wrote: > Hello Peter, > >

Re: Regarding Apached cTakes

2018-06-01 Thread Ankit Bisht
Thanks Peter. I have not done that before. How could it be done? Would it be done like this: java -Xms512M -Xmx3g ClassName? -Ankit On Fri, Jun 1, 2018 at 12:05 PM, Peter Abramowitsch wrote: > That's good. But the fact that the stack trace shows you're out of memory, > probably indicates that