Apache Jenkins Server | 7 Jul 22:57 2015
Picon

Jenkins build is unstable: UIMA-DUCC #478

See <https://builds.apache.org/job/UIMA-DUCC/478/changes>

Apache Jenkins Server | 7 Jul 22:57 2015
Picon

Jenkins build became unstable: UIMA-DUCC » Apache UIMA DUCC: uima-ducc-container #478

See <https://builds.apache.org/job/UIMA-DUCC/org.apache.uima$uima-ducc-container/478/>

Marshall Schor | 7 Jul 21:37 2015

Generics in 2.8.0 getAllIndexedFS

Burn reports a source incompatibility with the 2.8.0 signature for the
getAllIndexedFS.  This is a somewhat complex issue.  Here's what I've found so far:

1) We have 3 sets of versions of getAllIndexedFS - one in the plain CAS index
repo, one in the JCas version of the index repo, and one directly in the JCas
itself.  The signatures are not consistent.

2) https://issues.apache.org/jira/browse/UIMA-4299 strongly suggests not
returning values of <? extends XXX>.  We opted in the plain CAS version to use
   <T extends FeatureStructure> FSIterator<T> getAllIndexedFS(...)
and in the JCas index version:
                                FSIterator<FeatureStructure> getAllIndexedFS(...),
and in the JCas itself:
   <T extends TOP>              FSIterator<T> getAllIndexedFS(Class<T> clazz)

3) At first I thought that it was quite possible that the getAllIndexedFS call
will produce an iterator which returns a mixture of subtypes of the specified
class, or instances of FeatureStructure, which are not a subtype of the
specified class, and would produce a ClassCastException when assigned to a
variable of the iterator type.  I thought that FeatureStructure will be produced
if there is no JCas cover class, but I think this is incorrect.
There are generators for each type that generate the corresponding Java class. 
As part of the JCas creation, the method instantiateJCas_Types is called and
will replace the generators with JCas versions.  If no JCas cover class can be
found for a particular type, the generator is still replaced with one for the
first JCas cover type found in the supertype chain.  Since TOP is a built-in
defined JCas type, even if no other types have JCas cover types, TOP will.

4) Current user code often has some JCas cover class as the top-most class of
some set of Java cover objects being returned.  These are currently failing for
(Continue reading)

Lou DeGenaro (JIRA | 7 Jul 17:11 2015
Picon

[jira] [Resolved] (UIMA-4503) DUCC Web Server (WS) incorrectly reports Agent as "up"


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

Lou DeGenaro resolved UIMA-4503.
--------------------------------
    Resolution: Fixed

Code is delivered.

> DUCC Web Server (WS) incorrectly reports Agent as "up"
> ------------------------------------------------------
>
>                 Key: UIMA-4503
>                 URL: https://issues.apache.org/jira/browse/UIMA-4503
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 2.0.0-Ducc
>
>
> It seems that when calculating up/down status the WS is confused between seconds and milliseconds!

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Lou DeGenaro (JIRA | 7 Jul 16:33 2015
Picon

[jira] [Created] (UIMA-4503) DUCC Web Server (WS) incorrectly reports Agent as "up"

Lou DeGenaro created UIMA-4503:
----------------------------------

             Summary: DUCC Web Server (WS) incorrectly reports Agent as "up"
                 Key: UIMA-4503
                 URL: https://issues.apache.org/jira/browse/UIMA-4503
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Lou DeGenaro
            Priority: Minor
             Fix For: 2.0.0-Ducc

It seems that when calculating up/down status the WS is confused between seconds and milliseconds!

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Picon

[jira] [Updated] (UIMA-4299) improve generics for UIMA indexes and iterators


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

Richard Eckart de Castilho updated UIMA-4299:
---------------------------------------------
    Assignee: Marshall Schor

> improve generics for UIMA indexes and iterators
> -----------------------------------------------
>
>                 Key: UIMA-4299
>                 URL: https://issues.apache.org/jira/browse/UIMA-4299
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.7.0SDK
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.8.0SDK
>
>
> When the JCas is being used, there are Java classes for UIMA types.  
> Each index definition is associated with a top-most type in the type hierarchy.
> Indexes are used to create iterators of various kinds; some of these iterators are defined within classes
which implement Iterable.  
> Add generic mechanisms to the Indexes and iterators to support Iterables whose elements are JCas types. 
> Update the APIs that get indexes over particular types to allow specifying those types by the type class,
and use this for generic typing, so casts are not necessary for user code.
(Continue reading)

Jerry Cwiklik (JIRA | 6 Jul 21:30 2015
Picon

[jira] [Created] (UIMA-4502) DUCC JP does not exit cleanly on end of job

Jerry Cwiklik created UIMA-4502:
-----------------------------------

             Summary: DUCC JP does not exit cleanly on end of job
                 Key: UIMA-4502
                 URL: https://issues.apache.org/jira/browse/UIMA-4502
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 2.0.0-Ducc

Sometimes a JP does not terminate on end of job. An agent sends a request to stop to the JP, but it gets stuck in
camel contex.stop() and never completes the shutdown forcing agent to kill the process via -9.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Apache Jenkins Server | 6 Jul 21:55 2015
Picon

Jenkins build became unstable: UIMA-DUCC » Apache UIMA DUCC: uima-ducc-container #475

See <https://builds.apache.org/job/UIMA-DUCC/org.apache.uima$uima-ducc-container/475/>

Lou DeGenaro (JIRA | 6 Jul 13:50 2015
Picon

[jira] [Reopened] (UIMA-4492) DUCC Web Server (WS) shows zero for file sizes under Job, Reservations, Services Details...


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

Lou DeGenaro reopened UIMA-4492:
--------------------------------

incorrect resolution

> DUCC Web Server (WS) shows zero for file sizes under Job, Reservations, Services Details...
> -------------------------------------------------------------------------------------------
>
>                 Key: UIMA-4492
>                 URL: https://issues.apache.org/jira/browse/UIMA-4492
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 2.0.0-Ducc
>
>
> The Jobs Details page Processes tab, the Reservations Details page Processes tab, and the Services
Details page Deployments tab may show zero for file sizes when the WS itself (running as "ducc") does not
have access to user files.
> The fix is to add code to have WS employ ducc_ling for logged-in users.

--
This message was sent by Atlassian JIRA
(Continue reading)

Lou DeGenaro (JIRA | 6 Jul 13:50 2015
Picon

[jira] [Resolved] (UIMA-4492) DUCC Web Server (WS) shows zero for file sizes under Job, Reservations, Services Details...


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

Lou DeGenaro resolved UIMA-4492.
--------------------------------
    Resolution: Fixed

> DUCC Web Server (WS) shows zero for file sizes under Job, Reservations, Services Details...
> -------------------------------------------------------------------------------------------
>
>                 Key: UIMA-4492
>                 URL: https://issues.apache.org/jira/browse/UIMA-4492
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 2.0.0-Ducc
>
>
> The Jobs Details page Processes tab, the Reservations Details page Processes tab, and the Services
Details page Deployments tab may show zero for file sizes when the WS itself (running as "ducc") does not
have access to user files.
> The fix is to add code to have WS employ ducc_ling for logged-in users.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
(Continue reading)

Picon

[jira] [Updated] (UIMA-2419) Initial view for sofa unaware components not automatically created


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

Richard Eckart de Castilho updated UIMA-2419:
---------------------------------------------
    Assignee: Marshall Schor

> Initial view for sofa unaware components not automatically created
> ------------------------------------------------------------------
>
>                 Key: UIMA-2419
>                 URL: https://issues.apache.org/jira/browse/UIMA-2419
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.4.0SDK
>            Reporter: Richard Eckart de Castilho
>            Assignee: Marshall Schor
>              Labels: patch
>         Attachments: UIMA-2419-REC-20120609.patch
>
>
> When running a sofa-unaware component in an aggregate analysis engine, the initial view for the
component to operate on is not automatically created if it does not exist. This causes a
CASRuntimeException, here "No sofaFS with name A found.".
> {noformat}
> org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator processing failed.    
> 	at org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.callAnalysisComponentProcess(PrimitiveAnalysisEngine_impl.java:394)
> 	at org.apache.uima.analysis_engine.impl.PrimitiveAnalysisEngine_impl.processAndOutputNewCASes(PrimitiveAnalysisEngine_impl.java:298)
(Continue reading)


Gmane