gmane.comp.apache.uima.devel

[jira] [Commented] (UIMA-2752) DuccJobSubmit option --process_failures_limit is ignored

Lou DeGenaro (JIRA — 2013-05-23T21:20:20

    [ https://issues.apache.org/jira/browse/UIMA-2752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665681#comment-13665681 ] 

Lou DeGenaro commented on UIMA-2752:
------------------------------------

I ran a simple test that shows this feature works...I'll need to look at the job you cite to understand what's different.

In my test, I submitted a job with --process_failures_limit 1 and waited until at least one JP had initialized.  I then killed one running JP at random and the job was terminated according to plan, since the process failures limit was reached.

On the Jobs page, I see Reason = ProcessFailure, and when I hover I see: health monitor detected job process failures limit reached: 1

For the process I killed, the State Agent = Failed and the Reason Agent = Croaked

                


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http:

[jira] [Assigned] (UIMA-2935) DUCC command line interface (CLI) should allow specification of --process_initialization_time_max

Lou DeGenaro (JIRA — 2013-05-23T17:19:20

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

Lou DeGenaro reassigned UIMA-2935:
----------------------------------

    Assignee: Jerry Cwiklik  (was: Lou DeGenaro)
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2935) DUCC command line interface (CLI) should allow specification of --process_initialization_time_max

Lou DeGenaro (JIRA — 2013-05-23T17:19:20

    [ https://issues.apache.org/jira/browse/UIMA-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665373#comment-13665373 ] 

Lou DeGenaro commented on UIMA-2935:
------------------------------------

xferring to Jerry for Agent implementation.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (UIMA-2935) DUCC command line interface (CLI) should allow specification of --process_initialization_time_max

Lou DeGenaro (JIRA — 2013-05-23T17:17:22

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

Lou DeGenaro updated UIMA-2935:
-------------------------------

    Summary: DUCC command line interface (CLI) should allow specification of --process_initialization_time_max  (was: DUCC command line interface (CLI) should allow specification of --process_init_time_max)
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (UIMA-2935) DUCC command line interface (CLI) should allow specification of --process_initialization_time_max

Lou DeGenaro (JIRA — 2013-05-23T17:17:23

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

Lou DeGenaro updated UIMA-2935:
-------------------------------

    Description: 
1. CLI to support new flag --process_initialization_time_max <integer>
   a) value to be passed to agent via IDuccStandardInfo
   b) similar to --process_per_item_time_max <integer>  
2. CLI to remove support for --process_get_meta_time_max
   a) get_meta time to be system configruable via ducc.properties

  was:
1. CLI to support new flag --process_init_time_max <integer>
   a) value to be passed to agent via IDuccStandardInfo
   b) similar to --process_per_item_time_max <integer>  
2. CLI to remove support for --process_get_meta_time_max
   a) get_meta time to be system configruable via ducc.properties

    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/softwa

[jira] [Created] (UIMA-2939) Dynamic anchoring of Ruta rules suffers from integer overflow

Peter Klügl (JIRA — 2013-05-23T15:39:20

Peter Klügl created UIMA-2939:
---------------------------------

             Summary: Dynamic anchoring of Ruta rules suffers from integer overflow
                 Key: UIMA-2939
                 URL: https://issues.apache.org/jira/browse/UIMA-2939
             Project: UIMA
          Issue Type: Bug
          Components: ruta
    Affects Versions: 2.0.1ruta
            Reporter: Peter Klügl
            Assignee: Peter Klügl
             Fix For: 2.0.2ruta


Dynamic anchoring of Ruta rules suffers from integer overflow: penalty value for optional elements should not be initialized with Integer.MAX_VALUE especially if there are sibling elements. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (UIMA-2937) Leading optional matching conditions in Ruta

Peter Klügl (JIRA — 2013-05-23T14:41:27

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

Peter Klügl updated UIMA-2937:
------------------------------

    Summary: Leading optional matching conditions in Ruta  (was: Leading optional literal matching conditions in Ruta)
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2935) DUCC command line interface (CLI) should allow specification of --process_init_time_max

Lou DeGenaro (JIRA — 2013-05-23T14:39:19

    [ https://issues.apache.org/jira/browse/UIMA-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665226#comment-13665226 ] 

Lou DeGenaro commented on UIMA-2935:
------------------------------------

Support in CLI, Orchestrator, Common and Transport delivered.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2937) Leading optional literal matching conditions in Ruta

Peter Klügl (JIRA — 2013-05-23T13:57:20

    [ https://issues.apache.org/jira/browse/UIMA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665186#comment-13665186 ] 

Peter Klügl commented on UIMA-2937:
-----------------------------------

test case:

document:
{noformat}
a b c x b c x c
{noformat}

script:
{noformat}
PACKAGE uima.ruta.tests;

DECLARE T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15;

"a"-> T1;
"b"-> T2;
"c"-> T3;

(T1? T2 T3){-> T4};
T1? T2 T3{-> MARK(T5,1,2,3)};
("a"? "b" "c"){->T6};
"a"? "b" "c"{-> MARK(T7,1,2,3)};

(T1? T2? T3){-> T8};
T1? T2? T3{-> MARK(T9,1,2,3)};
("a"? "b"? "c"){->T10};
"a"? "b"? "c"{-> MARK(T11,1,2,3)};

((T1? T2)? T3){-> T12};
(T1? T2)? T3{-> MARK(T13,1,2,3)};
(("a"? "b")? "c"){->T14};
("a"? "b")? "c"{-> MARK(T15,1,2,3)};
{noformat}
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/softwar

[jira] [Created] (UIMA-2938) Adapt formatter in Ruta Workbench to recent changes

Peter Klügl (JIRA — 2013-05-23T13:15:21

Peter Klügl created UIMA-2938:
---------------------------------

             Summary: Adapt formatter in Ruta Workbench to recent changes
                 Key: UIMA-2938
                 URL: https://issues.apache.org/jira/browse/UIMA-2938
             Project: UIMA
          Issue Type: Bug
          Components: ruta
    Affects Versions: 2.0.1ruta
            Reporter: Peter Klügl
            Assignee: Peter Klügl
             Fix For: 2.0.2ruta


The formatter in the UIMA Ruta Workbench needs to be adapted to the recent changes in the language definition, e.g., simple regexp rules, feature matches, feature expressions, implicit actions and conditions, ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (UIMA-2937) Leading optional literal matching conditions in Ruta

Peter Klügl (JIRA — 2013-05-23T11:34:20

Peter Klügl created UIMA-2937:
---------------------------------

             Summary: Leading optional literal matching conditions in Ruta
                 Key: UIMA-2937
                 URL: https://issues.apache.org/jira/browse/UIMA-2937
             Project: UIMA
          Issue Type: Bug
          Components: ruta
    Affects Versions: 2.0.1ruta
            Reporter: Peter Klügl
            Assignee: Peter Klügl
             Fix For: 2.0.2ruta


Armin Wegner reported:
In Ruta 2.0.2-SNAPSHOT, rules with an optional first element do not work. The optional part seems to be mandatory. Using

DECLARE Test;
"a"? "b" "c"{->MARK(Test, 1, 3)};

on

a b c x b c

marks "a b c" (0, 5) but not "b c" (8, 11).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (UIMA-2932) CLI needs to specify how to start a custom service

Burn Lewis (JIRA — 2013-05-23T00:43:19

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

Burn Lewis resolved UIMA-2932.
------------------------------

    Resolution: Fixed

Tested with a simple C++ service
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (UIMA-2928) The manifests of the executable jars must be changed when any of its jars change

Burn Lewis (JIRA — 2013-05-23T00:43:20

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

Burn Lewis resolved UIMA-2928.
------------------------------

    Resolution: Fixed
    

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (UIMA-2879) When --all_in_one option set client should not call exit

Burn Lewis (JIRA — 2013-05-23T00:41:20

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

Burn Lewis resolved UIMA-2879.
------------------------------

    Resolution: Fixed
    


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2917) Type System Merging for string subtypes with allowed values

Marshall Schor (JIRA — 2013-05-22T21:44:20

    [ https://issues.apache.org/jira/browse/UIMA-2917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664569#comment-13664569 ] 

Marshall Schor commented on UIMA-2917:
--------------------------------------

What happens after this fix, is that an ResourceInitializationException is thrown, saying the 2 same-named types cannot be successfully merged.  

What happened before this fix is that no checking was done, and the "first one" in the merge set "wins", the others were ignored.

To your point of one type system making a restriction, and the other not - let's see... the one not making a restriction would define a feature to be of type "uima.cas.String"; the other would define it to be of type "my.set.of.allowed.values", which, in turn is a subtype of uima.cas.String.

The current merge code requires feature range types to match, in all cases.  So type merging always throws an exception if one feature fff has a range type of uima.cas.String in one definition of type

[jira] [Resolved] (UIMA-2936) DUCC webserver (WS) doesn't handle Custom Service log file correctly

Lou DeGenaro (JIRA — 2013-05-22T20:46:20

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

Lou DeGenaro resolved UIMA-2936.
--------------------------------

    Resolution: Fixed

Code delivered.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (UIMA-2936) DUCC webserver (WS) doesn't handle Custom Service log file correctly

Lou DeGenaro (JIRA — 2013-05-22T20:06:19

Lou DeGenaro created UIMA-2936:
----------------------------------

             Summary: DUCC webserver (WS) doesn't handle Custom Service log file correctly
                 Key: UIMA-2936
                 URL: https://issues.apache.org/jira/browse/UIMA-2936
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Lou DeGenaro
            Priority: Minor
             Fix For: 1.0-Ducc


From adjunct complainer:

I've just registered an autostart custom service (121) on the test ducc and it started two POP's 2344 2345 ... but it looks as if the WS assumes all service jobs are UIMA so the WS reports the wrong log filename, e.g. 2345-UIMA-... instead of 2345-POP-...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (UIMA-2935) DUCC command line interface (CLI) should allow specification of --process_init_time_max

Lou DeGenaro (JIRA — 2013-05-22T19:50:19

Lou DeGenaro created UIMA-2935:
----------------------------------

             Summary: DUCC command line interface (CLI) should allow specification of --process_init_time_max
                 Key: UIMA-2935
                 URL: https://issues.apache.org/jira/browse/UIMA-2935
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Lou DeGenaro
            Priority: Minor
             Fix For: 1.0-Ducc


1. CLI to support new flag --process_init_time_max <integer>
   a) value to be passed to agent via IDuccStandardInfo
   b) similar to --process_per_item_time_max <integer>  
2. CLI to remove support for --process_get_meta_time_max
   a) get_meta time to be system configruable via ducc.properties

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Jenkins build is back to normal : UIMA-uimaFIT #61

Apache Jenkins Server — 2013-05-22T19:42:35

See <https://builds.apache.org/job/UIMA-uimaFIT/61/>

[jira] [Resolved] (UIMA-2930) DUCC webserver (WS) should make available button(s) for Job Process (JP) cancellation

Lou DeGenaro (JIRA — 2013-05-22T19:40:21

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

Lou DeGenaro resolved UIMA-2930.
--------------------------------

    Resolution: Fixed

Code delivered.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (UIMA-2930) DUCC webserver (WS) should make available button(s) for Job Process (JP) cancellation

Lou DeGenaro (JIRA — 2013-05-22T19:40:19

    [ https://issues.apache.org/jira/browse/UIMA-2930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664448#comment-13664448 ] 

Lou DeGenaro commented on UIMA-2930:
------------------------------------

1. Add new "Agent Reason" AdministratorInitiated
2. Insure Job Process Init and Run Times have end time when Job Process is abandoned
3. OR should not overlay Process Deallocation Type if already set
4. Support "confirm relsase shares" in ducc.js
5. New data class JobProcessInfo
6. New WS utilities
   a) to get list of JobId+ProcessId pairs "stuck" on nodes that are not "up"
   b) to determine of request user is an administrator
   c) to build ReleaseMachine and ReleaseAll buttons
7. New WS Servlet to employ ducc_ling to release stuck JPs according to parameter: particular machine or all machines
8. New Hint: Login user is not an Administrator
9. Classic and Scroll views support for Release Stuck JP shares on Machines page by logged-in administrator