headers
Marshall Schor | 1 Nov 18:29

new testcase for running Pear inside CPE - question on how to package

There will be a new testcase for the CPE to test running Pears inside a
CPE.  The test needs a Pear.  So I made one by setting up another
eclipse project "uimaj-pear-forTesting" which is a pear which does
nothing, but references a JCas cover class.

In the uimaj-cpe project, I added a new resource under
src/test/resources to be where I "installed" the pear, and then I
installed the uimaj-pear-forTesting pear, there.  I changed the two
parts of the install which hard-coded the absolute path, to relative
paths, and tested for Maven builds, - looks like it works fine.

So - my question - I think I should check in the uimaj-pear-forTesting"
project - so we have the source in case we want to alter/improve/fix
this test pear someday.  It's not needed to be built as part of the
maven build.  I'm thinking of just leaving it as a plain Eclipse
project, and checking in the .project and .classpath files - that way,
the "pear packager" tool will work (the project has the "UIMA nature").

Anyone have alternate / better suggestion?

Cheers. -Marshall
Permalink | Reply | 4 comments |
headers
Marshall Schor (JIRA | 1 Nov 20:24
Picon
Favicon

[jira] Resolved: (UIMA-607) Running PEAR class path switching code broken in multi-threading case (CPM)


     [
https://issues.apache.org/jira/browse/UIMA-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor resolved UIMA-607.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3

> Running PEAR class path switching code broken in multi-threading case (CPM)
> ---------------------------------------------------------------------------
>
>                 Key: UIMA-607
>                 URL: https://issues.apache.org/jira/browse/UIMA-607
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.2
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 2.3
>
>
> The new facility in 2.2 to run a Pear, switching class paths, has threading issues when run from a CPM in
multiple threads.  Needs a code review and fixes for case where CAS Pools are sharing one type system with
all the CASes in the pool.

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor (JIRA | 2 Nov 15:24
Picon
Favicon

[jira] Created: (UIMA-608) Move to Java 1.5

Move to Java 1.5
----------------

                 Key: UIMA-608
                 URL: https://issues.apache.org/jira/browse/UIMA-608
             Project: UIMA
          Issue Type: Improvement
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor

Move the source and target levels for JVM compilation to 1.5.  This involves updating the main POM, and the
uimaj-distr pom (to point to the right javadocs).

Also, need to update the docs / prerequisites / FAQs etc.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 6 comments |
headers
Jörn Kottmann (JIRA | 4 Nov 20:33
Picon
Favicon

[jira] Reopened: (UIMA-574) CAS heap size is just increased by the initial heap size and is not doubled until a threshold is reached


     [
https://issues.apache.org/jira/browse/UIMA-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann reopened UIMA-574:
--------------------------------

      Assignee: Jörn Kottmann  (was: Thilo Goetz)

On my machine the heap size of 400M is not enough to run this test, heap size should be increased to 450M.
I am using java 1.6 for linux.

> CAS heap size is just increased by the initial heap size and is not doubled until a threshold is reached
> --------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-574
>                 URL: https://issues.apache.org/jira/browse/UIMA-574
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.3
>            Reporter: Michael Baessler
>            Assignee: Jörn Kottmann
>             Fix For: 2.3
>
>
> Currently the CAS heap size is increased by the initial heap size if new heap space is required. If the
initial heap space is very small there is a high performance impact for large documents.

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann (JIRA | 4 Nov 20:37
Picon
Favicon

[jira] Closed: (UIMA-574) CAS heap size is just increased by the initial heap size and is not doubled until a threshold is reached


     [
https://issues.apache.org/jira/browse/UIMA-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann closed UIMA-574.
------------------------------

    Resolution: Fixed

Heap size is now 450M.

> CAS heap size is just increased by the initial heap size and is not doubled until a threshold is reached
> --------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-574
>                 URL: https://issues.apache.org/jira/browse/UIMA-574
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.3
>            Reporter: Michael Baessler
>            Assignee: Jörn Kottmann
>             Fix For: 2.3
>
>
> Currently the CAS heap size is increased by the initial heap size if new heap space is required. If the
initial heap space is very small there is a high performance impact for large documents.

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann | 4 Nov 22:33
Picon

Deadlocks in CPM tests ?

Hello,

I did build uima serveral times with maven, but in two cases
the tests block. I guess we have race conditions which lead
to deadlocks.

Here are the console output.

First case:

Running org.apache.uima.collection.impl.cpm.CpmInitTest
Initialize was called: true
Nov 4, 2007 8:32:03 PM  
org.apache.uima.collection.impl.cpm.BaseCPMImpl process
WARNING: Processing the request to stop the CPM. (Thread Name: main)
Nov 4, 2007 8:32:03 PM  
org.apache.uima.collection.impl.cpm.engine.CPMEngine process
INFO: The collection reader thread state is: 2007 (Thread Name: main)
Initialize was called: true
Nov 4, 2007 8:32:04 PM  
org.apache.uima.collection.impl.cpm.BaseCPMImpl process
WARNING: Processing the request to stop the CPM. (Thread Name: main)
Nov 4, 2007 8:32:04 PM  
org.apache.uima.collection.impl.cpm.engine.CPMEngine process
INFO: The collection reader thread state is: 1001 (Thread Name: main)
Nov 4, 2007 8:32:04 PM  
org.apache.uima.collection.impl.cpm.engine.CPMEngine process
INFO: The CPM processing unit is 0 and processing state 2004. (Thread  
Name: main)
Nov 4, 2007 8:32:04 PM
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jörn Kottmann | 4 Nov 22:56
Picon

PearCasPoolTest.testCasPool fails

Hello,

on my machine this tests fails while building with maven. I guess
the "src\test\resources\pearTests\installedSimpleTokenPear\uimaj-pear- 
forTesting"
cannot be found in an unix environment.

Here is the console output:

Running org.apache.uima.collection.impl.cpm.PearCasPoolTest
org.apache.uima.resource.ResourceInitializationException:  
Initialization of CAS Processor with name "ErrorTestAnnotator"  
failed.        at  
org.apache.uima.collection.impl.CollectionProcessingEngine_impl.initiali 
ze(CollectionProcessingEngine_impl.java:83)
        at  
org.apache.uima.impl.UIMAFramework_impl._produceCollectionProcessingEngi 
ne(UIMAFramework_impl.java:395)
        at  
org.apache.uima.UIMAFramework.produceCollectionProcessingEngine 
(UIMAFramework.java:865)
        at  
org.apache.uima.collection.impl.cpm.PearCasPoolTest.setupCpm 
(PearCasPoolTest.java:166)
        at org.apache.uima.collection.impl.cpm.PearCasPoolTest.core 
(PearCasPoolTest.java:91)
        at  
org.apache.uima.collection.impl.cpm.PearCasPoolTest.testCasPool 
(PearCasPoolTest.java:72)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
(Continue reading)

Permalink | Reply | 5 comments |
headers
Marshall Schor | 5 Nov 04:38

Re: PearCasPoolTest.testCasPool fails

Hi Joern - do you think this is just a case of using "backslashes"
instead of forward slashes?  If it's easy for you to test, can see if
switching this "fixes" the problem?

-Marshall

Jörn Kottmann wrote:
> Hello,
>
> on my machine this tests fails while building with maven. I guess
> the
> "src\test\resources\pearTests\installedSimpleTokenPear\uimaj-pear-forTesting"
>
> cannot be found in an unix environment.
>
> Here is the console output:
>
> Running org.apache.uima.collection.impl.cpm.PearCasPoolTest
> org.apache.uima.resource.ResourceInitializationException:
> Initialization of CAS Processor with name "ErrorTestAnnotator"
> failed.        at
> org.apache.uima.collection.impl.CollectionProcessingEngine_impl.initialize(CollectionProcessingEngine_impl.java:83)
>
>        at
> org.apache.uima.impl.UIMAFramework_impl._produceCollectionProcessingEngine(UIMAFramework_impl.java:395)
>
>        at
> org.apache.uima.UIMAFramework.produceCollectionProcessingEngine(UIMAFramework.java:865)
>
>        at
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jörn Kottmann | 5 Nov 10:02
Picon

Re: PearCasPoolTest.testCasPool fails

> Hi Joern - do you think this is just a case of using "backslashes"
> instead of forward slashes?  If it's easy for you to test, can see if
> switching this "fixes" the problem?

Sure, I replaced the backslashes with slashes and now I got another  
exception.
Just give me a note, I can test for you again.

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007  
sec
Running org.apache.uima.collection.impl.cpm.PearCasPoolTest
org.apache.uima.resource.ResourceInitializationException:  
Initialization of CAS Processor with name "ErrorTestAnnotator" failed.
         at  
org.apache.uima.collection.impl.CollectionProcessingEngine_impl.initiali 
ze(CollectionProcessingEngine_impl.java:83)
         at  
org.apache.uima.impl.UIMAFramework_impl._produceCollectionProcessingEngi 
ne(UIMAFramework_impl.java:395)
         at  
org.apache.uima.UIMAFramework.produceCollectionProcessingEngine 
(UIMAFramework.java:865)
         at  
org.apache.uima.collection.impl.cpm.PearCasPoolTest.setupCpm 
(PearCasPoolTest.java:166)
         at org.apache.uima.collection.impl.cpm.PearCasPoolTest.core 
(PearCasPoolTest.java:91)
         at  
org.apache.uima.collection.impl.cpm.PearCasPoolTest.testCasPool 
(PearCasPoolTest.java:72)
(Continue reading)

Permalink | Reply | 3 comments |
headers
Michael Baessler | 5 Nov 13:36
Picon

Re: new testcase for running Pear inside CPE - question on how to package

Marshall Schor wrote:
> There will be a new testcase for the CPE to test running Pears inside a
> CPE.  The test needs a Pear.  So I made one by setting up another
> eclipse project "uimaj-pear-forTesting" which is a pear which does
> nothing, but references a JCas cover class.
>
> In the uimaj-cpe project, I added a new resource under
> src/test/resources to be where I "installed" the pear, and then I
> installed the uimaj-pear-forTesting pear, there.  I changed the two
> parts of the install which hard-coded the absolute path, to relative
> paths, and tested for Maven builds, - looks like it works fine.
>
> So - my question - I think I should check in the uimaj-pear-forTesting"
> project - so we have the source in case we want to alter/improve/fix
> this test pear someday.  It's not needed to be built as part of the
> maven build.  I'm thinking of just leaving it as a plain Eclipse
> project, and checking in the .project and .classpath files - that way,
> the "pear packager" tool will work (the project has the "UIMA nature").
>
> Anyone have alternate / better suggestion?
>
> Cheers. -Marshall
>   
I have also written some tests for the PEAR stuff where I need PEAR 
files for testing.
I created the PEARs and packaged them together with source code, 
.project and .classpath files.
I only committed the packaged PEAR to the SVN. If changes are necessary, 
the PEAR can be extracted and the source code can be changed.
(Continue reading)

Permalink | Reply | 3 comments |

Gmane