Jerry Cwiklik (JIRA | 31 Jul 21:15 2015
Picon

[jira] [Created] (UIMA-4546) UIMA-AS client not recovering when broker connection is lost

Jerry Cwiklik created UIMA-4546:
-----------------------------------

             Summary: UIMA-AS client not recovering when broker connection is lost
                 Key: UIMA-4546
                 URL: https://issues.apache.org/jira/browse/UIMA-4546
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
    Affects Versions: 2.6.0AS
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 2.6.1AS

The UIMA-AS client reports:

Jul 31, 2015 1:35:50 PM org.apache.uima.adapter.jms.client.ActiveMQMessageSender reject
INFO: UIMA AS Client Message Dispatcher Rejecting Process Request - the Broker Is Not Available.
Jul 31, 2015 1:35:50 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl handleException
INFO: Received Exception In Message From Service on Queue:UimaASClient Broker: tcp://broker1:61616
Cas Identifier:94c42d8:14ee51d8e71:-783c Exception:org.a\
pache.uima.jms.error.handler.BrokerConnectionException: Unable To Deliver Message To
Destination. Connection To Broker tcp://broker1:61616 Has Been Lost

Jul 31, 2015 1:35:50 PM
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl$SharedConnection retryConnectionUntilSuccessfull
WARNING: UIMA AS Client Has Lost Connection To Broker:tcp://broker1:61616 Retrying Connection every
5secs until successful. Is Client Stopped:
Jul 31, 2015 1:35:50 PM 
(Continue reading)

Jerry Cwiklik (JIRA | 31 Jul 15:58 2015
Picon

[jira] [Updated] (UIMA-4397) DUCC Agent throws NumberFormatException when scraping cpu time from top


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

Jerry Cwiklik updated UIMA-4397:
--------------------------------
    Fix Version/s:     (was: future-DUCC)
                   2.0.0-Ducc

> DUCC Agent throws NumberFormatException when scraping cpu time from top
> -----------------------------------------------------------------------
>
>                 Key: UIMA-4397
>                 URL: https://issues.apache.org/jira/browse/UIMA-4397
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.0.0-Ducc
>
>
> An agent collects per process CPU stats by using the following: 
>  top -b -n 1 -p "+pid+" | tail -n 2 | head -n 1 | awk '{print $9}';
> The above seems to cause a NumberFormatException while trying to convert scraped output into an integer.
The exception is:
> java.lang.NumberFormatException: For input string: "%CPU"
>         at java.lang.NumberFormatException.forInputString(NumberFormatException.java:76)
>         at java.lang.Integer.parseInt(Integer.java:492)
>         at java.lang.Integer.valueOf(Integer.java:593)
(Continue reading)

Jerry Cwiklik (JIRA | 31 Jul 15:44 2015
Picon

[jira] [Updated] (UIMA-4540) DUCC JP does not publish final AE init stats when it completes initialization


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

Jerry Cwiklik updated UIMA-4540:
--------------------------------
    Fix Version/s:     (was: 2.1.0-Ducc)
                   2.0.0-Ducc

> DUCC JP does not publish final AE init stats when it completes initialization
> -----------------------------------------------------------------------------
>
>                 Key: UIMA-4540
>                 URL: https://issues.apache.org/jira/browse/UIMA-4540
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.0.0-Ducc
>
>
> When a JP is launched, it starts an executor which spins a thread every 20 seconds to collect AE
initialization status which is published to an agent.
> When all AEs initialize, a JP stops the executor and a reporting thread preventing the final update from
being sent to an agent. The WS in such case is never updated and shows stale information.
> Fix: modifiy JobProcessComponent.start() to force an update to an agent before stopping the executor..

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

Apache Jenkins Server | 31 Jul 03:58 2015
Picon

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

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

Jaroslaw Cwiklik | 30 Jul 21:34 2015
Picon

[VOTE] [CANCEL] Release UIMA-DUCC 2.0.0 RC6

Hi, I am cancelling the vote due to the following issues:

- Ducc documentation states that cgroups are enabled by default but
  in default.ducc.properties cgroups are disabled.

- The TimeInit window shows some AEs in Initialize state even though
   the JP process is terminated

Thanks to those who voted

-jerry
Marshall Schor (JIRA | 29 Jul 16:46 2015
Picon

[jira] [Resolved] (UIMA-4545) build of uimaj-ep-launcher needs updated bundle plugin


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

Marshall Schor resolved UIMA-4545.
----------------------------------
    Resolution: Fixed

> build of uimaj-ep-launcher needs updated bundle plugin
> ------------------------------------------------------
>
>                 Key: UIMA-4545
>                 URL: https://issues.apache.org/jira/browse/UIMA-4545
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Eclipse plugins
>    Affects Versions: 2.8.1SDK
>         Environment: Eclipse "Mars"
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.8.2SDK
>
>
> While running with Eclipse MARS (the latest) I found that the ep-launcher was not building - the maven
bundle plugin (version 2.3.7) complained of some "manifest" error.  Upgrading this to 2.5.0 (the current
level) got rid of the problem.  But when I upgraded this in the parent pom for uimaj, some other plugin
started failing to build, giving an error "default package '.' not permitted,
org.apache.uima.cas.impl.  
> I didn't track this down; I just kept the 2.3.7 version in the uimaj-parent pom, and changed the pom for
(Continue reading)

Marshall Schor (JIRA | 29 Jul 16:45 2015
Picon

[jira] [Created] (UIMA-4545) build of uimaj-ep-launcher needs updated bundle plugin

Marshall Schor created UIMA-4545:
------------------------------------

             Summary: build of uimaj-ep-launcher needs updated bundle plugin
                 Key: UIMA-4545
                 URL: https://issues.apache.org/jira/browse/UIMA-4545
             Project: UIMA
          Issue Type: Improvement
          Components: Eclipse plugins
    Affects Versions: 2.8.1SDK
         Environment: Eclipse "Mars"
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor
             Fix For: 2.8.2SDK

While running with Eclipse MARS (the latest) I found that the ep-launcher was not building - the maven
bundle plugin (version 2.3.7) complained of some "manifest" error.  Upgrading this to 2.5.0 (the current
level) got rid of the problem.  But when I upgraded this in the parent pom for uimaj, some other plugin
started failing to build, giving an error "default package '.' not permitted,
org.apache.uima.cas.impl.  

I didn't track this down; I just kept the 2.3.7 version in the uimaj-parent pom, and changed the pom for
uimaj-ep-launcher to 2.5.0.

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

(Continue reading)

Marshall Schor (JIRA | 29 Jul 16:14 2015
Picon

[jira] [Created] (UIMA-4544) uv3x autoJCasGen using ASM experiments

Marshall Schor created UIMA-4544:
------------------------------------

             Summary: uv3x autoJCasGen using ASM experiments
                 Key: UIMA-4544
                 URL: https://issues.apache.org/jira/browse/UIMA-4544
             Project: UIMA
          Issue Type: New Feature
          Components: Core Java Framework
            Reporter: Marshall Schor
            Assignee: Marshall Schor

Jira for changes related to experiments for UIMA version 3 approaches to JCasGen that uses ASM generation
at start of run.

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

Marshall Schor | 28 Jul 19:21 2015

[VOTE] Release UIMA SDK 2.8.1 - rc1

Hi,

I've posted the UIMAJ SDK 2.8.1 rc1 release candidate.  

This version has mainly bug fixes for issues found as 2.8.0 got a bit wider use.

The list of changes in Jira: 

https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.8.1SDK%20AND%20project%20%3D%20UIMA

The source and binary zip/tars and the Eclipse update site are staged to
http://people.apache.org/~schor/uima-release-candidates/uimaj-2.8.1-rc1/
<http://people.apache.org/%7Eschor/uima-release-candidates/uimaj-2.8.1-rc1/>

The Maven artifacts are here: 
https://repository.apache.org/content/repositories/orgapacheuima-1067

The SVN tags are here:
http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.8.1/

and for the Eclipse Update Site:
http://people.apache.org/~schor/uima-release-candidates/uimaj-2.8.1-rc1/eclipse-update-site/uimaj/
<http://people.apache.org/%7Eschor/uima-release-candidates/uimaj-2.8.1-rc1/eclipse-update-site/uimaj/>

See http://uima.apache.org/testing-builds.html for suggestions on how to test
release candidates.

Please vote on release:

[ ] +1 OK to release
(Continue reading)

Marshall Schor (JIRA | 28 Jul 15:56 2015
Picon

[jira] [Created] (UIMA-4543) Add UIMA nature popping up large blank extra dialog box

Marshall Schor created UIMA-4543:
------------------------------------

             Summary: Add UIMA nature popping up large blank extra dialog box
                 Key: UIMA-4543
                 URL: https://issues.apache.org/jira/browse/UIMA-4543
             Project: UIMA
          Issue Type: Bug
          Components: Eclipse plugins
    Affects Versions: 2.8.0SDK
         Environment: Works OK on windows, fails on Linux.  Works OK on Eclipse versions before MARS, fails on MARS
            Reporter: Marshall Schor
            Priority: Minor

When using the right-context-menu action of Adding Uima Nature to a project, (MARS + LINUX), the dialog box
that pops up has a background large empty box that also pops up.  When the intended dialog box is dismissed,
the large background empty box remains.  It can be dismissed by closing it via the "x".  The add UIMA nature
action seems to be ok.

Other dialog boxes (e.g., adding a Type to the type system using the component descriptor editor) seem to
work OK without this extra blank box.

Investigate and fix

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

Marshall Schor (JIRA | 28 Jul 15:06 2015
Picon

[jira] [Updated] (UIMA-4499) Pears and local External Resources


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

Marshall Schor updated UIMA-4499:
---------------------------------
    Description: 
Currently, the design for External Resources presumes they can be used by any annotator, including those
with a PEAR.  This is supported by having UIMA load resources associated with External Resources using the
main UIMA class loader, and in particular, not using the PEAR's special isolating class loader.

This causes an issue if part of the PEAR code references the same classes as the external resource, and these
are found in the PEAR class path.  You end up with two different versions of the class, loaded under
different class loaders (one the main UIMA class loader, the other, the special class loader for the
PEAR), and things break. 

A possible fix is to treat external resource definitions that occur with a PEAR as only visible to that PEAR,
and load them under the PEAR's class loader.

  was:
Currently, the design for External Resources presumes they can be used by any annotator, including those
with a PEAR.  This is supported by having UIMA load resources associated with External Resources using the
main UIMA class loader, and in particular, not using the PEAR's special isolating class loader.

This causes an issue if part of the PEAR code references the same classes as the external resource, and these
are found in the PEAR class path.  You end up with two different versions of the class, loaded under the same
class loader, and things break. 

A possible fix is to treat external resource definitions that occur with a PEAR as only visible to that PEAR,
and load them under the PEAR's class loader.
(Continue reading)


Gmane