Re: [DISCUSS] New PMC chairperson

I'd like to add my sincere thanks to Marshall for all the support and advice that he gave as I learned about UIMA and open source development. He will be missed but UIMA is in good hands with Richard as PMC chair. Thanks to you both! Burn On Thu, Oct 29, 2020 at 2:55 PM Marshall Schor wrote: >

Re: [VOTE] Releasing UIMA-C++ version 3.0.0 rc1

[ ] -1 Not OK to release, because Mac OSX Catalina build fails. Set the correct JAVA_HOME & used gcc-5 & g++-5 & set CPPFLAGS to reference the sdk path for /usr/include but ICU puts that directive ahead of the local ones which means that the wrong util.h is loaded ... may need to hack ICU to not

Re: [VOTE] Moving UIMA-AS to Git Repo

[X] +1 OK to move UIMA-AS from SVN to (writable) GIT for source control Burn On Wed, Jan 15, 2020 at 5:33 PM Marshall Schor wrote: > [X] +1 OK to move UIMA-AS from SVN to (writable) GIT for source control > > -Marshall Schor > > On 1/15/2020 3:54 PM, Jaroslaw Cwiklik wrote: > > I would like to

Re: [VOTE] moving uima-uimacpp project to r/w git

+1 Burn Lewis On Tue, Oct 8, 2019 at 10:50 AM Marshall Schor wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > +1 Marshall Schor > > On 10/8/2019 10:49 AM, Marshall Schor wrote: > > I forgot that INFRA needs a [VOTE] on this. > >

[jira] [Created] (UIMA-6124) Simplify master/backup determination for reliable DUCC

Burn Lewis created UIMA-6124: Summary: Simplify master/backup determination for reliable DUCC Key: UIMA-6124 URL: https://issues.apache.org/jira/browse/UIMA-6124 Project: UIMA Issue Type

[jira] [Resolved] (UIMA-6120) ducc_update fails if not invoked from a shell

[ https://issues.apache.org/jira/browse/UIMA-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-6120. -- Resolution: Fixed Used os.getcwd() > ducc_update fails if not invoked from a sh

[jira] [Closed] (UIMA-6120) ducc_update fails if not invoked from a shell

[ https://issues.apache.org/jira/browse/UIMA-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-6120. > ducc_update fails if not invoked from a sh

[jira] [Created] (UIMA-6120) ducc_update fails if not invoked from a shell

Burn Lewis created UIMA-6120: Summary: ducc_update fails if not invoked from a shell Key: UIMA-6120 URL: https://issues.apache.org/jira/browse/UIMA-6120 Project: UIMA Issue Type: Bug

[jira] [Created] (UIMA-6116) Improve error msg when all job-driver slots are in use

Burn Lewis created UIMA-6116: Summary: Improve error msg when all job-driver slots are in use Key: UIMA-6116 URL: https://issues.apache.org/jira/browse/UIMA-6116 Project: UIMA Issue Type

[jira] [Created] (UIMA-6114) Add the experiments page code

Burn Lewis created UIMA-6114: Summary: Add the experiments page code Key: UIMA-6114 URL: https://issues.apache.org/jira/browse/UIMA-6114 Project: UIMA Issue Type: Improvement

[jira] [Closed] (UIMA-6099) DUCC should reject invalid scheduling class names

[ https://issues.apache.org/jira/browse/UIMA-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-6099. > DUCC should reject invalid scheduling class na

[jira] [Closed] (UIMA-6109) Some DUCC classes are ignored by the DuccLogger

[ https://issues.apache.org/jira/browse/UIMA-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-6109. > Some DUCC classes are ignored by the DuccLog

[jira] [Resolved] (UIMA-6109) Some DUCC classes are ignored by the DuccLogger

[ https://issues.apache.org/jira/browse/UIMA-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-6109. -- Resolution: Fixed Changed log4j.xml to use the same appender for all classes putting the logs

Re: [VOTE] uimaj 3.1.0 rc1

checked signatures: OK - but the filename is missing from uimaj-3.1.0-source-release.zip.sha512 installed binary & ran document analyzer: OK ran a simple annotator via DUCC: OK checked docs: OK build from sources: OK checked signatures & docs: OK extracted the build & ran document analyzer: OK

[jira] [Created] (UIMA-6111) Service instance failures caused by resource issues should not penalize the service

Burn Lewis created UIMA-6111: Summary: Service instance failures caused by resource issues should not penalize the service Key: UIMA-6111 URL: https://issues.apache.org/jira/browse/UIMA-6111 Project

[jira] [Created] (UIMA-6109) Some DUCC classes are ignored by the DuccLogger

Burn Lewis created UIMA-6109: Summary: Some DUCC classes are ignored by the DuccLogger Key: UIMA-6109 URL: https://issues.apache.org/jira/browse/UIMA-6109 Project: UIMA Issue Type: Improvement

Re: [VOTE] uimaj-2.10.4-rc1

checked signatures: OK - but the filename is missing from uimaj-2.10.4-source-release.zip.sha512 installed binary & ran document analyzer: OK checked docs: OK build from sources: OK checked signatures & docs: OK extracted the build & ran document analyzer: OK ran an NLP pipeline with many

Re: [VOTE] uimaj 3.0.3 rc2

checked signatures: OK - but the filename is missing from uimaj-3.0.3-source-release.zip.sha512 installed binary & ran document analyzer: OK checked docs: OK build from sources: OK checked signatures & docs: OK extracted the build & ran document analyzer: OK ran a simple annotator via DUCC: OK

[jira] [Resolved] (UIMA-6104) Agent should accept requests from a single head-node system

[ https://issues.apache.org/jira/browse/UIMA-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-6104. -- Resolution: Fixed Accept work from a "master" or "unspecified" head node &

[jira] [Created] (UIMA-6104) Agent should accept requests from a single head-node system

Burn Lewis created UIMA-6104: Summary: Agent should accept requests from a single head-node system Key: UIMA-6104 URL: https://issues.apache.org/jira/browse/UIMA-6104 Project: UIMA Issue Type

[jira] [Created] (UIMA-6103) start_ducc should always check ssh access

Burn Lewis created UIMA-6103: Summary: start_ducc should always check ssh access Key: UIMA-6103 URL: https://issues.apache.org/jira/browse/UIMA-6103 Project: UIMA Issue Type: Bug

[jira] [Resolved] (UIMA-6099) DUCC should reject invalid scheduling class names

[ https://issues.apache.org/jira/browse/UIMA-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-6099. -- Resolution: Fixed > DUCC should reject invalid scheduling class na

[jira] [Commented] (UIMA-6099) DUCC should reject invalid scheduling class names

[ https://issues.apache.org/jira/browse/UIMA-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896450#comment-16896450 ] Burn Lewis commented on UIMA-6099: -- Moved scheduling class checks from CLI to OR or SM assign

[jira] [Created] (UIMA-6099) DUCC should reject invalid scheduling class names

Burn Lewis created UIMA-6099: Summary: DUCC should reject invalid scheduling class names Key: UIMA-6099 URL: https://issues.apache.org/jira/browse/UIMA-6099 Project: UIMA Issue Type: Bug

[jira] [Resolved] (UIMA-6089) ducc_update refuses to run even though there are no ducc daemons running on the head node comprising the attempted update

[ https://issues.apache.org/jira/browse/UIMA-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-6089. -- Resolution: Fixed Removed check for obsolete pids file which may have been the problem. Also check

[jira] [Closed] (UIMA-5975) Missing method in pull service's ServiceConfiguration

[ https://issues.apache.org/jira/browse/UIMA-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5975. Resolution: Fixed > Missing method in pull service's ServiceConfigurat

[jira] [Created] (UIMA-5975) Missing method in pull service's ServiceConfiguration

Burn Lewis created UIMA-5975: Summary: Missing method in pull service's ServiceConfiguration Key: UIMA-5975 URL: https://issues.apache.org/jira/browse/UIMA-5975 Project: UIMA Issue Type: Bug

[jira] [Created] (UIMA-5941) Remove unused imports

Burn Lewis created UIMA-5941: Summary: Remove unused imports Key: UIMA-5941 URL: https://issues.apache.org/jira/browse/UIMA-5941 Project: UIMA Issue Type: Bug Components: DUCC

[jira] [Updated] (UIMA-5941) Remove unused imports

[ https://issues.apache.org/jira/browse/UIMA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5941: - Affects Version/s: 2.2.2-Ducc > Remove unused imports > - > >

[jira] [Updated] (UIMA-5941) Remove unused imports

[ https://issues.apache.org/jira/browse/UIMA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5941: - Fix Version/s: 2.2.3-Ducc > Remove unused imports > - > >

[jira] [Work started] (UIMA-5941) Remove unused imports

[ https://issues.apache.org/jira/browse/UIMA-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-5941 started by Burn Lewis. > Remove unused imports > - > > Ke

[jira] [Commented] (UIMA-5869) The JCas getView method throws CasRuntimeException not CasException

[ https://issues.apache.org/jira/browse/UIMA-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16623698#comment-16623698 ] Burn Lewis commented on UIMA-5869: -- Unchecked exceptions are for errors the code is unlikely to be able

[jira] [Created] (UIMA-5869) The JCas getView method throws CasRuntimeException not CasException

Burn Lewis created UIMA-5869: Summary: The JCas getView method throws CasRuntimeException not CasException Key: UIMA-5869 URL: https://issues.apache.org/jira/browse/UIMA-5869 Project: UIMA

[jira] [Created] (UIMA-5862) RM can fail with a comparator violating its general contract

Burn Lewis created UIMA-5862: Summary: 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

[jira] [Created] (UIMA-5822) DUCC pull service failures immediately after initialization may be treated as initialization failures

Burn Lewis created UIMA-5822: Summary: DUCC pull service failures immediately after initialization may be treated as initialization failures Key: UIMA-5822 URL: https://issues.apache.org/jira/browse/UIMA-5822

[jira] [Created] (UIMA-5821) Pull service errors are not returned correctly

Burn Lewis created UIMA-5821: Summary: Pull service errors are not returned correctly Key: UIMA-5821 URL: https://issues.apache.org/jira/browse/UIMA-5821 Project: UIMA Issue Type: Bug

[jira] [Created] (UIMA-5782) Improve ducc_update handling of elevated ducc_ling

Burn Lewis created UIMA-5782: Summary: Improve ducc_update handling of elevated ducc_ling Key: UIMA-5782 URL: https://issues.apache.org/jira/browse/UIMA-5782 Project: UIMA Issue Type: Bug

[jira] [Commented] (UIMA-5756) UIMA-DUCC: Create a new project for the pull service

[ https://issues.apache.org/jira/browse/UIMA-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487292#comment-16487292 ] Burn Lewis commented on UIMA-5756: -- Added copyrights to a few methods.  Added setters

[jira] [Commented] (UIMA-5756) UIMA-DUCC: Create a new project for the pull service

[ https://issues.apache.org/jira/browse/UIMA-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16487216#comment-16487216 ] Burn Lewis commented on UIMA-5756: -- Renamed some packages so all start with "org.apache.uima.du

[jira] [Created] (UIMA-5779) DUCC should tolerate DB errors

Burn Lewis created UIMA-5779: Summary: DUCC should tolerate DB errors Key: UIMA-5779 URL: https://issues.apache.org/jira/browse/UIMA-5779 Project: UIMA Issue Type: Bug Components: DUCC

Re: [VOTE] release uima addon ConceptMapper 2.10.2

- Checked signatures - Spot-checked license, notices, issues, docs - Tested by running an existing application & got same results - Built from source [X] +1 OK to release On Thu, Apr 19, 2018 at 1:48 PM, Marshall Schor wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash:

Re: [jira] [Commented] (UIMA-5763) UIMA: need a way to lock a CAS to prevent user from releasing it prematurely

Could this particular case be fixed by marking the CAS "unowned" when it is released? Or assigning it an ID when used and clearing it when released? The more general solution of preventing any invalid multi-threaded access to a CAS is something programmers are responsible for on every other

Re: [VOTE] UIMA-AS 2.10.3 RC1

- Downloaded binary & source and checked signatures - Built from source & checked signatures - On both builds ran a couple of UIMA-AS pipelines - On both builds verified that multiple JMS service descriptors can connect to the same service - Checked README, RELEASE_NOTES,LICENSE and NOTICE - Spot

Re: [VOTE] UIMA-DUCC 2.2.2 RC4

+ downloaded binary & source and checked signatures + installed binary on a multi-node cluster and ran a large experiment with jobs, services & APs + ran the mega-30-min tests on 53 simulated nodes but using UIMA-AS 2.9.0 to avoid bug in 2.10.2 + built from source and checked signatures ^ ran

[jira] [Created] (UIMA-5746) DUCC jobs that use a JMS service descriptor no longer work

Burn Lewis created UIMA-5746: Summary: DUCC jobs that use a JMS service descriptor no longer work Key: UIMA-5746 URL: https://issues.apache.org/jira/browse/UIMA-5746 Project: UIMA Issue Type

Re: [VOTE] UIMA-DUCC 2.2.2 RC3

+ downloaded & checked signatures + installed binary on a multi-node cluster and ran a large experiment with jobs, services & APs * tested the Raw Test Process sample application + built from source and checked signatures ^ ran 1.job etc. on that build + spot checked install, readme, release

Re: [VOTE] uimaj-3.0.0 rc4

Finally - checked signatures: OK - spot checked readme, release notes, license, etc.: OK - after converting many JCas classes recompiled a large set of projects using the maven artifacts: OK - ran a multi-annotator pipeline and compared with V2 results: OK - built from source & checked

[jira] [Resolved] (UIMA-5390) DUCC may restart failing custom services forever

[ https://issues.apache.org/jira/browse/UIMA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5390. -- Resolution: Fixed Problem was not the lack of an initialization phase ... runtime errors were

[jira] [Closed] (UIMA-5390) DUCC may restart failing custom services forever

[ https://issues.apache.org/jira/browse/UIMA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5390. Assignee: Burn Lewis > DUCC may restart failing custom services fore

[jira] [Updated] (UIMA-5390) DUCC may restart failing custom services forever

[ https://issues.apache.org/jira/browse/UIMA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5390: - Fix Version/s: (was: future-DUCC) 2.2.2-Ducc Runtime errors are wrongly reset when

Re: [VOTE] UIMA-DUCC 2.2.2 RC1

Ran 1.dd.job with UIMA 2.10.0 and got: java.lang.NoSuchMethodError: org/apache/uima/internal/util/XMLUtils.createDocumentBuilderFactory() Ljavax/xml/parsers/DocumentBuilderFactory; Can we avoid requiring UIMA 2.10.2 in user code? ~Burn On Wed, Feb 21, 2018 at 8:58 AM, Lou DeGenaro

Re: [jira] [Closed] (UIMA-5728) UIMA-DUCC: prepare for v.2.2.2 release

Ran 1.dd.job with UIMA 2.10.0 and got: java.lang.NoSuchMethodError: org/apache/uima/internal/util/XMLUtils.createDocumentBuilderFactory()Ljavax/xml/parsers/DocumentBuilderFactory; Can we avoid requiring UIMA 2.10.2 in user code? ~Burn On Mon, Feb 19, 2018 at 10:06 AM, Jerry Cwiklik (JIRA)

[jira] [Updated] (UIMA-5654) ducc_ling should verify that it's "ducc" id is correct

[ https://issues.apache.org/jira/browse/UIMA-5654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5654: - Fix Version/s: (was: 2.2.2-Ducc) future-DUCC Moved to a later release > ducc_l

[jira] [Closed] (UIMA-5732) DuccJobService should have a stop method to allow a clean shutdown

[ https://issues.apache.org/jira/browse/UIMA-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5732. > DuccJobService should have a stop method to allow a clean shutd

[jira] [Resolved] (UIMA-5732) DuccJobService should have a stop method to allow a clean shutdown

[ https://issues.apache.org/jira/browse/UIMA-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5732. -- Resolution: Fixed DuccJobService:stop calls DuccService.stop (in the ducc classpath) which now calls

[jira] [Created] (UIMA-5732) DuccJobService should have a stop method to allow a clean shutdown

Burn Lewis created UIMA-5732: Summary: DuccJobService should have a stop method to allow a clean shutdown Key: UIMA-5732 URL: https://issues.apache.org/jira/browse/UIMA-5732 Project: UIMA Issue

[jira] [Closed] (UIMA-3918) DUCC Command Line Interface (CLI) should provide driver_exception_handler_arguments

[ https://issues.apache.org/jira/browse/UIMA-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-3918. > DUCC Command Line Interface (CLI) should provide > driver_exception_handler_arg

[jira] [Resolved] (UIMA-3918) DUCC Command Line Interface (CLI) should provide driver_exception_handler_arguments

[ https://issues.apache.org/jira/browse/UIMA-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-3918. -- Resolution: Duplicate Was fixed in UIMA-4219 > DUCC Command Line Interface (CLI) should prov

[jira] [Closed] (UIMA-4727) Cassandra DB crashes with IBM Java

[ https://issues.apache.org/jira/browse/UIMA-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-4727. Resolution: Fixed Fixed with latest jams > Cassandra DB crashes with IBM J

[jira] [Resolved] (UIMA-5246) Serialize re-registration of DUCC services to reduce chance of duplicate services

[ https://issues.apache.org/jira/browse/UIMA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5246. -- Resolution: Duplicate The fix in 5372 has done the trick ... no more problems observed > Serialize

[jira] [Closed] (UIMA-5246) Serialize re-registration of DUCC services to reduce chance of duplicate services

[ https://issues.apache.org/jira/browse/UIMA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5246. > Serialize re-registration of DUCC services to reduce chance of duplicate > se

[jira] [Resolved] (UIMA-5551) Add registry support so pull services can locate their server

[ https://issues.apache.org/jira/browse/UIMA-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5551. -- Resolution: Fixed Replaced the -D specifying the pull service config file by an explicit -D specifying

[jira] [Reopened] (UIMA-5551) Add registry support so pull services can locate their server

[ https://issues.apache.org/jira/browse/UIMA-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reopened UIMA-5551: -- Simplify the implementation by passing the specifications directly instead of via a configuration file

[jira] [Closed] (UIMA-5678) When the SM starts a service process its environment has USER=ducc

[ https://issues.apache.org/jira/browse/UIMA-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5678. > When the SM starts a service process its environment has USER=d

[jira] [Closed] (UIMA-5649) The new ducc.uid property may cause migration problems as the default of "ducc" will be used

[ https://issues.apache.org/jira/browse/UIMA-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5649. > The new ducc.uid property may cause migration problems as the default of > "ducc&qu

[jira] [Resolved] (UIMA-5678) When the SM starts a service process its environment has USER=ducc

[ https://issues.apache.org/jira/browse/UIMA-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5678. -- Resolution: Not A Problem Assignee: Burn Lewis False alarm.  ducc_ling is launched as DUCC

[jira] [Resolved] (UIMA-5700) DUCC pull-service wrapper should not always kill the process when a work-item fails

[ https://issues.apache.org/jira/browse/UIMA-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5700. -- Resolution: Fixed Fix worked perfectly > DUCC pull-service wrapper should not always kill the proc

[jira] [Closed] (UIMA-5700) DUCC pull-service wrapper should not always kill the process when a work-item fails

[ https://issues.apache.org/jira/browse/UIMA-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5700. > DUCC pull-service wrapper should not always kill the process when a work-item >

Re: [VOTE] UIMA-AS 2.10.2 RC6

- Checked binary signatures - OK - Built from source & checked signatures - OK - Ran MeetingDetector example on binary & source builds - OK - Tested service targeting of an already-deployed service on both builds - OK But using runRemoteAsyncAE with both -d and -TargetServiceId didn't work as

[jira] [Created] (UIMA-5700) DUCC pull-service wrapper should not always kill the process when a work-item fails

Burn Lewis created UIMA-5700: Summary: DUCC pull-service wrapper should not always kill the process when a work-item fails Key: UIMA-5700 URL: https://issues.apache.org/jira/browse/UIMA-5700 Project

Re: [VOTE] UIMA-AS 2.10.2 RC5

- Checked signatures - OK - Tested binary with a dozen CASes - OK - Built from source & checked signatures - OK - Tested source build with a dozen CASes - OK - Spot checked README, RELEASE_NOTES, LICENSE, NOTICE, JIRAs, docs - OK - Tested TargetServiceId - OK Minor complaint - The (undocumented)

[jira] [Created] (UIMA-5678) When the SM starts a service process its environment has USER=ducc

Burn Lewis created UIMA-5678: Summary: When the SM starts a service process its environment has USER=ducc Key: UIMA-5678 URL: https://issues.apache.org/jira/browse/UIMA-5678 Project: UIMA Issue

Re: UIMA-AS Client API Change Discussion

dCAS(CAS cas, String serviceTargetId) > > sendAndReceiveCAS(CAS cas, List > > componentMetricsList, String serviceTargetId ) > > > > Another suggestion from Lou Degenaro is to create a new method > > > > submit(CAS cas, ProcessingOptions pos); > > > >

[jira] [Created] (UIMA-5654) ducc_ling should verify that it's "ducc" id is correct

Burn Lewis created UIMA-5654: Summary: ducc_ling should verify that it's "ducc" id is correct Key: UIMA-5654 URL: https://issues.apache.org/jira/browse/UIMA-5654 Project: UIMA Issue

[jira] [Resolved] (UIMA-5649) The new ducc.uid property may cause migration problems as the default of "ducc" will be used

[ https://issues.apache.org/jira/browse/UIMA-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5649. -- Resolution: Fixed Removed ducc.uid from the properties file and instead use the owner of ducc_util.py

[jira] [Created] (UIMA-5649) The new ducc.uid property may cause migration problems as the default of "ducc" will be used

Burn Lewis created UIMA-5649: Summary: The new ducc.uid property may cause migration problems as the default of "ducc" will be used Key: UIMA-5649 URL: https://issues.apache.org/jira/browse

Re: [VOTE] uimaj-3.0.0-beta-rc8

- checked signatures on binary - built from source and checked signatures - ran a couple UIMA pipelines on both builds - migrated a pipeline with many types and ran it on both builds - spot-checked readme etc. [X] +1 OK to release Minor complaints: - JCasImpl has a getType method that throws

[jira] [Closed] (UIMA-5641) Errors in custom containers cause class not found

[ https://issues.apache.org/jira/browse/UIMA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5641. Resolution: Fixed Access changed to public. Two methods in DuccAbstractProcessContainer must

[jira] [Created] (UIMA-5641) Errors in custom containers cause class not found

Burn Lewis created UIMA-5641: Summary: Errors in custom containers cause class not found Key: UIMA-5641 URL: https://issues.apache.org/jira/browse/UIMA-5641 Project: UIMA Issue Type: Bug

Re: [VOTE] uimaj-2.10.2 rc2

- Downloaded binary & source and checked md5 & sha1 signatures - Built from source - Ran 2 pipelines with both the binary and source builds - Spot checked license, notices & lira reports [+1] OK On Mon, Oct 30, 2017 at 5:09 PM, Marshall Schor wrote: > Hi, > >

Re: [jira] [Assigned] (UIMA-5605) DUCC scheduler ArrayIndexOutOfBoundsException

Jörg, We were able to reproduce this problem as Eddie described and I've verified that it is now fixed. Will be in next DUCC release. Burn On Thu, Oct 26, 2017 at 2:41 PM, Burn Lewis (JIRA) <dev@uima.apache.org> wrote: > > [ https://issues.apache.org/jira/browse/UI

[jira] [Updated] (UIMA-5551) Add registry support so pull services can locate their server

[ https://issues.apache.org/jira/browse/UIMA-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5551: - Fix Version/s: (was: future-DUCC) 2.2.2-Ducc > Add registry support so p

[jira] [Closed] (UIMA-5605) DUCC scheduler ArrayIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/UIMA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5605. > DUCC scheduler ArrayIndexOutOfBoundsExcept

[jira] [Resolved] (UIMA-5605) DUCC scheduler ArrayIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/UIMA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5605. -- Resolution: Fixed Fixed error in setting free space when a machine size changes. This problem was more

[jira] [Assigned] (UIMA-5605) DUCC scheduler ArrayIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/UIMA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis reassigned UIMA-5605: Assignee: Burn Lewis > DUCC scheduler ArrayIndexOutOfBoundsExcept

[jira] [Updated] (UIMA-5605) DUCC scheduler ArrayIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/UIMA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5605: - Fix Version/s: (was: future-DUCC) 2.2.2-Ducc > DUCC schedu

[jira] [Closed] (UIMA-5606) DUCC ResourceManager crashed with ArrayIndexOutOfBounds

[ https://issues.apache.org/jira/browse/UIMA-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5606. > DUCC ResourceManager crashed with ArrayIndexOutOfBou

[jira] [Updated] (UIMA-5606) DUCC ResourceManager crashed with ArrayIndexOutOfBounds

[ https://issues.apache.org/jira/browse/UIMA-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5606: - Fix Version/s: (was: future-DUCC) 2.2.2-Ducc > DUCC ResourceManager cras

[jira] [Created] (UIMA-5615) DUCC's WaitingForDriver should not include the JD initialization phase

Burn Lewis created UIMA-5615: Summary: DUCC's WaitingForDriver should not include the JD initialization phase Key: UIMA-5615 URL: https://issues.apache.org/jira/browse/UIMA-5615 Project: UIMA

[jira] [Commented] (UIMA-5611) UIMA-DUCC: Agent fails to kill a child process sometimes

[ https://issues.apache.org/jira/browse/UIMA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199493#comment-16199493 ] Burn Lewis commented on UIMA-5611: -- These became defunct processes so kill -9 won't help ... perhaps agent

Re: [jira] [Updated] (UIMA-5605) DUCC scheduler ArrayIndexOutOfBoundsException

Ironically we also hit this problem yesterday ,,, I don't know why it has waited this long to show up. Removing that piece of code will be the simplest fix but I suspect its a sign of a problem elsewhere. On Fri, Oct 6, 2017 at 8:53 AM, Burn Lewis (JIRA) <dev@uima.apache.org>

[jira] [Resolved] (UIMA-5606) DUCC ResourceManager crashed with ArrayIndexOutOfBounds

[ https://issues.apache.org/jira/browse/UIMA-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5606. -- Resolution: Duplicate Already reported in 5605 > DUCC ResourceManager cras

[jira] [Updated] (UIMA-5605) DUCC scheduler ArrayIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/UIMA-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis updated UIMA-5605: - Fix Version/s: future-DUCC > DUCC scheduler ArrayIndexOutOfBoundsExcept

[jira] [Created] (UIMA-5606) DUCC ResourceManager crashed with ArrayIndexOutOfBounds

Burn Lewis created UIMA-5606: Summary: DUCC ResourceManager crashed with ArrayIndexOutOfBounds Key: UIMA-5606 URL: https://issues.apache.org/jira/browse/UIMA-5606 Project: UIMA Issue Type: Bug

Re: [jira] [Commented] (UIMA-5587) DUCC Process Manager (PM) takes OOM on Apache DUCC demo

Since this affects all daemons how about a pre-fetch of 1? On Thu, Sep 28, 2017 at 6:48 PM, Jaroslaw Cwiklik wrote: > Actually, the correct broker decoration should be: > > # # The broker *client* url decoration (ie - DUCC daemons). >

[jira] [Created] (UIMA-5589) DUCC may preempt too many shares in some cases

Burn Lewis created UIMA-5589: Summary: DUCC may preempt too many shares in some cases Key: UIMA-5589 URL: https://issues.apache.org/jira/browse/UIMA-5589 Project: UIMA Issue Type: Bug

[jira] [Commented] (UIMA-5551) Add registry support so pull services can locate their server

[ https://issues.apache.org/jira/browse/UIMA-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175447#comment-16175447 ] Burn Lewis commented on UIMA-5551: -- Added a simple file-based registry and also a configuration properties

[jira] [Resolved] (UIMA-5551) Add registry support so pull services can locate their server

[ https://issues.apache.org/jira/browse/UIMA-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-5551. -- Resolution: Fixed > Add registry support so pull services can locate their ser

[jira] [Created] (UIMA-5582) Launch external pingers with the user-supplied --jvm instead of DUCC's

Burn Lewis created UIMA-5582: Summary: 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

[jira] [Created] (UIMA-5581) When a CLI request fails because ducc is down, say so

Burn Lewis created UIMA-5581: Summary: When a CLI request fails because ducc is down, say so Key: UIMA-5581 URL: https://issues.apache.org/jira/browse/UIMA-5581 Project: UIMA Issue Type

  1   2   3   4   5   6   7   8   9   10   >