[jira] [Updated] (UIMA-6487) Support Aggregate Engines in Apache UIMACPP
[ https://issues.apache.org/jira/browse/UIMA-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pablo Duboue updated UIMA-6487: --- Description: UIMA is a framework for unstructured information management, built around the idea of heavy annotators interoperating using a common exchange format. It has been in production use for about two decades. The framework is mostly written in Java. It has a C++ counterpart that implements a subset of the framework. The challenge for this GSOC is to work together with the mentor to implement the full framework. More details on GitHub: [https://github.com/apache/uima-uimacpp/issues/6] h2. Benefits to the community This has been discussed as one of the main roadblocks in using the C++ version of the framework by its users: [https://lists.apache.org/thread/f1r3sghgn2oqhvzz27y26zg6j3olv8qq] On a larger perspective, there is the question of why we need NLP frameworks in 2024. The field has moved to approaches where source text is consumed in a destructive tokenization process that generates subtoken indices over a fixed vocabulary. These are then fed as input to a deep/transformer neural network. Now, when training said networks, particularly when building Large Language Models (LLMs), gargantuan amounts of texts are quickly tokenized and fed into the model being trained. Additional computational efforts at indexing time can help improve data quality, privacy and terms of use of the text. A high performant UIMA CPP can be the missing piece for quality input data to LLMs. h2. Technical Skills Working on this problem requires intermediate knowledge of the C++ programming language. A solution will most probably exercise this type of skills, which could be learned along the way parallel to the project (mentoring on these topics is not part of the project): * Linux command-line and build systems * XML parsing * Docker (image creation, deployment, debugging) h2. About the mentor Dr. Duboue has more than 25 years of experience in AI. He has a Ph.D. in Computer Science from Columbia University. and was a member of the IBM Watson team that beat the Jeopardy! Champions. Aside from his consulting work, he he has taught in three different countries and done joint research with more than fifty co-authors. He has years of experience mentoring both students and employees. was: UIMA is a framework for unstructured information management, built around the idea of heavy annotators interoperating using a common exchange format. It has been in production use for about two decades. The framework is mostly written in Java. It has a C++ counterpart that implements a subset of the framework. The challenge for this GSOC is to work together with the mentor to implement the full framework. More details on GitHub: [https://github.com/apache/uima-uimacpp/issues/6] Benefits to the community This has been discussed as one of the main roadblocks in using the C++ version of the framework by its users: [https://lists.apache.org/thread/f1r3sghgn2oqhvzz27y26zg6j3olv8qq] About the mentor Dr. Duboue has more than 25 years of experience in AI. He has a Ph.D. in Computer Science from Columbia University. and was a member of the IBM Watson team that beat the Jeopardy! Champions. Aside from his consulting work, he he has taught in three different countries and done joint research with more than fifty co-authors. He has years of experience mentoring both students and employees. > Support Aggregate Engines in Apache UIMACPP > --- > > Key: UIMA-6487 > URL: https://issues.apache.org/jira/browse/UIMA-6487 > Project: UIMA > Issue Type: New Feature >Reporter: Pablo Duboue >Priority: Major > Labels: NLP, full-time, gsoc2024, mentor, uima > > UIMA is a framework for unstructured information management, built around the > idea of heavy annotators interoperating using a common exchange format. > It has been in production use for about two decades. > The framework is mostly written in Java. It has a C++ counterpart that > implements a subset of the framework. > The challenge for this GSOC is to work together with the mentor to implement > the full framework. > More details on GitHub: [https://github.com/apache/uima-uimacpp/issues/6] > h2. Benefits to the community > This has been discussed as one of the main roadblocks in using the C++ > version of the framework by its users: > [https://lists.apache.org/thread/f1r3sghgn2oqhvzz27y26zg6j3olv8qq] > On a larger perspective, there is the question of why we need NLP frameworks > in 2024. The field has moved to approaches where source text is consumed in a > destructive tokenization process that generates subtoken indices over a
[jira] [Moved] (UIMA-6487) Support Aggregate Engines in Apache UIMACPP
[ https://issues.apache.org/jira/browse/UIMA-6487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik moved GSOC-264 to UIMA-6487: - Key: UIMA-6487 (was: GSOC-264) Workflow: classic default workflow (was: Default workflow, editable Closed status) Project: UIMA (was: Comdev GSOC) > Support Aggregate Engines in Apache UIMACPP > --- > > Key: UIMA-6487 > URL: https://issues.apache.org/jira/browse/UIMA-6487 > Project: UIMA > Issue Type: New Feature >Reporter: Pablo Duboue >Priority: Major > Labels: NLP, full-time, gsoc2024, mentor, uima > > UIMA is a framework for unstructured information management, built around the > idea of heavy annotators interoperating using a common exchange format. > It has been in production use for about two decades. > The framework is mostly written in Java. It has a C++ counterpart that > implements a subset of the framework. > The challenge for this GSOC is to work together with the mentor to implement > the full framework. > More details on GitHub: [https://github.com/apache/uima-uimacpp/issues/6] > > Benefits to the community > This has been discussed as one of the main roadblocks in using the C++ > version of the framework by its users: > [https://lists.apache.org/thread/f1r3sghgn2oqhvzz27y26zg6j3olv8qq] > > About the mentor > Dr. Duboue has more than 25 years of experience in AI. He has a Ph.D. in > Computer Science from Columbia University. and was a member of the IBM Watson > team that beat the Jeopardy! Champions. > Aside from his consulting work, he he has taught in three different countries > and done joint research with more than fifty co-authors. > He has years of experience mentoring both students and employees. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4089) make xml comparisons in test cases use xml unit
[ https://issues.apache.org/jira/browse/UIMA-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4089. -- Assignee: (was: Marshall Schor) Resolution: Done Over time, we actually have migrated various tests over to XMLUnit. > make xml comparisons in test cases use xml unit > --- > > Key: UIMA-4089 > URL: https://issues.apache.org/jira/browse/UIMA-4089 > Project: UIMA > Issue Type: Test > Components: Core Java Framework >Affects Versions: 2.6.0SDK >Reporter: Marshall Schor >Priority: Minor > > Saw some errors being reported by Jenkins due to different styles of xml end > tags being compared for string equal. Use XML Unit to avoid these being > considered as errors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-2546) Add author extraction service
[ https://issues.apache.org/jira/browse/UIMA-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-2546. -- Resolution: Abandoned Issue has received no attention over the last years - closing. > Add author extraction service > - > > Key: UIMA-2546 > URL: https://issues.apache.org/jira/browse/UIMA-2546 > Project: UIMA > Issue Type: Improvement > Components: addons >Affects Versions: 2.3.1Addons >Reporter: Tommaso Teofili >Priority: Major > > Add the 'author extraction service' (see > http://www.alchemyapi.com/api/author/) to AlchemyAPI Annotator. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-1290) Need a Way to Determine if Two Type Systems Are Compatible
[
https://issues.apache.org/jira/browse/UIMA-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-1290.
--
Resolution: Not A Problem
Seems like the need for this has disappeared. That said, actually the core UIMA
Java SDK has an internal functionality to de-duplicate type systems to reduce
memory usage. Cf. system property {{uima.disable_typesystem_consolidation}}.
This functionality works by comparing type systems as to whether they are
identical. As far as I can tell, this is simply implemented through
{{TypeSystemImpl.equals(other)}}.
> Need a Way to Determine if Two Type Systems Are Compatible
> --
>
> Key: UIMA-1290
> URL: https://issues.apache.org/jira/browse/UIMA-1290
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
>Affects Versions: 2.3
>Reporter: Jaroslaw Cwiklik
>Priority: Major
>
> Uima AS client needs to validate that the type system returned from a Uima AS
> service is compatible. In case when a binary serialization is used, the type
> systems *must* be identical. For XMI serialization, the type system of the
> delegate*must* be compatible but not necessarily identical. The core should
> provide an API which will enable the validation of type systems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (UIMA-2546) Add author extraction service
[ https://issues.apache.org/jira/browse/UIMA-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-2546: - Fix Version/s: (was: 2.4.0Addons) > Add author extraction service > - > > Key: UIMA-2546 > URL: https://issues.apache.org/jira/browse/UIMA-2546 > Project: UIMA > Issue Type: Improvement > Components: addons >Affects Versions: 2.3.1Addons >Reporter: Tommaso Teofili >Priority: Major > > Add the 'author extraction service' (see > http://www.alchemyapi.com/api/author/) to AlchemyAPI Annotator. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (UIMA-3004) Investigate memory consumption of TextRuler framework
[ https://issues.apache.org/jira/browse/UIMA-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Klügl closed UIMA-3004. - Resolution: Won't Fix > Investigate memory consumption of TextRuler framework > - > > Key: UIMA-3004 > URL: https://issues.apache.org/jira/browse/UIMA-3004 > Project: UIMA > Issue Type: Task > Components: Ruta >Affects Versions: 2.1.0ruta >Reporter: Peter Klügl >Assignee: Peter Klügl >Priority: Major > > Investigate memory consumption of TextRuler framework: Some rule induction > algorithms did not finish in a normal learning setting (java heap space). A > first simple profiling pointed to the maps in RutaBasic, which used about 1GB. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3132) uimaFIT maven plugins do not run on ASF Jenkins slave "windows1"
[
https://issues.apache.org/jira/browse/UIMA-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-3132.
--
Resolution: Works for Me
Never ran into this issue again...
> uimaFIT maven plugins do not run on ASF Jenkins slave "windows1"
>
>
> Key: UIMA-3132
> URL: https://issues.apache.org/jira/browse/UIMA-3132
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT-Maven-Plugin
>Affects Versions: 2.0.0uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> Getting this error:
> {noformat}
> Caused by: java.lang.IllegalStateException: ${maven.home} is not specified as
> a directory: 'F:\hudson\tools\maven\latest3'.
> at
> org.apache.maven.shared.invoker.MavenCommandLineBuilder.findMavenExecutable(MavenCommandLineBuilder.java:475)
> at
> org.apache.maven.shared.invoker.MavenCommandLineBuilder.build(MavenCommandLineBuilder.java:68)
> at
> org.apache.maven.shared.invoker.DefaultInvoker.execute(DefaultInvoker.java:91)
> at
> org.apache.maven.plugin.invoker.AbstractInvokerMojo.runBuild(AbstractInvokerMojo.java:1493)
> at
> org.apache.maven.plugin.invoker.AbstractInvokerMojo.runBuild(AbstractInvokerMojo.java:1214)
> at
> org.apache.maven.plugin.invoker.AbstractInvokerMojo.runBuilds(AbstractInvokerMojo.java:1133)
> at
> org.apache.maven.plugin.invoker.AbstractInvokerMojo.execute(AbstractInvokerMojo.java:670)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (UIMA-3004) Investigate memory consumption of TextRuler framework
[ https://issues.apache.org/jira/browse/UIMA-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681333#comment-17681333 ] Richard Eckart de Castilho commented on UIMA-3004: -- [~pkluegl] Can we close this one? The issue does not really describe how to reproduce the problem (e.g. which rule induction algorithms need to be investigated) and the issue didn't draw any more attention the last like 10 years... > Investigate memory consumption of TextRuler framework > - > > Key: UIMA-3004 > URL: https://issues.apache.org/jira/browse/UIMA-3004 > Project: UIMA > Issue Type: Task > Components: Ruta >Affects Versions: 2.1.0ruta >Reporter: Peter Klügl >Assignee: Peter Klügl >Priority: Major > > Investigate memory consumption of TextRuler framework: Some rule induction > algorithms did not finish in a normal learning setting (java heap space). A > first simple profiling pointed to the maps in RutaBasic, which used about 1GB. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5520) Fix docs for job descriptor overrides
[ https://issues.apache.org/jira/browse/UIMA-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5520. -- Resolution: Abandoned DUCC is being retired. > Fix docs for job descriptor overrides > - > > Key: UIMA-5520 > URL: https://issues.apache.org/jira/browse/UIMA-5520 > Project: UIMA > Issue Type: Bug >Reporter: Rong Li >Priority: Major > > Overrides are blank not comma separated -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5900) SM should delay starting custom service pingers
[ https://issues.apache.org/jira/browse/UIMA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5900. -- Resolution: Abandoned DUCC is being retired. > SM should delay starting custom service pingers > --- > > Key: UIMA-5900 > URL: https://issues.apache.org/jira/browse/UIMA-5900 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 2.2.2-Ducc >Reporter: Eddie Epstein >Priority: Major > > in v2.2.2 custom services can connect to the agent and report states = > initializing and running. This may take several seconds after the service > instance is started. Currently the SM starts a custom service pinger as soon > as it is notified that the first instance is started. A delay is needed to > detect that the instance has reported itself as initializing in which case > the pinger should not be started until an instance reports itself running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5862) RM can fail with a comparator violating its general contract
[ https://issues.apache.org/jira/browse/UIMA-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5862. -- Resolution: Abandoned DUCC is being retired. > RM can fail with a comparator violating its general contract > > > Key: UIMA-5862 > URL: https://issues.apache.org/jira/browse/UIMA-5862 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Major > > Problem is JobByTimeSorter in NodepoolScheduler -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6114) Add the experiments page code
[ https://issues.apache.org/jira/browse/UIMA-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6114. -- Resolution: Abandoned DUCC is being retired. > Add the experiments page code > - > > Key: UIMA-6114 > URL: https://issues.apache.org/jira/browse/UIMA-6114 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Major > > Adds the Experiments button ... could be made optional. > Code checks if each Job or AP is a child of an experiment ... will display an > empty page if none found. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6201) Analysis engine Enhancement
[ https://issues.apache.org/jira/browse/UIMA-6201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6201. -- Assignee: Richard Eckart de Castilho Resolution: Information Provided > Analysis engine Enhancement > --- > > Key: UIMA-6201 > URL: https://issues.apache.org/jira/browse/UIMA-6201 > Project: UIMA > Issue Type: Question > Components: UIMA >Reporter: dhinesh >Assignee: Richard Eckart de Castilho >Priority: Major > > Hi Friends, > can any one suggest me how to filter specific class annotations from the > chunk of annotations. > For Example > I am getting output as > org.apache.ctakes.typesystem.type.syntax.PRT > org.apache.ctakes.typesystem.type.syntax.PP > org.apache.ctakes.typesystem.type.OntologyConcept > etc > I need output only as > org.apache.ctakes.typesystem.type.OntologyConcept > Where do I restrict for my specific class annotations in analysis engine. > Thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6442) Avoid artifactory.openntf.org being used outside Eclipse modules
[ https://issues.apache.org/jira/browse/UIMA-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6442. -- Resolution: Not A Problem This being a problem was just a hypothesis. Recently, I did not notice slowness due to openntf, so I'm closing this. If necessary, re-open on GitHub. > Avoid artifactory.openntf.org being used outside Eclipse modules > > > Key: UIMA-6442 > URL: https://issues.apache.org/jira/browse/UIMA-6442 > Project: UIMA > Issue Type: Improvement > Components: Build, Packaging and Test >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > Avoid artifactory.openntf.org being used outside Eclipse modules - this could > speed up the build and the P2 repos are not needed outside the Eclipse > modules. Either move to an intermediate parent pom or move into a profile. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (UIMA-6442) Avoid artifactory.openntf.org being used outside Eclipse modules
[ https://issues.apache.org/jira/browse/UIMA-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6442: - Fix Version/s: (was: 3.4.1SDK) > Avoid artifactory.openntf.org being used outside Eclipse modules > > > Key: UIMA-6442 > URL: https://issues.apache.org/jira/browse/UIMA-6442 > Project: UIMA > Issue Type: Improvement > Components: Build, Packaging and Test >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > > Avoid artifactory.openntf.org being used outside Eclipse modules - this could > speed up the build and the P2 repos are not needed outside the Eclipse > modules. Either move to an intermediate parent pom or move into a profile. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4563) Traffic monitoring using Google Analytics
[ https://issues.apache.org/jira/browse/UIMA-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4563. -- Resolution: Done > Traffic monitoring using Google Analytics > - > > Key: UIMA-4563 > URL: https://issues.apache.org/jira/browse/UIMA-4563 > Project: UIMA > Issue Type: Improvement > Components: Website >Reporter: Richard Eckart de Castilho >Priority: Major > > Apparently, the ASF main page uses Google Analytics now as well, so I think > we can also do that - they have privacy statement that we can simply reuse. > http://www.apache.org/foundation/policies/privacy.html -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6335) Optimize release process
[
https://issues.apache.org/jira/browse/UIMA-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6335.
--
Resolution: Done
Most points have been addressed. If the remaining open points remain pain
points, open new issues for them on the GitHub issue tracker.
> Optimize release process
>
>
> Key: UIMA-6335
> URL: https://issues.apache.org/jira/browse/UIMA-6335
> Project: UIMA
> Issue Type: Improvement
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The release checklist is pretty long. To facilitate releases, we should see
> what can be optimized / cut.
> - (/) {{README.md}} becomes version-independent and contains a proper project
> description suitable as a GitHub repo landing page
> - (/) {{RELEASE_NOTES.md}} contains only version-specific release notes and
> can be largely copy/pasted to the release announcments mail/website/etc.
> - (/) [uimaFIT] Drop the binary release package of uimaFIT - the source
> release and obtaining the artifacts via Maven Central should be sufficient
> (UIMA-6448)
> - (/) [UIMAJ] Integrate building of Eclipse update sites into the build
> (UIMA-6443)
> - (/) [RUTA] Integrate building of Eclipse update sites into the build (part
> of UIMA-6447)
> - (/) [UIMAJ] Use RC-auto-staging from Parent POM 15
> - (/) [uimaFIT] Use RC-auto-staging from Parent POM 15
> - (/) [RUTA] Use RC-auto-staging from Parent POM 15
> - (x) [UIMAJ] Put the examples in the UIMA Java SDK into a form where they
> are convenient to use form the source distribution or find some other way of
> providing them which does not require binary release package. In particular,
> they should not be Eclipse projects but rather regular Maven projects
> - (x) [UIMAJ] Drop the binary release package of UIMA Java SDK - the source
> release and obtaining the artifacts via Maven Central should be sufficient -
> will safe us from having to maintain the LICENSE/NOTICE files for binary
> releases
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-6428) cas.select(TOP.class).count() has unexpected result
[ https://issues.apache.org/jira/browse/UIMA-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6428. -- Fix Version/s: (was: 3.4.1SDK) Resolution: Duplicate > cas.select(TOP.class).count() has unexpected result > --- > > Key: UIMA-6428 > URL: https://issues.apache.org/jira/browse/UIMA-6428 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Reporter: Richard Eckart de Castilho >Priority: Major > > Calling cas.select(TOP.class).count() returns a very large long number - > probably Long.MAX_VALUE. It is a bit unexpected... To get an accurate number, > one has to call cas.select(TOP.class).asList().size(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (UIMA-6428) cas.select(TOP.class).count() has unexpected result
[ https://issues.apache.org/jira/browse/UIMA-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17681321#comment-17681321 ] Richard Eckart de Castilho commented on UIMA-6428: -- Issue has moved here and has been resolved: https://github.com/apache/uima-uimaj/issues/272 > cas.select(TOP.class).count() has unexpected result > --- > > Key: UIMA-6428 > URL: https://issues.apache.org/jira/browse/UIMA-6428 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Reporter: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.1SDK > > > Calling cas.select(TOP.class).count() returns a very large long number - > probably Long.MAX_VALUE. It is a bit unexpected... To get an accurate number, > one has to call cas.select(TOP.class).asList().size(). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (UIMA-6444) Automatically sign Eclipse plugins during release builds
[ https://issues.apache.org/jira/browse/UIMA-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6444: - Fix Version/s: 3.4.1SDK (was: 3.4.0SDK) > Automatically sign Eclipse plugins during release builds > > > Key: UIMA-6444 > URL: https://issues.apache.org/jira/browse/UIMA-6444 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.1SDK > > > *Note:* we do have detached PGP signatures for the Eclipse update site > artifacts - it is mandatory according to the ASF release policy - but they > are currently not included in such a way that Eclipse can verify them and > offer the user to trust them during the plugin installation process. > > Currently, we do not sign the Eclipse plugins because it is extra effort and > the old way of using the Symantec Service are gone anyway. > There is a new jarsigning approach which could be used. > Alternatively, it is meanwhile possible to embed PGP signatures in P2 > repositories. > Let's see which of these options are viable for us. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (UIMA-6442) Avoid artifactory.openntf.org being used outside Eclipse modules
[ https://issues.apache.org/jira/browse/UIMA-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6442: - Fix Version/s: 3.4.1SDK (was: 3.4.0SDK) > Avoid artifactory.openntf.org being used outside Eclipse modules > > > Key: UIMA-6442 > URL: https://issues.apache.org/jira/browse/UIMA-6442 > Project: UIMA > Issue Type: Improvement > Components: Build, Packaging and Test >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.1SDK > > > Avoid artifactory.openntf.org being used outside Eclipse modules - this could > speed up the build and the P2 repos are not needed outside the Eclipse > modules. Either move to an intermediate parent pom or move into a profile. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (UIMA-6468) Problem with JCas classes with re-used across different type systems
[ https://issues.apache.org/jira/browse/UIMA-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6468: - Fix Version/s: 3.4.1SDK (was: 3.4.0SDK) > Problem with JCas classes with re-used across different type systems > > > Key: UIMA-6468 > URL: https://issues.apache.org/jira/browse/UIMA-6468 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.1SDK > > > When a JCas wrapper class is loaded, its features are bound to "index" > positions in the type system available at the time that they are loaded. > Normally this works great, even if different type systems are used because > the features defined by the JCas classes have priority and thereby receive > stable index positions. > However, there can be problems in situations where multiple classloaders are > involved such that a JCas class that has been bound to one indexes in type > system would later be bound to other indexes in slightly different type > system, e.g. because the available features change (in a reasonably > "compatible" way). > It would be nice if UIMA had a solution for this type of problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6478) ManagedCas test utility not usable
[
https://issues.apache.org/jira/browse/UIMA-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6478.
--
Fix Version/s: (was: 3.4.0SDK)
Resolution: Not A Problem
> ManagedCas test utility not usable
> --
>
> Key: UIMA-6478
> URL: https://issues.apache.org/jira/browse/UIMA-6478
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
>Priority: Major
>
> The ManagedCas and ManagedJCas classes had been rules for JUnit 4. While
> porting to JUnit 5, there were turned into TestWatchers - but that currently
> makes them hardly usable because watchers / extensions seem to be normally
> instantiated by JUnit itself and then we have no access to the contained CAS.
> Looks like these classes should rather work like {{@TempDir}} in JUnit 5.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (UIMA-6486) Fix for FileUtil vulnerability in UIMA 2.*?
[ https://issues.apache.org/jira/browse/UIMA-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679776#comment-17679776 ] Richard Eckart de Castilho commented on UIMA-6486: -- There are no plans to release any new versions of the 2.x line. We have even removed references to v2 from the website recently - it is no longer supported. The suggested course of action is to upgrade to v3. Alternatively, you can fix the issue yourself and perform an internal release. Or you could become a contributor, fix v2 and propose to prepare a new release yourself. New contributors are always welcome. We also do not use Jira anymore. Please open issues in the GitHub issue tracker: https://github.com/apache/uima-uimaj/issues/new/choose > Fix for FileUtil vulnerability in UIMA 2.*? > --- > > Key: UIMA-6486 > URL: https://issues.apache.org/jira/browse/UIMA-6486 > Project: UIMA > Issue Type: Bug >Affects Versions: 2.11.0SDK >Reporter: Benjamin De Boe >Priority: Major > > Hi, > we distribute a custom annotator built on UIMA v2, which is affected by > https://nvd.nist.gov/vuln/detail/CVE-2022-32287. We do not have any near-term > bandwidth to upgrade our library to v3, and more critically some of our > customers have other pipelines still running on v2 that they may not be able > to migrate to v3 any time soon. > Are there any plans to deliver a new v2.11 bugfix release that addresses this > vulnerability? > Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (UIMA-6486) Fix for FileUtil vulnerability in UIMA 2.*?
[ https://issues.apache.org/jira/browse/UIMA-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17679777#comment-17679777 ] Benjamin De Boe commented on UIMA-6486: --- It seems this was addressed for v3.3.* through UIMA-6469 (well, that's a half-educated guess) > Fix for FileUtil vulnerability in UIMA 2.*? > --- > > Key: UIMA-6486 > URL: https://issues.apache.org/jira/browse/UIMA-6486 > Project: UIMA > Issue Type: Bug >Affects Versions: 2.11.0SDK >Reporter: Benjamin De Boe >Priority: Major > > Hi, > we distribute a custom annotator built on UIMA v2, which is affected by > https://nvd.nist.gov/vuln/detail/CVE-2022-32287. We do not have any near-term > bandwidth to upgrade our library to v3, and more critically some of our > customers have other pipelines still running on v2 that they may not be able > to migrate to v3 any time soon. > Are there any plans to deliver a new v2.11 bugfix release that addresses this > vulnerability? > Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6486) Fix for FileUtil vulnerability in UIMA 2.*?
[ https://issues.apache.org/jira/browse/UIMA-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6486. -- Resolution: Abandoned Marking issue as abandoned as Jira is no longer used. > Fix for FileUtil vulnerability in UIMA 2.*? > --- > > Key: UIMA-6486 > URL: https://issues.apache.org/jira/browse/UIMA-6486 > Project: UIMA > Issue Type: Bug >Affects Versions: 2.11.0SDK >Reporter: Benjamin De Boe >Assignee: Richard Eckart de Castilho >Priority: Major > > Hi, > we distribute a custom annotator built on UIMA v2, which is affected by > https://nvd.nist.gov/vuln/detail/CVE-2022-32287. We do not have any near-term > bandwidth to upgrade our library to v3, and more critically some of our > customers have other pipelines still running on v2 that they may not be able > to migrate to v3 any time soon. > Are there any plans to deliver a new v2.11 bugfix release that addresses this > vulnerability? > Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (UIMA-6486) Fix for FileUtil vulnerability in UIMA 2.*?
[ https://issues.apache.org/jira/browse/UIMA-6486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho reassigned UIMA-6486: Assignee: Richard Eckart de Castilho > Fix for FileUtil vulnerability in UIMA 2.*? > --- > > Key: UIMA-6486 > URL: https://issues.apache.org/jira/browse/UIMA-6486 > Project: UIMA > Issue Type: Bug >Affects Versions: 2.11.0SDK >Reporter: Benjamin De Boe >Assignee: Richard Eckart de Castilho >Priority: Major > > Hi, > we distribute a custom annotator built on UIMA v2, which is affected by > https://nvd.nist.gov/vuln/detail/CVE-2022-32287. We do not have any near-term > bandwidth to upgrade our library to v3, and more critically some of our > customers have other pipelines still running on v2 that they may not be able > to migrate to v3 any time soon. > Are there any plans to deliver a new v2.11 bugfix release that addresses this > vulnerability? > Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (UIMA-6486) Fix for FileUtil vulnerability in UIMA 2.*?
Benjamin De Boe created UIMA-6486: - Summary: Fix for FileUtil vulnerability in UIMA 2.*? Key: UIMA-6486 URL: https://issues.apache.org/jira/browse/UIMA-6486 Project: UIMA Issue Type: Bug Affects Versions: 2.11.0SDK Reporter: Benjamin De Boe Hi, we distribute a custom annotator built on UIMA v2, which is affected by https://nvd.nist.gov/vuln/detail/CVE-2022-32287. We do not have any near-term bandwidth to upgrade our library to v3, and more critically some of our customers have other pipelines still running on v2 that they may not be able to migrate to v3 any time soon. Are there any plans to deliver a new v2.11 bugfix release that addresses this vulnerability? Thanks! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6436) Move maintainer documentation from website into maintainer guide
[ https://issues.apache.org/jira/browse/UIMA-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6436. -- Resolution: Fixed We have a reasonable maintainer documentation in UIMA-J now. Might still consider moving that to a separate repo at some point. > Move maintainer documentation from website into maintainer guide > > > Key: UIMA-6436 > URL: https://issues.apache.org/jira/browse/UIMA-6436 > Project: UIMA > Issue Type: Task >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > Move maintainer documentation from website into maintainer guide which will > for the time being be located in the UIMA Java SDK as being the main project. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6485) NPE while deserializing an XMI in a PEAR context
[
https://issues.apache.org/jira/browse/UIMA-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6485.
--
Resolution: Duplicate
> NPE while deserializing an XMI in a PEAR context
>
>
> Key: UIMA-6485
> URL: https://issues.apache.org/jira/browse/UIMA-6485
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 3.3.1SDK
> Environment: * SO: macOS 12.6.2
> * OpenJDK Temurin 1.8.0_322
> * uimaj-core 3.3.1
>Reporter: Beni Santos
>Priority: Major
>
> When running an AAE in a PEAR context (uimaj-core 3.3.1), if a CAS Multiplier
> tries to populate a new CAS while loading it from an XMI file, a
> {{NullPointerException}} is thrown by the method
> {{maybeMakeBaseVersionForPear}} of the class {{CASImpl.java}} (line 1536).
>
> Complete failing example here:
> [https://github.com/benisantos/uima3-xmi-deserializer-in-pear]
>
> Workaround: use the uimaj-io-json library and de/serialize JSON instead of
> XMI.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (UIMA-6485) NPE while deserializing an XMI in a PEAR context
[
https://issues.apache.org/jira/browse/UIMA-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677673#comment-17677673
]
Richard Eckart de Castilho commented on UIMA-6485:
--
Thx :)
> NPE while deserializing an XMI in a PEAR context
>
>
> Key: UIMA-6485
> URL: https://issues.apache.org/jira/browse/UIMA-6485
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 3.3.1SDK
> Environment: * SO: macOS 12.6.2
> * OpenJDK Temurin 1.8.0_322
> * uimaj-core 3.3.1
>Reporter: Beni Santos
>Priority: Major
>
> When running an AAE in a PEAR context (uimaj-core 3.3.1), if a CAS Multiplier
> tries to populate a new CAS while loading it from an XMI file, a
> {{NullPointerException}} is thrown by the method
> {{maybeMakeBaseVersionForPear}} of the class {{CASImpl.java}} (line 1536).
>
> Complete failing example here:
> [https://github.com/benisantos/uima3-xmi-deserializer-in-pear]
>
> Workaround: use the uimaj-io-json library and de/serialize JSON instead of
> XMI.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (UIMA-6485) NPE while deserializing an XMI in a PEAR context
[
https://issues.apache.org/jira/browse/UIMA-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677671#comment-17677671
]
Beni Santos commented on UIMA-6485:
---
[~rec] [https://github.com/apache/uima-uimaj/issues/285]
> NPE while deserializing an XMI in a PEAR context
>
>
> Key: UIMA-6485
> URL: https://issues.apache.org/jira/browse/UIMA-6485
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 3.3.1SDK
> Environment: * SO: macOS 12.6.2
> * OpenJDK Temurin 1.8.0_322
> * uimaj-core 3.3.1
>Reporter: Beni Santos
>Priority: Major
>
> When running an AAE in a PEAR context (uimaj-core 3.3.1), if a CAS Multiplier
> tries to populate a new CAS while loading it from an XMI file, a
> {{NullPointerException}} is thrown by the method
> {{maybeMakeBaseVersionForPear}} of the class {{CASImpl.java}} (line 1536).
>
> Complete failing example here:
> [https://github.com/benisantos/uima3-xmi-deserializer-in-pear]
>
> Workaround: use the uimaj-io-json library and de/serialize JSON instead of
> XMI.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (UIMA-6485) NPE while deserializing an XMI in a PEAR context
[
https://issues.apache.org/jira/browse/UIMA-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677656#comment-17677656
]
Richard Eckart de Castilho commented on UIMA-6485:
--
Thank you for reporting the problem and creating the GitHub repo for
reproduction.
We do not use Jira anymore. Could you please open a corresponding issue on our
tracker on GitHub?
https://github.com/apache/uima-uimaj/issues
> NPE while deserializing an XMI in a PEAR context
>
>
> Key: UIMA-6485
> URL: https://issues.apache.org/jira/browse/UIMA-6485
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
>Affects Versions: 3.3.1SDK
> Environment: * SO: macOS 12.6.2
> * OpenJDK Temurin 1.8.0_322
> * uimaj-core 3.3.1
>Reporter: Beni Santos
>Priority: Major
>
> When running an AAE in a PEAR context (uimaj-core 3.3.1), if a CAS Multiplier
> tries to populate a new CAS while loading it from an XMI file, a
> {{NullPointerException}} is thrown by the method
> {{maybeMakeBaseVersionForPear}} of the class {{CASImpl.java}} (line 1536).
>
> Complete failing example here:
> [https://github.com/benisantos/uima3-xmi-deserializer-in-pear]
>
> Workaround: use the uimaj-io-json library and de/serialize JSON instead of
> XMI.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (UIMA-6485) NPE while deserializing an XMI in a PEAR context
Beni Santos created UIMA-6485:
-
Summary: NPE while deserializing an XMI in a PEAR context
Key: UIMA-6485
URL: https://issues.apache.org/jira/browse/UIMA-6485
Project: UIMA
Issue Type: Bug
Components: Core Java Framework
Affects Versions: 3.3.1SDK
Environment: * SO: macOS 12.6.2
* OpenJDK Temurin 1.8.0_322
* uimaj-core 3.3.1
Reporter: Beni Santos
When running an AAE in a PEAR context (uimaj-core 3.3.1), if a CAS Multiplier
tries to populate a new CAS while loading it from an XMI file, a
{{NullPointerException}} is thrown by the method
{{maybeMakeBaseVersionForPear}} of the class {{CASImpl.java}} (line 1536).
Complete failing example here:
[https://github.com/benisantos/uima3-xmi-deserializer-in-pear]
Workaround: use the uimaj-io-json library and de/serialize JSON instead of XMI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (UIMA-6470) RC auto staging checks out SVN even on non-release builds
[
https://issues.apache.org/jira/browse/UIMA-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677346#comment-17677346
]
Richard Eckart de Castilho commented on UIMA-6470:
--
Has been moved here: https://github.com/apache/uima-parent-pom/issues/37
> RC auto staging checks out SVN even on non-release builds
> -
>
> Key: UIMA-6470
> URL: https://issues.apache.org/jira/browse/UIMA-6470
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Affects Versions: parent-pom-15
>Reporter: Richard Eckart de Castilho
>Priority: Major
> Fix For: parent-pom-16
>
>
> The auto-staging mechanism for release candidates checks out the staging
> repository for release candidates even when there is no release build going
> on. This is a bit annoying because it requires that people that want to build
> auto-staging-enabled projects need to have SVN installed.
> This happens during SNAPSHOT CI builds as well - pretty annoying. I have to
> declare {{-Ddisable-rc-auto-staging}} in the {{Jenkinsfile}}s to get around
> this.
> Enabling the auto-staging profile by adding it to the Maven Release Plugin
> {{releaseProfiles}} would work. But then projects that do not use it have to
> override the {{releaseProfiles}} setting to remove it again or if we do not
> make it the default, then projects that use it have to override
> {{releaseProfiles}} to add it.
> Adding a {{-Dxxx}} to the {{arguments}} setting does not seem to be a great
> idea because it is more common that a developer would like to pass additional
> arguments than a developer wanting to pass additional release profiles. And
> developer-set arguments would not be accepted anymore if we hard-set the
> arguments in the release plugin - been there, done that, was not good.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-6470) RC auto staging checks out SVN even on non-release builds
[
https://issues.apache.org/jira/browse/UIMA-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-6470.
--
Fix Version/s: (was: parent-pom-16)
Resolution: Duplicate
> RC auto staging checks out SVN even on non-release builds
> -
>
> Key: UIMA-6470
> URL: https://issues.apache.org/jira/browse/UIMA-6470
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
>Affects Versions: parent-pom-15
>Reporter: Richard Eckart de Castilho
>Priority: Major
>
> The auto-staging mechanism for release candidates checks out the staging
> repository for release candidates even when there is no release build going
> on. This is a bit annoying because it requires that people that want to build
> auto-staging-enabled projects need to have SVN installed.
> This happens during SNAPSHOT CI builds as well - pretty annoying. I have to
> declare {{-Ddisable-rc-auto-staging}} in the {{Jenkinsfile}}s to get around
> this.
> Enabling the auto-staging profile by adding it to the Maven Release Plugin
> {{releaseProfiles}} would work. But then projects that do not use it have to
> override the {{releaseProfiles}} setting to remove it again or if we do not
> make it the default, then projects that use it have to override
> {{releaseProfiles}} to add it.
> Adding a {{-Dxxx}} to the {{arguments}} setting does not seem to be a great
> idea because it is more common that a developer would like to pass additional
> arguments than a developer wanting to pass additional release profiles. And
> developer-set arguments would not be accepted anymore if we hard-set the
> arguments in the release plugin - been there, done that, was not good.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (UIMA-6445) CPE not calling destroy if there was an exception
[ https://issues.apache.org/jira/browse/UIMA-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6445: - Fix Version/s: 3.4.0SDK (was: 3.3.2SDK) > CPE not calling destroy if there was an exception > - > > Key: UIMA-6445 > URL: https://issues.apache.org/jira/browse/UIMA-6445 > Project: UIMA > Issue Type: Bug > Components: Collection Processing >Affects Versions: 3.3.0SDK >Reporter: Richard Eckart de Castilho >Priority: Major > Fix For: 3.4.0SDK > > > There are indications that the CPE is not calling destroy if there was an > exception. > Need a test case for this. > Need to think if calling destroy is ok or whether it might disrupt some > functionality of CPEs (checkpoints?). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6482) Request for Visual Studio Code or IDEA Extension
[ https://issues.apache.org/jira/browse/UIMA-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6482. -- Resolution: Feedback Received > Request for Visual Studio Code or IDEA Extension > - > > Key: UIMA-6482 > URL: https://issues.apache.org/jira/browse/UIMA-6482 > Project: UIMA > Issue Type: New Feature > Components: addons, Ruta >Reporter: Yue Yang >Priority: Trivial > > Eclipse is slow and losing popularity, and I request visual studio code or > IDEA extension so that I can debug my Ruta script there. I found [one IDEA > extension|https://plugins.jetbrains.com/plugin/12212-uima-ruta-language-support] > but it is not compatible with the latest release of IntelliJ IDE now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6178) Daemons fail to start on Mac OSX
[ https://issues.apache.org/jira/browse/UIMA-6178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6178. -- Resolution: Abandoned DUCC has been retired. > Daemons fail to start on Mac OSX > > > Key: UIMA-6178 > URL: https://issues.apache.org/jira/browse/UIMA-6178 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > > Setup of JAVA_HOME is wrong for latest OS/X (Catalina) > Test for ssh-to-self may falsely succeed (on any platform) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3816) DUCC SM should support ping-only UIMA-AS services
[ https://issues.apache.org/jira/browse/UIMA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3816. -- Resolution: Abandoned DUCC has been retired. > DUCC SM should support ping-only UIMA-AS services > - > > Key: UIMA-3816 > URL: https://issues.apache.org/jira/browse/UIMA-3816 > Project: UIMA > Issue Type: New Feature > Components: DUCC >Affects Versions: 1.0.0-Ducc >Reporter: Jim Challenger >Assignee: Jim Challenger >Priority: Major > Fix For: future-DUCC > > > Currently DUCC supports only CUSTOM services as ping-only. While it is > possible to define a ping-only services that monitors a UIMA-AS service, this > is not explicit. > The new function is to allow a UIMA-AS service with no DD to be defined. > DUCC will treat this as ping-only, using the UIMA-AS ping/monitor logic > explicitly rather than the CUSTOM ping logic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5010) Errors triggered when a JP is preempted can falsely produce an Error sttus
[ https://issues.apache.org/jira/browse/UIMA-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5010. -- Resolution: Abandoned DUCC has been retired. > Errors triggered when a JP is preempted can falsely produce an Error sttus > -- > > Key: UIMA-5010 > URL: https://issues.apache.org/jira/browse/UIMA-5010 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > When a JP is preempted just as it starts running, the shutdown may trigger a > UIMA-AS error (Uima EE Client Not In Running State) ... ducc-mon should > report it as preempted (Forced?) ... not as Error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4044) DUCC Job Driver (JD) having OOM should cause job to terminate immediately
[ https://issues.apache.org/jira/browse/UIMA-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4044. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) having OOM should cause job to terminate immediately > - > > Key: UIMA-4044 > URL: https://issues.apache.org/jira/browse/UIMA-4044 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > 06 Oct 2014 17:58:28,157 16969 ERROR user.err workItemError 2007263482 > seqNo:7307 wiId:1010 PID:4473:52 > 06 Oct 2014 17:58:29,444 16969 ERROR user.err workItemError 2007263482 > java.lang.OutOfMemoryError: Java heap space > at sun.net.www.ParseUtil.encodePath(ParseUtil.java:117) > at sun.misc.URLClassPath$FileLoader.getResource(URLClassPath.java:1287) > at sun.misc.URLClassPath$FileLoader.findResource(URLClassPath.java:1276) > at sun.misc.URLClassPath.findResource(URLClassPath.java:298) > at java.net.URLClassLoader$1.run(URLClassLoader.java:901) > at java.net.URLClassLoader$1.run(URLClassLoader.java:899) > at > java.security.AccessController.doPrivileged(AccessController.java:252) > at java.net.URLClassLoader.findResource(URLClassLoader.java:898) > at java.lang.ClassLoader.getResource(ClassLoader.java:485) > at java.net.URLClassLoader.getResourceAsStream(URLClassLoader.java:356) > at org.apache.xerces.parsers.SecuritySupport$6.run(Unknown Source) > at > java.security.AccessController.doPrivileged(AccessController.java:229) > at > org.apache.xerces.parsers.SecuritySupport.getResourceAsStream(Unknown Source) > at > org.apache.xerces.parsers.ObjectFactory.findJarServiceProvider(Unknown Source) > at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) > at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) > at org.apache.xerces.parsers.DOMParser.(Unknown Source) > at org.apache.xerces.parsers.DOMParser.(Unknown Source) > at org.apache.xerces.jaxp.DocumentBuilderImpl.(Unknown Source) > at > org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown > Source) > at > com.thoughtworks.xstream.io.xml.DomDriver.createReader(DomDriver.java:75) > at > com.thoughtworks.xstream.io.xml.DomDriver.createReader(DomDriver.java:66) > at com.thoughtworks.xstream.XStream.fromXML(XStream.java:853) > at com.thoughtworks.xstream.XStream.fromXML(XStream.java:845) > at > org.apache.uima.aae.UimaSerializer.deserializePerformanceMetrics(UimaSerializer.java:299) > at > org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.completeProcessingReply(BaseUIMAAsynchronousEngineCommon_impl.java:1705) > at > org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.deserializeAndCompleteProcessingReply(BaseUIMAAsynchronousEngineCommon_impl.java:2274) > at > org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.sendAndReceiveCAS(BaseUIMAAsynchronousEngineCommon_impl.java:2240) > at > org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.sendAndReceiveCAS(BaseUIMAAsynchronousEngineCommon_impl.java:2049) > at org.apache.uima.ducc.jd.client.WorkItem.run(WorkItem.java:145) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:482) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:345) > at java.util.concurrent.FutureTask.run(FutureTask.java:177) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626) > at java.lang.Thread.run(Thread.java:780) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4584) ducc-mon should warn logged-out users why files can't be read
[ https://issues.apache.org/jira/browse/UIMA-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4584. -- Resolution: Abandoned DUCC has been retired. > ducc-mon should warn logged-out users why files can't be read > - > > Key: UIMA-4584 > URL: https://issues.apache.org/jira/browse/UIMA-4584 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Affects Versions: 2.0.0-Ducc >Reporter: Burn L. Lewis >Priority: Minor > > Currently just says "No data found" --- could add "Try logging in" if not > already logged in -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3073) DUCC webserver (WS) shows job not completed, yet jd.out.log show all work items ended?
[ https://issues.apache.org/jira/browse/UIMA-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3073. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) shows job not completed, yet jd.out.log show all work > items ended? > -- > > Key: UIMA-3073 > URL: https://issues.apache.org/jira/browse/UIMA-3073 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > It seems that all work items for job 60037 completed, by examination of > jd.out.log. Yet WS shows otherwise. > Perhaps more logging is needed in OR to determine if correct JD publications > are arriving. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4766) DUCC Job Driver (JD) and Job Process (JP) support for keyless investment reset function
[ https://issues.apache.org/jira/browse/UIMA-4766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4766. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) and Job Process (JP) support for keyless investment > reset function > --- > > Key: UIMA-4766 > URL: https://issues.apache.org/jira/browse/UIMA-4766 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Jaroslaw Cwiklik >Priority: Major > Fix For: future-DUCC > > > Deprecate keyed investment reset, which uses user supplied work item name as > key. Replace with keyless investment reset function, based on JP thread > and/or JD assigned sequence number. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3118) DUCC job driver (JD) should detect "missing" exception and fail work items on any JP that has croaked
[ https://issues.apache.org/jira/browse/UIMA-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3118. -- Resolution: Abandoned DUCC has been retired. > DUCC job driver (JD) should detect "missing" exception and fail work items on > any JP that has croaked > - > > Key: UIMA-3118 > URL: https://issues.apache.org/jira/browse/UIMA-3118 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Job 63470. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5491) A WI in a DUCC job fails with a NPE but JPs are restarted forever
[ https://issues.apache.org/jira/browse/UIMA-5491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5491. -- Resolution: Abandoned DUCC has been retired. > A WI in a DUCC job fails with a NPE but JPs are restarted forever > - > > Key: UIMA-5491 > URL: https://issues.apache.org/jira/browse/UIMA-5491 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > The JD throws java.io.NotSerializableException when the error is returned. > See job 361532 on the floor, 427 on terstducc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4959) JobDriver is sometimes a reserved class, sometimes set in ducc.properties
[ https://issues.apache.org/jira/browse/UIMA-4959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4959. -- Resolution: Abandoned DUCC has been retired. > JobDriver is sometimes a reserved class, sometimes set in ducc.properties > - > > Key: UIMA-4959 > URL: https://issues.apache.org/jira/browse/UIMA-4959 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > DuccSchedulingClasses treats JobDriver as a reserved class name, but the OR > uses the value in ducc.jd.host.name (which is not documented) ... also the > docs don't indicate that JobDriver is a reserved class-name. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4939) First creation of a DB in ducc_post_install can fail if Cassandra is already running
[ https://issues.apache.org/jira/browse/UIMA-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4939. -- Resolution: Abandoned DUCC has been retired. > First creation of a DB in ducc_post_install can fail if Cassandra is already > running > > > Key: UIMA-4939 > URL: https://issues.apache.org/jira/browse/UIMA-4939 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Major > Fix For: future-DUCC > > > The console spits out many messages of the form: > connect Authorization fails with both the default userid/password and the new > userid/password. > connect Retrying, as first-time database may take a few moments to > initialize. > connect Initial DB connection failed with AuthorizationException. Retrying > database connection with your supplied userid and password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-2764) DUCC Services need monitoring support, similar to Jobs + Managed Reservations
[ https://issues.apache.org/jira/browse/UIMA-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-2764. -- Resolution: Abandoned DUCC has been retired. > DUCC Services need monitoring support, similar to Jobs + Managed Reservations > - > > Key: UIMA-2764 > URL: https://issues.apache.org/jira/browse/UIMA-2764 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4688) DUCC should self-detect and provide an alert when unable to write its log files
[ https://issues.apache.org/jira/browse/UIMA-4688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4688. -- Resolution: Abandoned DUCC has been retired. > DUCC should self-detect and provide an alert when unable to write its log > files > --- > > Key: UIMA-4688 > URL: https://issues.apache.org/jira/browse/UIMA-4688 > Project: UIMA > Issue Type: New Feature > Components: DUCC >Reporter: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > In the case where DUCC's log files are written to a filesystem with a quota, > when the quota is exceeded DUCC will be prevented from writing its logs. > Usually the inability to write to the file system would result in an > Exception with reason "quota exceeded". However, log4j v1 suppresses > exceptions and continues as if all is well. > Some possible alternatives: > 1. use log4j v2 > 2. use native Java logging > 3. use an alternative filesystem not writeable detection mechanism -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3488) Add support for injecting a new process into an existing container
[ https://issues.apache.org/jira/browse/UIMA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3488. -- Resolution: Abandoned DUCC has been retired. > Add support for injecting a new process into an existing container > -- > > Key: UIMA-3488 > URL: https://issues.apache.org/jira/browse/UIMA-3488 > Project: UIMA > Issue Type: New Feature > Components: DUCC >Reporter: Eddie Epstein >Assignee: Jaroslaw Cwiklik >Priority: Major > Fix For: future-DUCC > > > ducc_submit should allow users to inject a new process into an existing > container that they own. Given that no new allocation need be done, this > operation should be fast, typically a few seconds at most. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6100) viaducc does not handle attach_console correctly
[ https://issues.apache.org/jira/browse/UIMA-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6100. -- Resolution: Abandoned DUCC has been retired. > viaducc does not handle attach_console correctly > > > Key: UIMA-6100 > URL: https://issues.apache.org/jira/browse/UIMA-6100 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Eddie Epstein >Assignee: Eddie Epstein >Priority: Major > Fix For: 3.0.1-DUCC > > > by default viaducc enable both attach_console and cancel_on_interrupt. An > option was added to suppress cancel_on_interrupt with the intent to let the > remote process continue running after the local submit process was > terminated. This was misguided because in many cases the remote process will > terminate when it's stdout/stderr pipes were broken. > The new change makes attach_console an option, which in addition sets > cancel_on_interrupt. The result is that by default viaducc will only monitor > the DUCC state of the remote process and the remote process will not be > terminated if the local submitter is stopped. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5134) DUCC should verify that the version of ducc_ling is compatible
[ https://issues.apache.org/jira/browse/UIMA-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5134. -- Resolution: Abandoned DUCC has been retired. > DUCC should verify that the version of ducc_ling is compatible > -- > > Key: UIMA-5134 > URL: https://issues.apache.org/jira/browse/UIMA-5134 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > There was a change in 2.1.0 that separated the stdout & stderr streams for > APs ... this change requires a 2.1.0 ducc_ling -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5214) Add option to restrict vertical scaling of DUCC service instances
[ https://issues.apache.org/jira/browse/UIMA-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5214. -- Resolution: Abandoned DUCC has been retired. > Add option to restrict vertical scaling of DUCC service instances > - > > Key: UIMA-5214 > URL: https://issues.apache.org/jira/browse/UIMA-5214 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Could also add an option to request horizontal or vertical scaling -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5190) DUCC's RM logs too much
[ https://issues.apache.org/jira/browse/UIMA-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5190. -- Resolution: Abandoned DUCC has been retired. > DUCC's RM logs too much > --- > > Key: UIMA-5190 > URL: https://issues.apache.org/jira/browse/UIMA-5190 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Reduce level to "info" and change some messages to debug. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5549) DUCC may fail to stop a service if there is an instance id is invalid
[ https://issues.apache.org/jira/browse/UIMA-5549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5549. -- Resolution: Abandoned DUCC has been retired. > DUCC may fail to stop a service if there is an instance id is invalid > - > > Key: UIMA-5549 > URL: https://issues.apache.org/jira/browse/UIMA-5549 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > The DB entry for service 9776 has implementor 365461.0 which was killed > during a shutdown but not recorded by the SM. So now when it tries to cancel > it the request is ignored (service not found in even log) but perhaps because > the OR doesn't publish that this so-called "job" has terminated it is never > removed from the list of implementors. Perhaps the SM should validate the OR > publications against its lists of implementors. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3699) ducc.py script does not work for broker with localhost
[
https://issues.apache.org/jira/browse/UIMA-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-3699.
--
Resolution: Abandoned
DUCC has been retired.
> ducc.py script does not work for broker with localhost
> --
>
> Key: UIMA-3699
> URL: https://issues.apache.org/jira/browse/UIMA-3699
> Project: UIMA
> Issue Type: Bug
> Components: DUCC
>Affects Versions: future-DUCC
> Environment: uima-ducc-vm, see Jira Infra 7194
>Reporter: Lou DeGenaro
>Assignee: Jaroslaw Cwiklik
>Priority: Major
>
> We had to hack ducc.py to handle blocked ports. In particular:
> os.environ['ACTIVEMQ_OPTS'] = '-Djava.rmi.server.hostname=localhost
> -DDUCC_AMQ_PORT=' + broker_port + \
> and
> jvm_opts.append('-Djava.rmi.server.hostname=localhost')
> From Infra 7194:
> Also, the AMQ broker's RMI needed to be configured (via -D) to use localhost
> instead of defaulting to the host's IP address.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-6032) DUCC shutdown has become slow
[ https://issues.apache.org/jira/browse/UIMA-6032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6032. -- Resolution: Abandoned DUCC has been retired. > DUCC shutdown has become slow > - > > Key: UIMA-6032 > URL: https://issues.apache.org/jira/browse/UIMA-6032 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 3.0.0-Ducc >Reporter: Eddie Epstein >Priority: Minor > Fix For: future-DUCC > > > DUCC 3.0.0 shutdown is considerably slower and more verbose than previous > versions -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3329) DUCC webserver (WS) graphs
[ https://issues.apache.org/jira/browse/UIMA-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3329. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) graphs > -- > > Key: UIMA-3329 > URL: https://issues.apache.org/jira/browse/UIMA-3329 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3064) Updates to services in ducc-mon should apply immediately
[ https://issues.apache.org/jira/browse/UIMA-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3064. -- Resolution: Abandoned DUCC has been retired. > Updates to services in ducc-mon should apply immediately > > > Key: UIMA-3064 > URL: https://issues.apache.org/jira/browse/UIMA-3064 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Currently a service owner can change the autostart & instances fields in the > registry, but they are not "activated" until the service is restarted. Just > like the start & stop buttons these changes should be applied when made. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4337) Isolate DUCC Agent so that it is not dependent on common and transport
[ https://issues.apache.org/jira/browse/UIMA-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4337. -- Resolution: Abandoned DUCC has been retired. > Isolate DUCC Agent so that it is not dependent on common and transport > -- > > Key: UIMA-4337 > URL: https://issues.apache.org/jira/browse/UIMA-4337 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Jaroslaw Cwiklik >Assignee: Jaroslaw Cwiklik >Priority: Major > Fix For: future-DUCC > > > Changes to common and transport require Agent restart. Since the restart > means killing all running jobs (JDs, JPs and Services) such action can be > expensive. > The proposal is to find a way to remove Agent dependency on common and > transport jars. Agent code should be isolated and self contained. This > requires major refactoring with impact on other Ducc daemons. > Currently an Agent publishes its inventory of processes using common classes > included in transport jar. It also publishes metrics using classes from > common jar. Those publications are consumed by RM, OR, and WS. The Agent uses > common code to bootstrap and configure itself just like all of the Ducc > daemons. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4570) If a log directory exists DUCC renames it and sweeps away the job spec
[ https://issues.apache.org/jira/browse/UIMA-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4570. -- Resolution: Abandoned DUCC has been retired. > If a log directory exists DUCC renames it and sweeps away the job spec > -- > > Key: UIMA-4570 > URL: https://issues.apache.org/jira/browse/UIMA-4570 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > The result is that ducc-mon cannot find the job specification. > Since this renaming of the log directory is only useful in the unusual case > of reinstalling DUCC without preserving the orchestrator sequence number, we > should remove the logsweeper ... or somehow make it run before any other > component opens the log directory. Without it, if job numbers are reused, > the log directory would have stale out-of-date log files ... easily avoided > if the directory is removed before restarting DUCC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3083) DUCC webserver (WS) consumes excessive memory and CPU under java 1.7
[ https://issues.apache.org/jira/browse/UIMA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3083. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) consumes excessive memory and CPU under java 1.7 > > > Key: UIMA-3083 > URL: https://issues.apache.org/jira/browse/UIMA-3083 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > Bypass is to specify useLegacyMergeSort in ducc.properties, for example: > ducc.ws.jvm.args = -Xmx12G -XX:-OmitStackTraceInFastThrow > -Djava.util.Arrays.useLegacyMergeSort=true -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3522) DUCC orchestrtor (OR) StateManager should not prune too soon
[ https://issues.apache.org/jira/browse/UIMA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3522. -- Resolution: Abandoned DUCC has been retired. > DUCC orchestrtor (OR) StateManager should not prune too soon > > > Key: UIMA-3522 > URL: https://issues.apache.org/jira/browse/UIMA-3522 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > StateManager prunes after 1 minute. To be "friendly" to subscribers, it > should not prune a map entry until it has been published at least once as > "Completed". > This is low priority, since map absence should be seen as Completed by > subscribers anyway. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-6198) ducc_watcher should employ SSL certificate validation
[ https://issues.apache.org/jira/browse/UIMA-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6198. -- Resolution: Abandoned DUCC has been retired. > ducc_watcher should employ SSL certificate validation > - > > Key: UIMA-6198 > URL: https://issues.apache.org/jira/browse/UIMA-6198 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > See Sumary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3448) DUCC orchestrator (OR) and job driver (JD) should not retry forever work items that appear on failing JPs
[ https://issues.apache.org/jira/browse/UIMA-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3448. -- Resolution: Abandoned DUCC has been retired. > DUCC orchestrator (OR) and job driver (JD) should not retry forever work > items that appear on failing JPs > - > > Key: UIMA-3448 > URL: https://issues.apache.org/jira/browse/UIMA-3448 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > One or more work items may cause a Job Process (JP) to crash. The work items > should be tracked and given-up on after some number of JP crashes. And/or > there should be some limit to the number of JP crashes for the Job before it > is auto-terminated for cause. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4790) DUCC Job Driver (JD) and Job Process (JP) support for encrypted communication
[ https://issues.apache.org/jira/browse/UIMA-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4790. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) and Job Process (JP) support for encrypted communication > - > > Key: UIMA-4790 > URL: https://issues.apache.org/jira/browse/UIMA-4790 > Project: UIMA > Issue Type: New Feature > Components: DUCC >Reporter: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > DUCC's work item communications between Job Driver (JD) and Job Process (JP) > should be configurable to employ encryption, similar that for for Web Server > (WS) login requests over https. > Justification: private information within the user supplied work item (e.g. > personal health, financial...) may be transmitted for processing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3942) Agents hang on shutdown if broker shutsdown too quickly
[ https://issues.apache.org/jira/browse/UIMA-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3942. -- Resolution: Abandoned DUCC has been retired. > Agents hang on shutdown if broker shutsdown too quickly > --- > > Key: UIMA-3942 > URL: https://issues.apache.org/jira/browse/UIMA-3942 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 1.0.0-Ducc >Reporter: Burn L. Lewis >Assignee: Jaroslaw Cwiklik >Priority: Minor > Fix For: future-DUCC > > > As a first step increase the stop_ducc wait time from 30 to 60 secs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3847) DUCC Web Server (WS) needs to simplify Scheduler & Agent { States + Reasons + Exit Codes } on Processes tab of Job Details page
[
https://issues.apache.org/jira/browse/UIMA-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-3847.
--
Resolution: Abandoned
DUCC has been retired.
> DUCC Web Server (WS) needs to simplify Scheduler & Agent { States + Reasons +
> Exit Codes } on Processes tab of Job Details page
> ---
>
> Key: UIMA-3847
> URL: https://issues.apache.org/jira/browse/UIMA-3847
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Minor
> Fix For: future-DUCC
>
>
> One unified state perhaps? Or leave as is but flag unexpected results in
> red? And/or have admin and user views?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-4434) DUCC Orchestrator (OR) job:node blacklisting
[ https://issues.apache.org/jira/browse/UIMA-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4434. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) job:node blacklisting > > > Key: UIMA-4434 > URL: https://issues.apache.org/jira/browse/UIMA-4434 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > A submitted Job may have shares allocated on some nodes where the JP works > and some nodes where the JP fails. > With respect to initialization, the OR should have a limit to the number of > initialization failures on a node before that node is banished for the Job. > The OR should communicate the blacklisted nodes for each Job to the RM who > should then not allocate and shares on said nodes for said corresponding Jobs. > An example failure situation is as follows: > 1. Node X does not have Filesystem F mounted > 2. Job 1 is submitted and is allocated to Node X > 3. Job 1's JP on Node X fails initialization (missing files!) > 4. RM allocates next JP for Job 1 to same Node X, ad infinitum until max init > failures is reached > 5. Job 1 is prevented from expanding because of a single "bad" Node > If Node X had been blacklisted, then the RM would have allocated Node Y to > Job 1 and expansion could have occurred. > Other types of JP failure scenarios: process croak and work item > failure/timeout will not be considered for blacklisting, presently. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3551) DUCC orchestrtor (OR) should take over responsibility for auto-cancel monitoring and enforcement
[ https://issues.apache.org/jira/browse/UIMA-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3551. -- Resolution: Abandoned DUCC has been retired. > DUCC orchestrtor (OR) should take over responsibility for auto-cancel > monitoring and enforcement > > > Key: UIMA-3551 > URL: https://issues.apache.org/jira/browse/UIMA-3551 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > This functionality is presently provided by the WS, due in part to early > development concerns relative to OR stability and performance which are no > longer. > This will free the WS from any requisite duties for running DUCC. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-2902) DUCC webserver (WS) should display enough of primitive name (Performance Name) to make it unique
[ https://issues.apache.org/jira/browse/UIMA-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-2902. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) should display enough of primitive name (Performance > Name) to make it unique > > > Key: UIMA-2902 > URL: https://issues.apache.org/jira/browse/UIMA-2902 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Sometime duplicates appear under Performance Name due to "mindless" > truncation of leading path. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4197) Using non-blocking "Future" instead of blocking "Future.get" to improve performance?
[
https://issues.apache.org/jira/browse/UIMA-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-4197.
--
Resolution: Abandoned
DUCC has been retired.
> Using non-blocking "Future" instead of blocking "Future.get" to improve
> performance?
>
>
> Key: UIMA-4197
> URL: https://issues.apache.org/jira/browse/UIMA-4197
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
>Reporter: Yu Lin
>Priority: Minor
> Fix For: future-DUCC
>
>
> Hi, I'm doing research on asynchronous programming. I found at some places,
> the code in uima-ducc ("trunk" branch) invokes "Future.get()", while it is a
> blocking call.
> For example, in "startAgents" method of "DuccAdmin" class (line 296), you
> invoke "result.get()", where "result" is a Future, so the code blocks.
> Why not use Guava ListenableFuture or Java8 CompletableFuture and avoid
> "Future.get()"? These two new constructs provide callbacks to listen to the
> Future's result:
> http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/util/concurrent/ListenableFuture.html
> https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html
> For example, in "DuccAdmin" class, you may put the code after "result.get()"
> (such as lines 301-307) into "CompletableFuture.thenRunAsync" method.
> Then make "startAgents" method return this CompletableFuture, and in the
> callers (such as "DuccAdmin.process()" or "DuccAdmin.main" method) you can
> put more continuations into "CompletableFuture.thenRunAsync". And you can
> also invoke "Future.get" somewhere in the callers (for example in
> "DuccAdmin.process()" method), instead of immediately.
> Do you think such kind of change is correct and can improve the code?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-3864) DUCC Web Server (WS) hide/show on services page may result in misleading display...
[ https://issues.apache.org/jira/browse/UIMA-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3864. -- Resolution: Abandoned DUCC has been retired. > DUCC Web Server (WS) hide/show on services page may result in misleading > display... > --- > > Key: UIMA-3864 > URL: https://issues.apache.org/jira/browse/UIMA-3864 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > The hide/show buttons on the Serivce Details page expand and contract all at > once. That is, the hide/show button for svc.classpath and the one for > svc.service_ping_classpath each cause both to hide or show in unison. > The user must then scroll to the right location on the page. > In one case, the user clicks on show for svc.service_ping_classpath. Both > and svc.service_ping_classpath are expanded, but the updated display starts > at the top where svc.classpath is displayed. The user expects to see > svc.service_ping_classpath and does not realize that scrolling down is > necessary, and is fooled into thinking the data in view is the data desired. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4940) Resurrect ducc_perf_stats
[ https://issues.apache.org/jira/browse/UIMA-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4940. -- Resolution: Abandoned DUCC has been retired. > Resurrect ducc_perf_stats > - > > Key: UIMA-4940 > URL: https://issues.apache.org/jira/browse/UIMA-4940 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > See UIMA-4509. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4489) CLI commands that don't use the log directory will fail if it cannot be created
[ https://issues.apache.org/jira/browse/UIMA-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4489. -- Resolution: Abandoned DUCC has been retired. > CLI commands that don't use the log directory will fail if it cannot be > created > --- > > Key: UIMA-4489 > URL: https://issues.apache.org/jira/browse/UIMA-4489 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > All CLI commands try to create the log directory and check that it exists, > even if they don't use it. Produces a surprising error if the default > ~/ducc/logs is a symbolic link to a deleted dir. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3065) DUCC webserver (WS) shows blank for new Service
[ https://issues.apache.org/jira/browse/UIMA-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3065. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) shows blank for new Service > --- > > Key: UIMA-3065 > URL: https://issues.apache.org/jira/browse/UIMA-3065 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > 10 Jul 2013 09:58:07,612 INFO WS.DuccHandler - handle N/A > java.lang.NullPointerException > At: > > org.apache.uima.ducc.ws.server.DuccHandler.handleDuccServletServiceSummaryData(DuccHandler.java:1907) > > org.apache.uima.ducc.ws.server.DuccHandler.handleDuccRequest(DuccHandler.java:3470) > > org.apache.uima.ducc.ws.server.DuccHandler.handle(DuccHandler.java:3620) > > org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:47) > > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110) > org.eclipse.jetty.server.Server.handle(Server.java:346) > ... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3697) DUCC common services
[ https://issues.apache.org/jira/browse/UIMA-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3697. -- Resolution: Abandoned DUCC has been retired. > DUCC common services > > > Key: UIMA-3697 > URL: https://issues.apache.org/jira/browse/UIMA-3697 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 1.0.0-Ducc >Reporter: Lou DeGenaro >Assignee: Jaroslaw Cwiklik >Priority: Minor > Fix For: future-DUCC > > > If information that is needed for route building is missing from > ducc.properties, no clue is given in the daemon logs. > Below is shown a stack trace obtained by adding try/catch code to WS > component only. > In this case, the problem was that the following was missing from > ducc.properties: > ducc.db.state.update.endpoint=ducc.db.state > The same problem could occur for other daemons relative their routes. > = > 26 Mar 2014 18:22:04,827 1 INFO WS.WebServerConfiguration - webServer > N/A routes added > 26 Mar 2014 18:22:04,907 1 INFO WS.WebServerComponent - start N/A > .Starting Admin Channel on endpoint:activemq:topic:ducc.admin.channel > 26 Mar 2014 18:22:05,005 1 INFO WS.WebServerComponent - startAdminChannel > N/A Admin Channel Activated on endpoint:activemq:topic:ducc.admin.channel > 26 Mar 2014 18:22:05,005 1 INFO WS.WebServerComponent - start N/A > .Starting Camel Context > 26 Mar 2014 18:22:07,722 1 ERROR WS.WebServerComponent - null N/A > org.apache.camel.FailedToCreateRouteException: Failed to create route route6: > Route[[From[no uri or ref supplied!]] -> [process[org.apache... because of > Either 'uri' or 'ref' must be specified on: > org.apache.camel.impl.DefaultRouteContext@52ea8917 > at > org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:176) > at > org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:722) > at > org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:1779) > at > org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1572) > at > org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1437) > at > org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:60) > at > org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:1405) > at > org.apache.uima.ducc.common.component.AbstractDuccComponent.start(AbstractDuccComponent.java:283) > at > org.apache.uima.ducc.ws.WebServerComponent.start(WebServerComponent.java:74) > at > org.apache.uima.ducc.common.component.AbstractDuccComponent.start(AbstractDuccComponent.java:263) > at > org.apache.uima.ducc.common.main.DuccService.boot(DuccService.java:141) > at > org.apache.uima.ducc.common.main.DuccService.main(DuccService.java:212) > Caused by: java.lang.IllegalArgumentException: Either 'uri' or 'ref' must be > specified on: org.apache.camel.impl.DefaultRouteContext@52ea8917 > at > org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:129) > at > org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72) > at > org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:89) > at > org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:851) > at > org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:171) > ... 11 more -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5473) Remove JCas classes from the user jar for UIMA V2/V3 compatibility
[ https://issues.apache.org/jira/browse/UIMA-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5473. -- Resolution: Abandoned DUCC has been retired. > Remove JCas classes from the user jar for UIMA V2/V3 compatibility > -- > > Key: UIMA-5473 > URL: https://issues.apache.org/jira/browse/UIMA-5473 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Major > Fix For: future-DUCC > > > UIMA V2 & V3 JCas classes are incompatible and since the uima-ducc-user jar > is added to the user's class path we must either support 2 versions of that > jar or remove any use of JCas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5283) SM sometimes keeps starting failing instances forever (see UIMA-5244)
[ https://issues.apache.org/jira/browse/UIMA-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5283. -- Resolution: Abandoned DUCC has been retired. > SM sometimes keeps starting failing instances forever (see UIMA-5244) > - > > Key: UIMA-5283 > URL: https://issues.apache.org/jira/browse/UIMA-5283 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Another attempt at fixing the problem reported in 5244. Must also fix the > false reporting of failing instances when DUCC is restarted and the OR > initially claims that the instances running at shutdown are still running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3532) DUCC doesn't fully follow UIMA resource-loading conventions
[ https://issues.apache.org/jira/browse/UIMA-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3532. -- Resolution: Abandoned DUCC has been retired. > DUCC doesn't fully follow UIMA resource-loading conventions > --- > > Key: UIMA-3532 > URL: https://issues.apache.org/jira/browse/UIMA-3532 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > DUCC doesn't use the UIMA resolveRelativePath method correctly when loading > descriptors. It should be set up with the user's classpath and JVM args. > Currently DUCC services must be given a file DD as classpath/data-path > loading doesn't work. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3126) DUCC webserver (WS) improvements for handing "down" node with respect to work items thereto dispatched
[ https://issues.apache.org/jira/browse/UIMA-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3126. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) improvements for handing "down" node with respect to work > items thereto dispatched > -- > > Key: UIMA-3126 > URL: https://issues.apache.org/jira/browse/UIMA-3126 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > 1. On Work Items tab, show down nodes for active work items in RED > 2. Indicate such "troubled" work items on Jobs page > 3. Offer user one button "clean-up" for doomed work items -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5099) DUCC Service Manager (SM) pinger message not clear when incorrect JMX has been port specified
[ https://issues.apache.org/jira/browse/UIMA-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5099. -- Resolution: Abandoned DUCC has been retired. > DUCC Service Manager (SM) pinger message not clear when incorrect JMX has > been port specified > - > > Key: UIMA-5099 > URL: https://issues.apache.org/jira/browse/UIMA-5099 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Jaroslaw Cwiklik >Priority: Minor > Fix For: future-DUCC > > > Service was configured with: > service_ping_arguments broker-jmx-port=1100 > After starting service, message in registry was: > = > meta.service-statistics JMX Failure[Failed to retrieve RMIServer stub: > javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: broker1; nested > exception is: java.net.ConnectException: Connection refused]]] > MetaNode[192.168.2.120] MetaPid[13647:76 > = > Problem was that port should have been 1099. > More clarity is desirable, such as: unable to connect to broker1 on port 1100. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3960) DUCC Orchestrator (OR) records wrong exit code == 0 to a Managed Reservation canceled by user
[ https://issues.apache.org/jira/browse/UIMA-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3960. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) records wrong exit code == 0 to a Managed Reservation > canceled by user > - > > Key: UIMA-3960 > URL: https://issues.apache.org/jira/browse/UIMA-3960 > Project: UIMA > Issue Type: Bug > Components: DUCC > Environment: Reported by Burn. >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Correct exit code should be 15. Probably a race condition in the OR. > Note: see logs in /degenaro/tmp/186050 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4629) DUCC Job Driver (JD) should provide individual work item performance breakdowns submit --flag
[ https://issues.apache.org/jira/browse/UIMA-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4629. -- Resolution: Abandoned DUCC has been retired. > DUCC Job Driver (JD) should provide individual work item performance > breakdowns submit --flag > - > > Key: UIMA-4629 > URL: https://issues.apache.org/jira/browse/UIMA-4629 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > See UIMA-4586. > Replace environment variable with ducc_submit flag and add to doc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5268) When DUCC is restarted the OR publishes defunct work that are treated as failures by the SM
[ https://issues.apache.org/jira/browse/UIMA-5268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5268. -- Resolution: Abandoned DUCC has been retired. > When DUCC is restarted the OR publishes defunct work that are treated as > failures by the SM > --- > > Key: UIMA-5268 > URL: https://issues.apache.org/jira/browse/UIMA-5268 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Major > Fix For: future-DUCC > > > The work that was active at shutdown is presented as Running after the > restart but is soon changed to Completed. This sometimes makes the SM > disable a service. Perhaps the completion-type or rationale could be > something like "Framework Error" or "node restart" so these are not treated > as user errors. > SM.ServiceHandler - 6107 handleModifiedServices !! Processing modified > instance 297751 state Running > SM.ServiceHandler - 6107 handleModifiedServices !! Processing modified > instance 297751 state Completed completion-type Warning rationale process > failure(s) occurred > After restarting all instances the registry had the following: > submit-errorService stopped by exessive failures. Initialization > failures[0], Runtime failures[0] > but soon after this was remove and ducc-mon said Available. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5582) Launch external pingers with the user-supplied --jvm instead of DUCC's
[ https://issues.apache.org/jira/browse/UIMA-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5582. -- Resolution: Abandoned DUCC has been retired. > Launch external pingers with the user-supplied --jvm instead of DUCC's > -- > > Key: UIMA-5582 > URL: https://issues.apache.org/jira/browse/UIMA-5582 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Burn L. Lewis >Assignee: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > Currently if JAVA_HOME is not in the environment DUCC uses the same JVM as > DUCC to launch external pingers. Instead use the jvm supplied by the user > which is likely to be the same as the service. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3498) DUCC webserver (WS) improved use of /bin/cat
[
https://issues.apache.org/jira/browse/UIMA-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Eckart de Castilho resolved UIMA-3498.
--
Resolution: Abandoned
DUCC has been retired.
> DUCC webserver (WS) improved use of /bin/cat
>
>
> Key: UIMA-3498
> URL: https://issues.apache.org/jira/browse/UIMA-3498
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Minor
> Fix For: future-DUCC
>
>
> In AlienFile.java, follow the recipe provided by Burn below:
> // Run process and log all output
> ProcessBuilder pb = new ProcessBuilder(args);
> pb.redirectErrorStream(true);
> Process p = pb.start();
> BufferedReader in = new BufferedReader(new
> InputStreamReader(p.getInputStream()));
> String line = in.readLine();
> while (line != null) {
> if (outStream == null) {
> logger.log(Level.INFO, "[" + id + "] " + line);
> } else {
> outStream.println(line);
> }
> line = in.readLine();
> }
> in.close();
> if (outStream != null) {
> outStream.close();
> }
> rc = p.waitFor();
> if (rc != 0 && outStream != null) {
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (UIMA-3009) DUCC webserver (WS) needs to employ executable jars
[ https://issues.apache.org/jira/browse/UIMA-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3009. -- Resolution: Abandoned DUCC has been retired. > DUCC webserver (WS) needs to employ executable jars > --- > > Key: UIMA-3009 > URL: https://issues.apache.org/jira/browse/UIMA-3009 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > slf4j messages are annoying! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5012) No error notification for services specifying an unwritable logfile directory
[ https://issues.apache.org/jira/browse/UIMA-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5012. -- Resolution: Abandoned DUCC has been retired. > No error notification for services specifying an unwritable logfile directory > - > > Key: UIMA-5012 > URL: https://issues.apache.org/jira/browse/UIMA-5012 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Eddie Epstein >Priority: Major > Fix For: future-DUCC > > > For other DUCC work submissions the cli checks for this problem and does a > fast fail. The same needs to be done for service instance submissions done by > the Service Manager, with the error persisted in the service meta information > and shown on the service page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5615) DUCC's WaitingForDriver should not include the JD initialization phase
[ https://issues.apache.org/jira/browse/UIMA-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5615. -- Resolution: Abandoned DUCC has been retired. > DUCC's WaitingForDriver should not include the JD initialization phase > -- > > Key: UIMA-5615 > URL: https://issues.apache.org/jira/browse/UIMA-5615 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > It would be better to add another state, Initializing Job Driver, to help > distinguish between waiting for the resource and waiting for the CR to > initialize -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4469) DUCC SM: Reference stop fails after some hot-restarts
[ https://issues.apache.org/jira/browse/UIMA-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4469. -- Resolution: Abandoned DUCC has been retired. > DUCC SM: Reference stop fails after some hot-restarts > - > > Key: UIMA-4469 > URL: https://issues.apache.org/jira/browse/UIMA-4469 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 1.0.0-Ducc, 1.1.0-Ducc, 2.0.0-Ducc >Reporter: Jim Challenger >Assignee: Jim Challenger >Priority: Minor > Fix For: future-DUCC > > > If SM is taken down for a while and jobs referencing existing services exit > so the services no longer are referenced, then SM is restarted, the fact that > a reference-started service is no longer referenced is not acted upon. > To fix, on hot restart, SM needs to insure all reference-started services are > still referenced and begin the lingering stop if not. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3981) DUCC Orchestrator (OR) makes wrong time stamp for Croaked JPs?
[ https://issues.apache.org/jira/browse/UIMA-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3981. -- Resolution: Abandoned DUCC has been retired. > DUCC Orchestrator (OR) makes wrong time stamp for Croaked JPs? > -- > > Key: UIMA-3981 > URL: https://issues.apache.org/jira/browse/UIMA-3981 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > It has been reported that when a Job Process (JP) Croaks and later the Job > goes to Completed state, the ending time stamp for the JP is changed from the > actual time it finished (as observed via Web Server) to a time close in > proximity to the Job Completion time. > The OR should not (if it does) modify the time of an already completed JP > during Job Completed clean-up time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-4756) check_ducc reports success for a remote worker that cannot be reached
[ https://issues.apache.org/jira/browse/UIMA-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-4756. -- Resolution: Abandoned DUCC has been retired. > check_ducc reports success for a remote worker that cannot be reached > - > > Key: UIMA-4756 > URL: https://issues.apache.org/jira/browse/UIMA-4756 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Eddie Epstein >Priority: Minor > Fix For: future-DUCC > > > check_ducc shows no errors for machines that are not reachable on the network. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-2641) DUCC orchestrator (OR) should mark unused, stubbornly alive Job Processes (JPs) as "Stopped" when all work items are accounted for...
[ https://issues.apache.org/jira/browse/UIMA-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-2641. -- Resolution: Abandoned DUCC has been retired. > DUCC orchestrator (OR) should mark unused, stubbornly alive Job Processes > (JPs) as "Stopped" when all work items are accounted for... > - > > Key: UIMA-2641 > URL: https://issues.apache.org/jira/browse/UIMA-2641 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > Recently, a job was submitted but got stuck in state "Completing". All work > items had completed. During the run a Job Process (JP) was launched and got > stuck in Initializing state because the machine on which it (once) existed > crashed and (therefore) the DUCC Agent responsible was unable to report or > take action. This stuck JP was keeping the job from advancing to the > "Completed" state. > The user issued the DUCC cancel command using flag --dpid to cancel the bogus > JP and the job completed normally. > This situation could be detected by the orchestrator (OR) and handled w/o > human (user) intervention. > Additionally, the WS could be helpful in a) identifying those cases that > cannot be automatically handled and b) offering guidance towards freeing up > work items held in limbo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3592) DUCC WebServer (WS) some pages missing data for logged-in user
[ https://issues.apache.org/jira/browse/UIMA-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3592. -- Resolution: Abandoned DUCC has been retired. > DUCC WebServer (WS) some pages missing data for logged-in user > --- > > Key: UIMA-3592 > URL: https://issues.apache.org/jira/browse/UIMA-3592 > Project: UIMA > Issue Type: Bug > Components: DUCC >Reporter: Lou DeGenaro >Priority: Minor > Fix For: future-DUCC > > > - downloaded RC10 binary tarball to standalone 8GB thinkpad running RHEL 6.4 > - followed directions from INSTALL file for single-user install and > verification > - followed directions for multi-user install with webserver login and > verified with 1.job submitted from non-ducc user. Found webserver problem > displaying "Files" in the job details page. More on this below (*). > - followed directions from duccbook.html, chapter 9 to install opennlp and > run text processing sample > - ran CAS input processing sample from chapter 10 > - setup java_viaducc as per chapter 3.13 and ran hello world type program. > Process ran fine, but webserver again could not display "Files" or > "Specification" from reservation details page. See (**). > (*) Directory permissions for non-ducc user are configured to not allow > read access by user "ducc". In this situation the webserver will not be > able to display job details from user log files, unless authenticated to > the webserver as the user with read permission. After logging into the > webserver, all job details were accessible except for "Files" tab. > (**) Similar problem as with Job details. Log file OK, but nothing shown in > "Files" or "Specification" tabs. > All these details are available to users as human readable files in their > filesystem. Another workaround available, if it is OK for cluster users to > see each others logfiles, is simply to give user "ducc" read access to the > user log directories and files there. Therefor I do not consider this a > blocker for first release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-5313) Can get concurrent modification when closing the threads attached to a DUCC AP
[ https://issues.apache.org/jira/browse/UIMA-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-5313. -- Resolution: Abandoned DUCC has been retired. > Can get concurrent modification when closing the threads attached to a DUCC AP > -- > > Key: UIMA-5313 > URL: https://issues.apache.org/jira/browse/UIMA-5313 > Project: UIMA > Issue Type: Bug >Reporter: Burn L. Lewis >Priority: Minor > Fix For: future-DUCC > > > id:32044 state:Completed > id:32044 rationale:code=0 > id:32044 rc:0 > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:934) > at java.util.HashMap$ValueIterator.next(HashMap.java:962) > at > org.apache.uima.ducc.cli.ConsoleListener.shutdown(ConsoleListener.java:89) > at org.apache.uima.ducc.cli.CliBase.monitorExits(CliBase.java:677) > at org.apache.uima.ducc.cli.MonitorListener.run(MonitorListener.java:92) > at java.lang.Thread.run(Thread.java:809) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (UIMA-3048) DUCC components, for example Job Driver (JD), should publish data (e.g. JSON) not objects across the network
[ https://issues.apache.org/jira/browse/UIMA-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-3048. -- Resolution: Abandoned DUCC has been retired. > DUCC components, for example Job Driver (JD), should publish data (e.g. JSON) > not objects across the network > > > Key: UIMA-3048 > URL: https://issues.apache.org/jira/browse/UIMA-3048 > Project: UIMA > Issue Type: Improvement > Components: DUCC >Reporter: Lou DeGenaro >Assignee: Lou DeGenaro >Priority: Major > Fix For: future-DUCC > > > By passing JSON data (for example) instead of Java objects between daemons, > the theory is that backward compatibility is more easily achieved as DUCC > development moves forward. -- This message was sent by Atlassian Jira (v8.20.10#820010)
