Jerry Cwiklik (JIRA | 24 Apr 18:14 2015
Picon

[jira] [Closed] (UIMA-4366) Make JD Jetty max threads and idle time configurable via ducc.properties


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

Jerry Cwiklik closed UIMA-4366.
-------------------------------
    Resolution: Fixed

added jettyMaxThreads and jettyThreadIdleTime to ducc.properties and code to read them in the JobDriverConfiguration

> Make JD Jetty max threads and idle time configurable via ducc.properties
> ------------------------------------------------------------------------
>
>                 Key: UIMA-4366
>                 URL: https://issues.apache.org/jira/browse/UIMA-4366
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.0.0-Ducc
>
>
> Externalize JD jetty params max threads and idle time. 

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

(Continue reading)

Jerry Cwiklik (JIRA | 24 Apr 18:06 2015
Picon

[jira] [Created] (UIMA-4366) Make JD Jetty max threads and idle time configurable via ducc.properties

Jerry Cwiklik created UIMA-4366:
-----------------------------------

             Summary: Make JD Jetty max threads and idle time configurable via ducc.properties
                 Key: UIMA-4366
                 URL: https://issues.apache.org/jira/browse/UIMA-4366
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 2.0.0-Ducc

Externalize JD jetty params max threads and idle time. 

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

Jerry Cwiklik (JIRA | 24 Apr 16:07 2015
Picon

[jira] [Closed] (UIMA-4360) DUCC Agent camel route shutdown hangs a thread trying to stop a JP


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

Jerry Cwiklik closed UIMA-4360.
-------------------------------
    Resolution: Fixed

Removed code from undeploy() which stops camel route responsible for stopping a camel route. The routs is
stopped in onProcessExit()

> DUCC Agent camel route shutdown hangs a thread trying to stop a JP
> ------------------------------------------------------------------
>
>                 Key: UIMA-4360
>                 URL: https://issues.apache.org/jira/browse/UIMA-4360
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.0.0-Ducc
>
>
> It looks like a thread trying to stop a JP hangs in the following code (NodeAgent.java):
>    	  // stop collecting process stats from /proc/≤pid>/statm
>           super.getContext().stopRoute(pid);
> The thread is stuck in stopRoute() until the JP is killed via -9. This hang does not happen every time but
seems to happens sometimes.

(Continue reading)

Apache Jenkins Server | 24 Apr 16:04 2015
Picon

Jenkins build is back to stable : UIMA-DUCC #374

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

Burn Lewis (JIRA | 24 Apr 15:46 2015
Picon

[jira] [Created] (UIMA-4365) JD should shut itself down instead of being killed -9 by agent

Burn Lewis created UIMA-4365:
--------------------------------

             Summary: JD should shut itself down instead of being killed -9 by agent
                 Key: UIMA-4365
                 URL: https://issues.apache.org/jira/browse/UIMA-4365
             Project: UIMA
          Issue Type: Improvement
          Components: DUCC
    Affects Versions: future-DUCC
            Reporter: Burn Lewis
            Priority: Minor

It would wait until all JPs were gone, and have time to generate a summary of work & time spent etc.

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

Jerry Cwiklik (JIRA | 24 Apr 15:31 2015
Picon

[jira] [Closed] (UIMA-4363) DUCC JP not handling errors while serializing process exceptions


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

Jerry Cwiklik closed UIMA-4363.
-------------------------------
    Resolution: Fixed

On failure while serializing user exception (process failed) create a RuntimeException and serialize
that instead. 

> DUCC JP not handling errors while serializing process exceptions
> ----------------------------------------------------------------
>
>                 Key: UIMA-4363
>                 URL: https://issues.apache.org/jira/browse/UIMA-4363
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.0.0-Ducc
>
>
> When an AE throws an exception from process(), the JP serializes the exception and sends it back to the JD.
If the annotator designer throws an exception that is not serializable, the JP fails and the JD is not
notified of a process failure. 
> Modify code to catch exceptions while serializing and send back serialized RuntimeException with an
appropriate message directing user to look at JP log for more details.

(Continue reading)

Lou DeGenaro (JIRA | 24 Apr 15:26 2015
Picon

[jira] [Resolved] (UIMA-4364) DUCC Orchestrator (OR) HealthMonitor is too aggressive during Job shutdown


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

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

Code is delivered.

> DUCC Orchestrator (OR) HealthMonitor is too aggressive during Job shutdown
> --------------------------------------------------------------------------
>
>                 Key: UIMA-4364
>                 URL: https://issues.apache.org/jira/browse/UIMA-4364
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>            Priority: Minor
>             Fix For: 2.0.0-Ducc
>
>
> OR's HealthMonitor should not Deallocate the JD unless and until all the JPs are terminated.

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

(Continue reading)

Lou DeGenaro (JIRA | 24 Apr 15:23 2015
Picon

[jira] [Created] (UIMA-4364) DUCC Orchestrator (OR) HealthMonitor is too aggressive during Job shutdown

Lou DeGenaro created UIMA-4364:
----------------------------------

             Summary: DUCC Orchestrator (OR) HealthMonitor is too aggressive during Job shutdown
                 Key: UIMA-4364
                 URL: https://issues.apache.org/jira/browse/UIMA-4364
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Lou DeGenaro
            Priority: Minor
             Fix For: 2.0.0-Ducc

OR's HealthMonitor should not Deallocate the JD unless and until all the JPs are terminated.

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

Lou DeGenaro (JIRA | 24 Apr 15:19 2015
Picon

[jira] [Resolved] (UIMA-4361) DUCC Job Driver (JD) should only recieve pertinent info from Orchestrator (OR)


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

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

Code is delivered.

> DUCC Job Driver (JD) should only recieve pertinent info from Orchestrator (OR) 
> -------------------------------------------------------------------------------
>
>                 Key: UIMA-4361
>                 URL: https://issues.apache.org/jira/browse/UIMA-4361
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 2.0.0-Ducc
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>
> OR publications can be large.  The JD only cares about its own Job, so all the rest is wasted bandwidth and memory.
> CLI and OR already communicate directly using HTTP.  JD will now use HTTP to publish its regular Status
Reports and in return receive up-to-date Job information (e.g. new and gone JPs).
> OR --hot start should continue to work for already running Jobs.

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

James Zhu (JIRA | 24 Apr 06:24 2015
Picon

[jira] [Updated] (UIMA-3374) A new mode for annotation viewer based on feature values


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

James Zhu updated UIMA-3374:
----------------------------
    Attachment: UIMA-3374 patch 2015-04-23.txt

In this patch, I did the following changes (the patch should be applied to the uimaj-tools project only):
1. Renamed class variables by removing the "m" prefix. This naming convention of using "m" prefix is not
consistent with other places in the uimaj-core project etc, and not consistent within the same class
itself. In most other places, the "m" prefix is not used.
2. Avoided warnings by adding types to the generics variables. The code is more readable as it is easier to
see what type of objects are stored in the collections. Avoided unnecessary cast subsequently when
iterating through the generics collection.
3. Applied best practice of programming against interface. For instance, instead of declaring variable
with "ArrayList<String> names = new ArrayList<String>();", use "List<String> names = new
ArrayList<String>();", instead of "public ArrayList<String> getNames() { return names;}", do
"public List<String> getNames() {return names;}".

These changes should have no impact to the functionality. Please review and let me know if you have any
concerns about these changes. Thanks.

> A new mode for annotation viewer based on feature values
> --------------------------------------------------------
>
>                 Key: UIMA-3374
>                 URL: https://issues.apache.org/jira/browse/UIMA-3374
>             Project: UIMA
>          Issue Type: Improvement
(Continue reading)

Jerry Cwiklik (JIRA | 23 Apr 23:09 2015
Picon

[jira] [Created] (UIMA-4363) DUCC JP not handling errors while serializing process exceptions

Jerry Cwiklik created UIMA-4363:
-----------------------------------

             Summary: DUCC JP not handling errors while serializing process exceptions
                 Key: UIMA-4363
                 URL: https://issues.apache.org/jira/browse/UIMA-4363
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 2.0.0-Ducc

When an AE throws an exception from process(), the JP serializes the exception and sends it back to the JD. If
the annotator designer throws an exception that is not serializable, the JP fails and the JD is not
notified of a process failure. 
Modify code to catch exceptions while serializing and send back serialized RuntimeException with an
appropriate message directing user to look at JP log for more details.

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


Gmane