Re: [DISCUSS] New PMC chairperson

[Burn Lewis]

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:

> The resolution was submitted, following the Apache change PMC Chair
> process;
> it's on the agenda for the next Board meeting scheduled for November 18th.
>
> Cheers. -Marshall
>
> On 10/29/2020 2:47 PM, Marshall Schor wrote:
> > Thank you all for your wonderful comments (blush!).
> >
> > I feel with the recent activity picking up under Richard's initiative
> that UIMA
> > is in good hands.
> >
> > Based on this consensus, I'll draft the appropriate resolution for the
> next
> > board meeting.
> >
> > -Marshall
> >
> > On 10/18/2020 10:19 AM, Marshall Schor wrote:
> >> Hi everyone,
> >>
> >> After a decade of serving as the UIMA Project's PMC Chairperson, I've
> decided to
> >> step down as the UIMA PMC chair, as soon as we can reach a consensus on
> a new
> >> chairperson.
> >>
> >> I have found being the chairperson of this project and working with the
> >> community on it, to be extremely personally rewarding, for which I am
> very
> >> grateful.  My own personal job role has shifted considerably over these
> years,
> >> and I now find that I currently do not have time to focus on this role.
> >>
> >> It's a good policy to have new people with fresh energy step up into
> this role
> >> from time to time.
> >>
> >> In terms of possible candidates, I see that Richard Eckart de Castilho
> has
> >> recently become quite active, and has picked up the activity around the
> core
> >> uimaj project as well, including working on many tricky internal
> issues;  if he
> >> were willing, I think he would be a very good candidate as the next PMC
> chair.
> >>
> >> Please express your opinions, and let's form a consensus, which we can
> then
> >> formalize with a [VOTE].
> >>
> >> -Marshall
> >>
>

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

[Burn Lewis]

[ ] -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 use such a common name.

On Thu, Feb 6, 2020 at 11:48 AM Eddie Epstein  wrote:

> UIMA-C++ v.3.0.0 release candidate 1 is ready for voting.
>
> This release includes extensive code changes to allow uimacpp to compile
> and run on modern machines. It also bundles much more up-to-date 3rd party
> dependencies. Code changes suggested by the community have been integrated.
> New documentation and tools have been added to facilitate building an SDK
> from source, including 3rd party libraries.
>
> For the complete list of issues fixed in this release please search
> https://issues.apache.org/jira/projects/UIMA
> for: project="UIMA", component="C++ Framework", FixVersion="3.0.0C"
>
> The source and binary tars are staged to
> https://dist.apache.org/repos/dist/dev/uima/uimacpp/3.0.0-rc1
>
> The GIT branch for this rc tag is here:
> https://github.com/apache/uima-uimacpp/releases/tag/uimacpp-3.0.0-rc1
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0 Don't care
> [ ] -1 Not OK to release, because ...
>

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

[Burn Lewis]

[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 move UIMA-AS to Git. Let me know with +1 or otherwise to
> > move UIMA-AS to a writable GIT repo and switch to using GIT for source
> > control system.
> >
> > [X] +1 OK to move UIMA-AS from SVN to (writable) GIT for source control
> >
> > [ ]  0  don't care
> >
> > [ ]  -1 not OK to move UIMA-AS from SVN to (writable) GIT for source
> control
> > because...
> >
> > -Jerry Cwiklik
> >
>

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

[Burn Lewis]

+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. > > Please Vote to move this
> to GIT :-) > > -Marshall > > On 10/1/2019 4:58 PM,
> Marshall Schor wrote: >> Hi, >> >> To encourage more community
> maintenance, I'd
> like to move the current read-only >> mirror git repo for uimacpp to a r/w
> status. >> >> Does anyone have any concerns? >> >> If not, I'll put in a
> similar
> INFRA request for this as we did for uima-uimaj >> recently. >> >>
> -Marshall >>
> >> https://github.com/apache/uima-uimacpp - the current readonly mirror.
> >> >> >
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEOn/mVSh3S1eNEDz+zHYv/c0Ez9YFAl2coh0ACgkQzHYv/c0E
> z9ZJGA/+L2lZZoasCbBAkj5Bubroha3fV7NLpNdBXXuYT2a5qNaVddx1OVtJ4RK1
> 24XUflgsXBFb8DyBGCrHW1VfOBmSYyduNRXWNj3En5RqeaSbjgbSpjUjYOLHkbhW
> t1wZUJTrd1r+CNUWISOirQt3QOwYQ7swJ4fG1Rz3O6zDRWWw9wqdv27YW6xrzIAu
> qVaRmLUM8ZeceITLZypr3sgdjfpRFC0YwuvvYHPQHG6RU6HuetRHyL/PmTLGAH18
> Ve8mIMABi+oY0Efqpijy1lWB9U1EGgUWVOsEaJS0ToB/UhsW9S/TU1mtsUgZvcWO
> Qvb3SwEprIksieeYYqn9KcPFsYKHpbVupzENWz7Jo5AFNwNVY41AkBU3NZ6AiGSL
> d1qXkawfl3Z4JTcD+p79VUmarFNQtyvu0PvbI/xL9kXq2xzRA4882PfVBHTxFPDb
> HaQbwCz3kiO/+S88bpfnayEqBTcIcSKWdKq75ghq7lYAFDO0kprzl4zDh99P8uNZ
> kZbZ/7e7bHoE/CMwmbpp2twl+axn6ZoCa+6p7hYnkANcq/lXHJIOcopJyjxAVJVV
> x+IkOwurtqQYm/0DIBw0TlWEUgu1p1kuuQpAMq3DIqsRiOji8AGKYEGRUcxHVCBQ
> 0RnVc6r9TBle6skew0MM2zLLfG2aFTWD/+/LkOv7B9yfX2DYaYg=
> =eZJR
> -END PGP SIGNATURE-
>
>

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

[Burn Lewis (Jira)]

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: Improvement
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: future-DUCC


Replace the multiple DuccHead classes by one that checks if a reliable 
installation & if a head node is active.  Simplify scripts by not checking if 
the Keepalived configuration is consistent with the head node declarations.  
Allow a single-node DB to be auto-managed by the master head node.  Get the 
(first part of) the current node name via python from ducc_base's 
self.localhost rather than running /bin/hostname.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

[Burn Lewis (Jira)]

 [ 
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 shell
> -
>
> Key: UIMA-6120
> URL: https://issues.apache.org/jira/browse/UIMA-6120
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Minor
> Fix For: 3.0.1-Ducc
>
>
> The script should not assume PWD has been set in the environment



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

[Burn Lewis (Jira)]

 [ 
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 shell
> -
>
> Key: UIMA-6120
> URL: https://issues.apache.org/jira/browse/UIMA-6120
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Minor
> Fix For: 3.0.1-Ducc
>
>
> The script should not assume PWD has been set in the environment



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

[Burn Lewis (Jira)]

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
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: 3.0.1-Ducc


The script should not assume PWD has been set in the environment



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

[Burn Lewis (JIRA)]

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: Improvement
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: future-DUCC


If a large number of jobs are submitted and all the available job-driver slots 
are in use jobs will be rejected.  The rejection msg should be changed from 
"job driver node unavailable" to "all job driver allocations in-use or node 
unavailable".  Eventually another JD allocation will be obtained with more 
slots.  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: future-DUCC


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
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

 [ 
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 names
> -
>
> Key: UIMA-6099
> URL: https://issues.apache.org/jira/browse/UIMA-6099
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 3.0.0-Ducc
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: future-DUCC
>
>
> Currently job requests hang if the scheduling class is unknown



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

 [ 
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 DuccLogger
> ---
>
> Key: UIMA-6109
> URL: https://issues.apache.org/jira/browse/UIMA-6109
> Project: UIMA
>  Issue Type: Improvement
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Minor
> Fix For: future-DUCC
>
>
> Only the main daemon packages are logged in the daemon log files ... msgs 
> from classes in the transport & common projects are sent to system.out and 
> lost 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

 [ 
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 in 
$DUCC_HOME/logs/..log.  Added user-log4j.xml for the JD & 
JP which logs to the console for duccling to capture.

> 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
>  Components: DUCC
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: future-DUCC
>
>
> Only the main daemon packages are logged in the daemon log files ... msgs 
> from classes in the transport & common projects are sent to system.out and 
> lost 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [VOTE] uimaj 3.1.0 rc1

[Burn Lewis]

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
ran a simple annotator via DUCC: OK

[X] +1 OK to release

On Sun, Aug 11, 2019 at 6:51 PM Marshall Schor  wrote:

> hoping those who voted or tested 3.0.3 can quickly review this - it just
> changed
> the version per Richard's suggestion.
>
> -Marshall
>
>

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

[Burn Lewis (JIRA)]

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: UIMA
  Issue Type: Bug
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: future-DUCC


If the RM purges a node (e.g. missed heartbeats) the SM should not treat that 
as an init or runtime failure, allowing another instance to be started.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: future-DUCC


Only the main daemon packages are logged in the daemon log files ... msgs from 
classes in the transport & common projects are sent to system.out and lost 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: [VOTE] uimaj-2.10.4-rc1

[Burn Lewis]

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 annotators: OK

[x] +1 OK to release

On Thu, Aug 1, 2019 at 4:22 AM Richard Eckart de Castilho 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Spot checked source changes: ok
> Dist artifact signatures: good
> Built from svn tag: ok
> RELEASE NOTES: ok
> API report spot check: ok
> Fixed issues list: ok
> README file: ok
>   There were a few additional oddly indented lines - I have committed
>   a corresponding change to trunk (no issue).
> Built DKPro Core against RC: ok
>
> [x] +1 OK to release
> -BEGIN PGP SIGNATURE-
>
> iQKTBAEBCgB9FiEEPY2MKJLmMo4NDQCrO8wPPFbjAA4FAl1CoOlfFIAALgAo
> aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNE
> OEQ4QzI4OTJFNjMyOEUwRDBEMDBBQjNCQ0MwRjNDNTZFMzAwMEUACgkQO8wPPFbj
> AA64Lg//UmFmlubaalQrSnKEJX28QtOI9E5jemoVLm1cGCkT9mpk0RC7eRlRVvU+
> aSAHxrDrCkeaH+l6WWn66f3V2a0mIsLx9zusncByl+ImNEb7895EkPWW3caBapj0
> D/mMr9phh+Ka7XkF2Bbww81qlSE1nz7gz/ZcQbGlf1E+VehG+xxh2mO609jDQFgv
> WcXxIvnZ0TgURePfH116YvuS1FH0GjZcI9IELiWOAW5ZXH/lKoem0rZTo+IFsYrc
> wFTcX8dCLQ2rwLy6IvHW7Oe/O0Ub5WRmRZNAAby8aMXFTtBB+8QBJa50gobWWzcJ
> meQmdTydiRlASkILNAoGoNLL0pSG6Xlsk75a0AsrxNOsR2XTqKcaFIss75kvAhS6
> GN+k0ltpIpARMG0LadgiCZRL4jaRfAypeJIsagrGEPNygnr2K8C+Z8fCOn8cweYb
> jHAbMTS78ZdwlJPu173fX7dt1XL6VGJYbX3sYJ/An2RDZyB2Vr4WIGKGVt2C5UcR
> KBimossCuWog7uJyhKlGX0nASobaQDNDFncJO1SYqPMigihJ67PAWIB9vdekEakC
> ZEGNJSkDWNms2OYtFhXUscMy+T0mwbTMke5R1pslw05bJXyeOBHVqC2JPR1gm3tL
> L2ya3q7oWUYhCKBfTr6GuMBJJ3qmL4aMaw2VwXRl5YPINPHFQQU=
> =FY/b
> -END PGP SIGNATURE-
>
>

Re: [VOTE] uimaj 3.0.3 rc2

[Burn Lewis]

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

x] +1 OK to release

On Mon, Jul 22, 2019 at 3:55 PM Marshall Schor  wrote:

>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
> signatures OK
> compare source-release with svn tag : OK
> installed plugins into Eclipse 2019-06 OK
> imported example project into Eclipse, it built OK, ran document analyzer:
> OK
> made new type system descriptor, ran JCasGen: OK
> used the Component Descriptor Editor to delete some features - works OK
> build from sources: OK
> issues-fixed jira report: OK
> api-change reports: OK
> ran document analyzer from bin package, viewed results- OK
> compare licenses with 3.0.2 - no change
> spot check license on staging repo: OK
>
> [x] +1 OK to release
>
> Marshall Schor
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEOn/mVSh3S1eNEDz+zHYv/c0Ez9YFAl02FJUACgkQzHYv/c0E
> z9Zt3g/+OWCvnxA5ZWuBhyEtidnhS1n/FmOqKLfl/WTn53+cuafxyOh9y8wZCVYS
> 1BbLkTNvlrq6fboYPW26fb545qduVtcHd2jSzbSly3RKtyXXA6hhv+a/vawFsxuF
> mFnDt/F2cyoG2XD2tSBh9TNqlZ2VmHHSDOy9ONlpK5c1i7qg0ntRvlu2xoxJ1Msz
> hmTQuW21meEknq4rdD+uMuNU9ZTnOpmIFgbxbfuG41lLnXO7f3m9xqV03eeonLbE
> bB2Dp8JEs8IBDGcQErG2+xOO1dBNJD0roWw8xULHwzPCB2cWyQ9vLdSop4NKX/3n
> nG9U6rYu0MI4MBNuDbJMOmZ9+CXWLYNEgfojd9XqYAdkuik1sEDPywGm2dco/y9H
> Pu2R/TKiw2gMK6PLXVlrlCRaaK/iU+T+Xzg2JRP6gmTKf5xUv8iqQJ/fb6PAoMgq
> mBNij1cIehFnBJmcolwegcRcgWDQViTK7NL1886XCqRxdR93k1AcY8DFGPH4YoFz
> 7PNkVktrb0bb4iy2fmVEKbF47A1yAyniYXRK3TK8TCTFNnt1dcKEPhyQwyGX1Sxr
> zb2yRLWum3cqinhMWqgCWW/kq+xlFvR2IRHJvgjD8OYkyAn+dGqH0dE3cEjjl7l5
> ms4rG91EnTTZEMNIEZwua5gK6ZBuHyTf6OcbGHtHqHAEDGEfmaQ=
> =48ve
> -END PGP SIGNATURE-
>
>

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

[Burn Lewis (JIRA)]

 [ 
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

> 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: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Major
> Fix For: future-DUCC
>
>
> The head-node state "unspecified" actually means a single-head system



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

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: Bug
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: future-DUCC


The head-node state "unspecified" actually means a single-head system



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Affects Versions: 3.0.0-Ducc
Reporter: Burn Lewis


Only one of the 2 ways to start agents makes the check ... change so both use 
the same code



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

 [ 
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 names
> -
>
> Key: UIMA-6099
> URL: https://issues.apache.org/jira/browse/UIMA-6099
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 3.0.0-Ducc
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: future-DUCC
>
>
> Currently job requests hang if the scheduling class is unknown



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

[ 
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 default -- check 
for valid name -- change to a fixed class if necessary.

> DUCC should reject invalid scheduling class names
> -
>
> Key: UIMA-6099
> URL: https://issues.apache.org/jira/browse/UIMA-6099
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 3.0.0-Ducc
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: future-DUCC
>
>
> Currently job requests hang if the scheduling class is unknown



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Affects Versions: 3.0.0-Ducc
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: future-DUCC


Currently job requests hang if the scheduling class is unknown



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[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

[Burn Lewis (JIRA)]

 [ 
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 for daemons running with the installer id which may not be "ducc"

> ducc_update refuses to run even though there are no ducc daemons running on 
> the head node comprising the attempted update
> -
>
> Key: UIMA-6089
> URL: https://issues.apache.org/jira/browse/UIMA-6089
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Burn Lewis
>Priority: Major
> Fix For: future-DUCC
>
>
> -bash-4.2$ ducc_runtime/admin/ducc_update ducc_runtime 
> download/uima-ducc-3.0.1-SNAPSHOT-bin.tar.gz 
> checking for ducc running, may take a few minutes...
> ERROR - DUCC appears to be running ... please run 
> '/opt/ducc/install/ducc/apache-uima-ducc-3.0.0/admin/stop_ducc -a'
> -bash-4.2$ ps -elf | grep ducc
> 4 S root 23999 14566  0  80   0 - 44933 poll_s 06:50 ?    00:00:00 
> sshd: ducc [priv]
> 5 S ducc 24192 23999  0  80   0 - 44933 poll_s 06:51 ?    00:00:00 
> sshd: ducc@pts/0
> 0 S ducc 24193 24192  0  80   0 - 28877 do_wai 06:51 pts/0    00:00:00 
> -bash
> 0 R ducc 27966 24193  0  80   0 - 38840 -  06:58 pts/0    00:00:00 ps 
> -elf
> 0 S ducc 27967 24193  0  80   0 - 28177 pipe_w 06:58 pts/0    00:00:00 
> grep --color=auto ducc



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

[Burn Lewis (JIRA)]

 [ 
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 ServiceConfiguration
> -
>
> Key: UIMA-5975
> URL: https://issues.apache.org/jira/browse/UIMA-5975
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Minor
> Fix For: 3.0.0-Ducc
>
>
> ServiceConfiguration needs a setWaitTime method.
> Also suppress an INFO log message produced for every task received in the 
> service, and remove trailing white-space.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: 3.0.0-Ducc


ServiceConfiguration needs a setWaitTime method.

Also suppress an INFO log message produced for every task received in the 
service, and remove trailing white-space.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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
Reporter: Burn Lewis
Assignee: Burn Lewis






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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
> -
>
> Key: UIMA-5941
> URL: https://issues.apache.org/jira/browse/UIMA-5941
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 2.2.2-Ducc
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: 2.2.3-Ducc
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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
> -
>
> Key: UIMA-5941
> URL: https://issues.apache.org/jira/browse/UIMA-5941
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 2.2.2-Ducc
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: 2.2.3-Ducc
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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
> -
>
> Key: UIMA-5941
> URL: https://issues.apache.org/jira/browse/UIMA-5941
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 2.2.2-Ducc
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: 2.2.3-Ducc
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

[ 
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 to recover 
from, e.g. IndexOutOfBounds, ConcurrentModification.  But a missing view can be 
handled so the claim that JCas::getView throws a CasException is reasonable and 
I've seen code that catches this and attempts to recover.  Unfortunately it 
calls CAS::getView which throws CasRuntimeException.  Ideally the JCas & CAS 
methods should have been given similar declarations but in an effort to reduce 
the impact on existing code we could catch CasRuntimeException in the JCas 
method and throw a CasException, leaving the Javadocs as-is.

> The JCas getView method throws CasRuntimeException not CasException
> ---
>
> Key: UIMA-5869
> URL: https://issues.apache.org/jira/browse/UIMA-5869
> Project: UIMA
>  Issue Type: Bug
>  Components: Core Java Framework
>Affects Versions: 2.10.2SDK, 3.0.0SDK
>Reporter: Burn Lewis
>Priority: Minor
>
> Code that uses JCas getView expects CasException to be thrown if a view is 
> missing, but instead the underlying CAS.getView method throws 
> CasRuntimeException.
> Either the code or the Javadocs should be fixed.  Since a missing view is not 
> uncommon, throwing an unchecked exception is not very useful.  Making the 
> framework code match the Javadocs should have tminimal impact on existing 
> user code.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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
  Issue Type: Bug
  Components: Core Java Framework
Affects Versions: 3.0.0SDK, 2.10.2SDK
Reporter: Burn Lewis


Code that uses JCas getView expects CasException to be thrown if a view is 
missing, but instead the underlying CAS.getView method throws 
CasRuntimeException.

Either the code or the Javadocs should be fixed.  Since a missing view is not 
uncommon, throwing an unchecked exception is not very useful.  Making the 
framework code match the Javadocs should have tminimal impact on existing user 
code.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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: Bug
  Components: DUCC
Reporter: Burn Lewis
 Fix For: future-DUCC


Problem is  JobByTimeSorter in NodepoolScheduler



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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
 Project: UIMA
  Issue Type: Bug
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: 2.2.3-Ducc


Added a 30sec delay before sending the first work request.  The real problem 
may be in the sequence of state messages from agent -> OR -> SM



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: 2.2.3-Ducc


The service returns a stringified stack trace which does not need to be 
deserialized by the client



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: 2.2.3-Ducc


Build ducc_ling in place after removing existing one.  Check in start_ducc that 
it is elevated (unless non-elevated explicitly indicated)

Fix ducc_update when PWD is not in the environment

check_ducc should merge in the site properties

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

[ 
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 to ServiceConfiguration & 
removed the clientURL validation check as it is optional.

> UIMA-DUCC: Create a new project for the pull service
> 
>
> Key: UIMA-5756
> URL: https://issues.apache.org/jira/browse/UIMA-5756
> Project: UIMA
>  Issue Type: New Feature
>  Components: DUCC
>Reporter: Jerry Cwiklik
>Assignee: Jerry Cwiklik
>Priority: Major
> Fix For: 2.2.3-Ducc
>
>
> Currently, Ducc's pull service is made up of classes from common, transport, 
> user, and container projects. Its transport and protocol handler are fixed in 
> the code. No way to plug in alternatives. The service is configured via -D's 
> and env vars. Such approach prevents collocating multiple services in the 
> same JVM. 
> The proposal is to move/refactor transport, protocol handler related classes 
> to a new project uima-ducc-pullservice. Also, move/refactor wrapper code 
> which deploys UIMA aggregate pipelines. The new project will be self 
> contained with no dependency on other Ducc projects/jars. It will have 
> dependency on UIMA, HttpClient, and Jetty.
> The new code will allow an application to instantiate as many instances of a 
> service as it needs. It will allow to plugin custom ProtocolHandler, 
> ErrorHandler, and ServiceMonitor with default implementation for these 
> provided.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

[ 
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.ducc.ps."

Renamed test classes to satisfy the maven plugin. (must match: Test* | *Test | 
*TestCase)

Commented out the test in JunitProtocolHandlerTestCase

> UIMA-DUCC: Create a new project for the pull service
> 
>
> Key: UIMA-5756
> URL: https://issues.apache.org/jira/browse/UIMA-5756
> Project: UIMA
>  Issue Type: New Feature
>  Components: DUCC
>Reporter: Jerry Cwiklik
>Assignee: Jerry Cwiklik
>Priority: Major
> Fix For: 2.2.3-Ducc
>
>
> Currently, Ducc's pull service is made up of classes from common, transport, 
> user, and container projects. Its transport and protocol handler are fixed in 
> the code. No way to plug in alternatives. The service is configured via -D's 
> and env vars. Such approach prevents collocating multiple services in the 
> same JVM. 
> The proposal is to move/refactor transport, protocol handler related classes 
> to a new project uima-ducc-pullservice. Also, move/refactor wrapper code 
> which deploys UIMA aggregate pipelines. The new project will be self 
> contained with no dependency on other Ducc projects/jars. It will have 
> dependency on UIMA, HttpClient, and Jetty.
> The new code will allow an application to instantiate as many instances of a 
> service as it needs. It will allow to plugin custom ProtocolHandler, 
> ErrorHandler, and ServiceMonitor with default implementation for these 
> provided.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: 2.2.3-Ducc


If the DB fails the daemons merely log the problem and carry on in a bad state.

The SM will not persist any registry changes and will confuse the WS

The RM thread handling node updates is blocked by synchronized methods in the 
scheduler and cause nodes to be falsely purged of their work

The OR fails writing the checkpoint



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] release uima addon ConceptMapper 2.10.2

[Burn Lewis]

- 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: SHA512
>
> signatures: OK
> compare with svntag: OK
> build from sources: OK
> test in a big application: OK
> issuesFixed: OK
>
> api change report: not present.
> The build produces it, but the bin assembly is missing the configuration
> to
> include it in the result.
> I'm considering this not a blocker.
>
> License/notice/readme/releasenotes: OK
>
> Maven artifacts:
> still has md5 sigs (should be removed) = not a blocker.
> pear artifact has license/notice inside Jar, but not at outer level.
>I'm considering this not a blocker.
>
> Users guide: OK
>
> Tested by replacing older version, in a big application: OK
>
> [X] +1 OK to release
>
> - -Marshall Schor
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCgAGBQJa2NZzAAoJEMx2L/3NBM/W3mwP+gPSlH0QqjvisC6K/T/zwWwf
> WfhjQ3IPgDMwREQyu2uDHRT+d9fakc5fGgx86Hex65SabTOraA8jO7yglX8W8YZ1
> c9nNSfh358PvgcdU+aLrCQ4AE4H20FxEn0TndnAQ0Wtv+vt/7weETu4AtUuUo5hi
> edHQPvGGdpSS8ECZUJM/rwPpT+MzEqgUynoyRh6cflcw9VAKYYep0D9OdqgyXrGg
> H/ANF2K4HHnx/ZnJAl84tVCapiDqFfF7KN+vWrMSiK3yN8234BUEWO5t8FUSZ9km
> 4vTNNmowqqg2S9fV9Py8dcMAJhJpMUVuskZuLh/h18Ug3w66iAihBlb6cHFzbT4i
> vKd3gRPIvWPxJbOtOIUpjxIfxG1lMTz4vR0sgMvWpQVBO8d7vgWQEdMoFNOBw3C4
> fxE3sI4uNjWwx8+HGURohGiTFXbpEYBhqDaHNo0ahn5UQwcRKXEG55VFQ+GBvwKw
> zRYf14yJ3qUlPQjzxbHX9Uy62BRmKlDM6XEy7eygmYa5j7moD2XaS8vTWtLmnSrn
> WX6bVOgoxcIlM/lJo/YAv/oIxP7WDbp6PT/LaEPZa+n7LXwF7vEXJHRwm8POB8oh
> 6299UD81De9G4Y+jzKj/0tf08GCS9zxEJW5pIXKqygPA5hXAU57S7d3Pmdi/aB1N
> V/DWGRshTrwx2Eh+cgz6
> =FkKr
> -END PGP SIGNATURE-
>
>

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

[Burn Lewis]

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 object.

Burn

On Thu, Apr 19, 2018 at 4:46 PM, Richard Eckart de Castilho (JIRA) <
dev@uima.apache.org> wrote:

>
> [ https://issues.apache.org/jira/browse/UIMA-5763?page=
> com.atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel=16444760#comment-16444760 ]
>
> Richard Eckart de Castilho commented on UIMA-5763:
> --
>
> > re: read-only flag: if such is set, and a user modifies the CAS, should
> this throw an exception or something else?
>
> Yes, an exception should be thrown.
>
>
>
> > UIMA: need a way to lock a CAS to prevent user from releasing it
> prematurely
> > 
> 
> >
> > Key: UIMA-5763
> > URL: https://issues.apache.org/jira/browse/UIMA-5763
> > Project: UIMA
> >  Issue Type: New Feature
> >  Components: UIMA
> >Reporter: Jerry Cwiklik
> >Assignee: Marshall Schor
> >Priority: Major
> > Fix For: 3.0.1SDK, 2.10.3SDK
> >
> >
> > UIMA-AS client supports an async style of sending CASes for processing
> to a remote service. When using sendCAS( CAS aCas), the code serializes CAS
> and dispatches it to the remote but keeps the CAS in a cache. When a reply
> comes, the cached CAS is used to deserialize a response. The contract is
> that the user code should not call CAS.release(). When a reply finally
> comes, the CAS is handed over to an application callback and upon return
> from the callback, the UIMA-AS releases the CAS.
> > Problem: there is nothing to prevent user code to violate the contract.
> If CAS.release() is called while UIMA-AS client awaits reply (or during
> reply deserialization), bad things happen. In a specific use case, a NPE
> was thrown during deserialization and debugging was quite painful.
> > Proposed solution: to protect integrity of a CAS need a way to
> lock/unlock it. Such facility can be added to CASImpl class. When a user
> code tries to call release()  when a CAS is locked,  the code should throw
> an exception (IllegalStateException or similar).
> > WDYT?
> >
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>

Re: [VOTE] UIMA-AS 2.10.3 RC1

[Burn Lewis]

- 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 checked docs

[x] +1 OK to release

On Mon, Mar 19, 2018 at 6:59 PM, Jaroslaw Cwiklik 
wrote:

> - Built from source - OK
> - Spot checked signatures - OK
> - issues fixed - OK
> - Checked README, RELEASE_NOTES,LICENSE and NOTICE - OK
> - Ran runRemoteAsyncAE.sh - OK
> - Ran UIMA-AS extended tests which includes a new test which validates
> deployment of async aggregate with a delegate which uses Jms Service
> Descriptor - OK
> - Created deployment descriptor which use Jms Service Descriptor to connect
> to Room Number Annotator. Launch two instances of it to test ClientID bug
> found in UIMA-AS v2.10.2 - OK
> - Imported uima examples into eclipse (oxygen) and tested UIMA Deploy AS
> Service.launch and UIMA Run Remote Async AE.launch - OK
> - Installed UIMA-AS eclipse plugins - OK
> - Documentation  - OK
>
> [x] +1 OK to release
>
> Jerry
>
> On Fri, Mar 16, 2018 at 3:04 PM, Jerry Cwiklik  wrote:
>
> > Hi,
> >
> > the UIMA-AS 2.10.3 release candidate 1 is ready for voting.
> >
> > This version contains the following fixes:
> >
> > - Modified client code to assign unique ClientID to broker connection
> > which fixes InvalidClientIDException
> > - Fixed ClassCastException when async aggregate initializes delegate with
> > JMS Service Descriptor
> > - Fixed broken classpath and logging for UIMA-AS run configurations
> > - Fixed eclipse update site pom to copy *.jar.pack.gz files to plugins
> > folder
> >
> > The list of changes in Jira:
> > http://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%2
> > 02.10.3AS%20AND%20project%20%3D%20UIMA
> >
> > The source and binary zip/tars are staged to
> > http://dist.apache.org/repos/dist/dev/uima/uima-as/2.10.3/RC1/
> >
> > The eclipse update subsite is here:
> > http://dist.apache.org/repos/dist/dev/uima/eclipse-update-site/uima-as/
> >
> > The Maven artifacts are here:
> > http://repository.apache.org/content/repositories/orgapacheuima-1191
> >
> > The SVN tags are here:
> > http://svn.apache.org/repos/asf/uima/uima-as/tags/uima-as-2.10.3/
> >
> > See http://uima.apache.org/testing-builds.html for suggestions on how to
> > test release candidates.
> >
> > Please vote on release:
> >
> > [ ] +1 OK to release
> > [ ] 0   Don't care
> > [ ] -1 Not OK to release, because ...
> >
> > --
> > Jerry Cwiklik
> > Apache UIMA
> >
> >
>

Re: [VOTE] UIMA-DUCC 2.2.2 RC4

[Burn Lewis]

+ 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 1.job etc. on that build
+ spot checked install, readme, release notes, issues fixed, licenses &
notices

[X] +1 OK to release

On Thu, Mar 15, 2018 at 10:24 AM, Jaroslaw Cwiklik 
wrote:

> Hi,
> - Spot checked signatures - OK
> - Built from source - OK
> - Issues Fixed report - OK
> - Spot checked duccbook - OK
> - Spot checked README, RELEASE_NOTES, NOTICE, LICENSE - OK
> - Spot checked links in duccmon - OK
> - Spot checked javadocs API - OK
> - Ran 1.job, 1.dd.job, 1.error.job - OK
> - Ran 1.job with --wait_for_completion - OK
>
> [X] +1 OK to release
>
> Jerry Cwiklik
>
> On Thu, Mar 15, 2018 at 10:24 AM, Jaroslaw Cwiklik 
> wrote:
>
> > Ducc does not use Tomcat directly but there is a jar with tomcat classes:
> >
> > /webserver/lib/apache-jsp/org.mortbay.jasper.apache-jsp-8.0.33.jar
> >
> > In that jar file there is a notice file which DUCC NOTICE includes.
> >
> > - Jerry
> >
> > On Thu, Mar 15, 2018 at 9:10 AM, Lou DeGenaro 
> > wrote:
> >
> >> > Downloaded uima-ducc-2.2.2-bin.tar.gz
> >>  >> 2/RC4/uima-ducc-2.2.2-bin.tar.gz>
> >> : OK
> >>
> >> > Installed and started Apache DUCC demo http://uima-ducc-demo.apache.o
> >> rg:42133/jobs.jsp :
> >>- Jobs, Services, Reservations running : OK
> >>- WS
> >>   - Jobs + Details: OK
> >>   - Reservations + Details : OK
> >>   - Services + Details : OK
> >>   - System Administration, Broker, Classes, Daemons, Machines : OK
> >>   * System DuccBook : OK
> >>   - System Viz : OK
> >>
> >> > Spot check LICENSE file : OK
> >>- note typo:
> >>   (webserver>navigation
> >>
> >> > Check README file : OK
> >>
> >> > Spot check NOTICE file: OK
> >>- line 225 Apache Tomcat is used?
> >>
> >> > Check ReleaseNotes.html : OK
> >>
> >> > Spot checked DUCC Book: OK
> >>- 19.4-6 are "To be filled in."
> >>- system-events.log not documented?
> >>
> >> Vote on RC4 = +1
> >>
> >> Lou.
> >>
> >> On Wed, Mar 14, 2018 at 3:01 PM, Jerry Cwiklik 
> >> wrote:
> >>
> >> > Hi,
> >> > the UIMA-DUCC 2.2.2 release candidate 4 is ready for voting.
> >> >
> >> > This version contains the following fixes since RC3:
> >> >
> >> > - Fixed Agent to support long user names (up to 32 chars) when
> >> collecting
> >> > node processes
> >> >
> >> > The list of changes in Jira:
> >> > https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%
> >> > 202.2.2-Ducc%20AND%20project%20%3D%20UIMA
> >> >
> >> > The source and binary zip/tars are staged to
> >> > https://dist.apache.org/repos/dist/dev/uima/uima-ducc/2.2.2/RC4
> >> >
> >> > The Maven artifacts are here:
> >> > https://repository.apache.org/content/repositories/orgapacheuima-1190
> >> >
> >> > The SVN tags are here:
> >> > http://svn.apache.org/repos/asf/uima/uima-ducc/tags/uima-ducc-2.2.2/
> >> >
> >> > See http://uima.apache.org/testing-builds.html for suggestions on how
> >> to
> >> > test release candidates.
> >> >
> >> > Please vote on release:
> >> >
> >> > [ ] +1 OK to release
> >> > [ ] 0   Don't care
> >> > [ ] -1 Not OK to release, because ...
> >> >
> >> > Thanks
> >> >
> >> > Jerry Cwiklik
> >> > Apache UIMA
> >> >
> >> > --
> >> > Jerry Cwiklik
> >> > Apache UIMA
> >> >
> >> >
> >>
> >
> >
>

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

[Burn Lewis (JIRA)]

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: Bug
  Components: DUCC
Reporter: Burn Lewis
 Fix For: 2.2.2-Ducc


Any JPs after first get:

Mar 12, 2018 3:38:19 PM 
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl 
notifyOnInitializationFailure

WARNING: Top Level Controller Initialization Exception.

javax.jms.InvalidClientIDException: Broker: localhost - Client: ClientListener 
already connected from tcp://192.168.3.13:46402

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] UIMA-DUCC 2.2.2 RC3

[Burn Lewis]

+ 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 notes, issues fixed, licenses &
notices

[X] +1 OK to release

On Wed, Mar 7, 2018 at 10:51 AM, Jaroslaw Cwiklik 
wrote:

>  - Spot checked signatures - OK
> - Built from source - OK
> - Issues Fixed report - OK
> - Spot checked duccbook - OK
> - Spot checked README, RELEASE_NOTES, NOTICE, LICENSE - OK
> - Spot checked links in duccmon - OK
> - Spot checked javadocs API - OK
> - Ran 1.job, 1.dd.job, 1.error.job - OK
> - Ran 1.job with --wait_for_completion - OK
>
> [X] +1 OK to release
>
> Jerry Cwiklik
>
> On Thu, Mar 1, 2018 at 3:04 PM, Jerry Cwiklik  wrote:
>
> > Hi,
> >
> > the UIMA-DUCC 2.2.2 release candidate 3 is ready for voting.
> >
> > This version contains the following fixes since RC2:
> >
> > - DUCC Web Server (WS) logs queries to DB too verbosely
> > - DUCC may restart failing custom services forever
> > - check_ducc & start_ducc problem when Banner is enabled in sshd_config
> > - fixed typo in README
> >
> > The list of changes in Jira:
> > https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%
> > 202.2.2-Ducc%20AND%20project%20%3D%20UIMA
> >
> > The source and binary zip/tars are staged to
> > https://dist.apache.org/repos/dist/dev/uima/uima-ducc/2.2.2/RC3
> >
> > The Maven artifacts are here:
> > https://repository.apache.org/content/repositories/orgapacheuima-1189
> >
> > The SVN tags are here:
> > http://svn.apache.org/repos/asf/uima/uima-ducc/tags/uima-ducc-2.2.2/
> >
> > See http://uima.apache.org/testing-builds.html for suggestions on how to
> > test release candidates.
> >
> > Please vote on release:
> >
> > [ ] +1 OK to release
> > [ ] 0   Don't care
> > [ ] -1 Not OK to release, because ...
> >
> > Thanks
> >
> > Jerry Cwiklik
> > Apache UIMA
> >
>

Re: [VOTE] uimaj-3.0.0 rc4

[Burn Lewis]

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 signatures: OK
 - tested source build with simple annotators: OK

[X] +1 OK to release


On Thu, Mar 1, 2018 at 8:38 AM, Marshall Schor  wrote:

> need 1 more vote?
>
> -M
>
>
> On 2/5/2018 4:28 PM, Marshall Schor wrote:
> > Hi,
> >
> > Here's rc4 of uimaj 3.0.0 sdk.
> >
> > The change since rc3: some fixes to the logging APIs to avoid "double
> scanning"
> > of substitution when using logrb style calls, some formatting of the
> messages
> > fixes for logging, and some caching added for internationalization of
> messages
> > using message bundles.
> >
> > -
> >
> > (Copied from previous vote msg):
> >
> > The change since rc2
> >   - fix for the class path in the uimaj examples eclipse project, to
> correspond
> > to the upgrades done for slf4j and jackson-core.
> >
> > Change since rc1:
> >   - bug when JCas range is unknown
> >   - exception thrown unnecessarily, making Component Descriptor Editor
> (CDE)
> > fail on bad JCas classes
> >   - changed CDE to bypass loading user-defined JCas classes.
> >
> > Changes since the beta are mainly 2 (plus some bug fixes):
> >   1) support for serialization / deserialization and subsequent access
> using
> > LowLeveCAS.getFSFromRef(int) API.
> >   2) support for applications which have JCas class classes, and load
> multiple
> > type systems (under the same class loader) with some of these having
> subsets of
> > the features.
> >
> > Also, added 2 more semi-built-in types: one is a variant of the
> FSHashSet, using
> > linked Hash Set, so iterating gives a reasonable order. The other is a
> general
> > map from ints to Feature Structures, intended to let users eventually
> replace
> > use of the LowLevelCAS API method referenced above.
> > ---
> >
> > The Jiras for this release are here:
> >
> > https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%2012310570%20AND%20fixVersion%20%3D%2012341578%20ORDER%20BY%20priority%
> 20DESC%2C%20key%20ASC
> >
> > Maven artifacts:
> > https://repository.apache.org/content/repositories/orgapacheuima-1183/
> >
> > Source and binary zip/tar staged to:
> > https://dist.apache.org/repos/dist/dev/uima/uimaj/3.0.0-rc4/artifacts/
> >
> > Eclipse update subsite:
> > https://dist.apache.org/repos/dist/dev/uima/uimaj/3.0.0-rc4/uimaj-uv3
> >
> > SVN tag: https://svn.apache.org/repos/asf/uima/uv3/uimaj-v3/tags/
> uimaj-3.0.0/
> >
> > Please vote on release:
> >
> > [ ] +1 OK to release
> > [ ] 0 Don't care
> > [ ] -1 Not OK to release, because ...
> >
> > Thanks.
> >
> > -Marshall
> >
> >
>
>

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

[Burn Lewis (JIRA)]

 [ 
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 not 
allowed to accumulate.  Service will now be disabled (no more instances 
restarted) if too many init or runtime errors occur.  By default runtime errors 
must not exceed 5 during a window of 30 mins, but these thresholds can be 
overridden by a custom pinger.

> DUCC may restart failing custom services forever
> 
>
> Key: UIMA-5390
> URL: https://issues.apache.org/jira/browse/UIMA-5390
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>Priority: Minor
> Fix For: 2.2.2-Ducc
>
>
> Since custom services have no initialization phase all init errors are 
> counted as run errors, but before the threshold is reached the error count 
> may be reset.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 forever
> 
>
> Key: UIMA-5390
> URL: https://issues.apache.org/jira/browse/UIMA-5390
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Minor
> Fix For: 2.2.2-Ducc
>
>
> Since custom services have no initialization phase all init errors are 
> counted as run errors, but before the threshold is reached the error count 
> may be reset.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 starting another instance.  

> DUCC may restart failing custom services forever
> 
>
> Key: UIMA-5390
> URL: https://issues.apache.org/jira/browse/UIMA-5390
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>Priority: Minor
> Fix For: 2.2.2-Ducc
>
>
> Since custom services have no initialization phase all init errors are 
> counted as run errors, but before the threshold is reached the error count 
> may be reset.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] UIMA-DUCC 2.2.2 RC1

[Burn Lewis]

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 
wrote:

> Installed on Apache-DUCC.  Get the following in the job submission script:
>
> id:5 location:26530@uima-ducc-vm2
> ERROR: java.lang.NoSuchMethodException: fromJson
>
> java.lang.NoSuchMethodException: fromJson
> at
> org.apache.uima.ducc.transport.dispatcher.ClassManager.invoke(
> ClassManager.java:275)
> at
> org.apache.uima.ducc.transport.dispatcher.DuccEventHttpDispatcherCl.
> fromJson(DuccEventHttpDispatcherCl.java:110)
> at
> org.apache.uima.ducc.transport.dispatcher.DuccEventHttpDispatcherCl.
> dispatchJson(DuccEventHttpDispatcherCl.java:119)
> at
> org.apache.uima.ducc.cli.DuccMonitor.runInternal(DuccMonitor.java:361)
> at org.apache.uima.ducc.cli.DuccMonitor.run(DuccMonitor.java:578)
> at
> org.apache.uima.ducc.cli.MonitorListener.run(MonitorListener.java:87)
> at java.lang.Thread.run(Thread.java:745)
>
> [X ] -1 Not OK to release
>
> Lou.
>
> On Tue, Feb 20, 2018 at 10:45 AM, Jerry Cwiklik 
> wrote:
>
> > - Spot checked signatures - OK
> >
> > - Compared DUCC source with SVN tag - OK
> >
> > - Built from source - OK
> >
> > - Issues Fixed report - OK
> >
> > - Spot checked duccbook - OK
> >
> > - Spot checked README, RELEASE_NOTES, NOTICE, LICENSE - OK
> >
> > - Spot checked links in duccmon - OK
> >
> > - Spot checked javadocs API - OK
> >
> > - Ran 1.job, 1.dd.job, 1.error.job, deployed test service - OK
> >
> >
> > [X] +1 OK to release
> >
> > Jerry
> >
> >
> > On 2/19/2018 1:22 PM, Jerry Cwiklik wrote:
> >
> >> Hi,
> >>
> >> the UIMA-DUCC 2.2.2 release candidate 1 is ready for voting.
> >>
> >> This version contains the following fixes:
> >> -Upgraded UIMA (2.10.2), UIMA-AS (2.10.2), ActiveMQ (5.15.2), Spring
> >> Framework (4.3.9), Camel (2.19.3), XStream (1.4.10)
> >> -Requires java 8 for builds and runtime
> >> -Fixed rogue process detector to prevent truncation of user names
> >> -Reduced size of publications between the PM and Agents
> >> -Improved Agent's detection of defunct processes
> >> -Improved logging of system events
> >> -ducc_watcher improvements
> >> -Job & managed reservation specs now saved in DB
> >> -DUCC Web Server (WS) queries DB too often
> >> -DUCC Web Server (WS) should use Resource Manager (RM) calculated value
> >> for machine's memory available
> >>
> >>
> >> The list of changes in Jira:
> >> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%
> >> 202.2.2-Ducc%20AND%20project%20%3D%20UIMA
> >>
> >> The source and binary zip/tars are staged to
> >> https://dist.apache.org/repos/dist/dev/uima/uima-ducc/2.2.2/RC1/
> >>
> >> The Maven artifacts are here:
> >> https://repository.apache.org/content/repositories/orgapacheuima-1186
> >>
> >> The SVN tags are here:
> >> http://svn.apache.org/repos/asf/uima/uima-ducc/tags/uima-ducc-2.2.2/
> >>
> >> See http://uima.apache.org/testing-builds.html for suggestions on how
> to
> >> test release candidates.
> >>
> >> Please vote on release:
> >>
> >> [ ] +1 OK to release
> >> [ ] 0   Don't care
> >> [ ] -1 Not OK to release, because ...
> >>
> >> Thanks
> >>
> >>
> > --
> > Jerry Cwiklik
> > Apache UIMA
> >
> >
>

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

[Burn Lewis]

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) 
wrote:

>
>  [ https://issues.apache.org/jira/browse/UIMA-5728?page=
> com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jerry Cwiklik closed UIMA-5728.
> ---
> Resolution: Fixed
>
> ready for RC1
>
>
>
> > UIMA-DUCC: prepare for v.2.2.2 release
> > --
> >
> > Key: UIMA-5728
> > URL: https://issues.apache.org/jira/browse/UIMA-5728
> > Project: UIMA
> >  Issue Type: Task
> >  Components: DUCC
> >Reporter: Jerry Cwiklik
> >Assignee: Jerry Cwiklik
> >Priority: Major
> > Fix For: 2.2.2-Ducc
> >
> >
> > Review and update README, RELEASE_NOTES, NOTICE, LICENSE
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>

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

[Burn Lewis (JIRA)]

 [ 
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_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 Type: Bug
>  Components: DUCC
>Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: future-DUCC
>
>
> It should check that the compiled ducc-id is correct



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 shutdown
> --
>
> Key: UIMA-5732
> URL: https://issues.apache.org/jira/browse/UIMA-5732
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Minor
> Fix For: 2.2.2-Ducc
>
>
> stop() should shutdown the Camel routes and cleanup MBeans etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 JobProcessComponent:stop before stopping Camel.  It looks as if that stop 
is called twice but appears safe.  Calling super.stop got an NPE

> 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 Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Minor
> Fix For: 2.2.2-Ducc
>
>
> stop() should shutdown the Camel routes and cleanup MBeans etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

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 Type: Bug
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: 2.2.2-Ducc


stop() should shutdown the Camel routes and cleanup MBeans etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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_arguments
> ---
>
> Key: UIMA-3918
> URL: https://issues.apache.org/jira/browse/UIMA-3918
> Project: UIMA
>  Issue Type: Improvement
>  Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Major
> Fix For: future-DUCC
>
>
> This would allow for customization of driver_exception_handler w/o the need 
> for user supplied replacement class (e.g. parameterization of the default 
> exception handler supplied by DUCC).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 provide 
> driver_exception_handler_arguments
> ---
>
> Key: UIMA-3918
> URL: https://issues.apache.org/jira/browse/UIMA-3918
> Project: UIMA
>  Issue Type: Improvement
>  Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Major
> Fix For: future-DUCC
>
>
> This would allow for customization of driver_exception_handler w/o the need 
> for user supplied replacement class (e.g. parameterization of the default 
> exception handler supplied by DUCC).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 Java
> --
>
> Key: UIMA-4727
> URL: https://issues.apache.org/jira/browse/UIMA-4727
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Major
> Fix For: future-DUCC
>
>
> Crashes were infrequent but are reliable with latest JVM.
> For fix see https://issues.apache.org/jira/browse/KAFKA-2421
> Upgrade LZ4 to version 1.3 to avoid crashing with IBM Java 7.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 re-registration of DUCC services to reduce chance  of duplicate 
> services
> --
>
> Key: UIMA-5246
> URL: https://issues.apache.org/jira/browse/UIMA-5246
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Major
> Fix For: future-DUCC
>
>
> After an unregister + register ducc-mon has sometimes shown 2 service with 
> the same endpoint.  Apparently the older unregistered one was not marked as 
> "archived" in the DB.  Currently new instances of the service may be created 
> before all of the old ones have been removed - would be better if the old 
> service is completely removed before the new instances created.
> Should also handle failures to update the DB.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 
> services
> --
>
> Key: UIMA-5246
> URL: https://issues.apache.org/jira/browse/UIMA-5246
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Major
> Fix For: future-DUCC
>
>
> After an unregister + register ducc-mon has sometimes shown 2 service with 
> the same endpoint.  Apparently the older unregistered one was not marked as 
> "archived" in the DB.  Currently new instances of the service may be created 
> before all of the old ones have been removed - would be better if the old 
> service is completely removed before the new instances created.
> Should also handle failures to update the DB.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 the registry and the name to look up.  Moved the registration of a 
service driver out of DuccServiceDriver for more flexibility. Dropped the 
ConfigurationProperties class.

> Add registry support so pull services can locate their server
> -
>
> Key: UIMA-5551
> URL: https://issues.apache.org/jira/browse/UIMA-5551
> Project: UIMA
>  Issue Type: New Feature
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> Optionally allow pull services to use a registry to locate resources such as 
> their server and other services such as a database.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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

> Add registry support so pull services can locate their server
> -
>
> Key: UIMA-5551
> URL: https://issues.apache.org/jira/browse/UIMA-5551
> Project: UIMA
>  Issue Type: New Feature
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> Optionally allow pull services to use a registry to locate resources such as 
> their server and other services such as a database.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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=ducc
> --
>
> Key: UIMA-5678
> URL: https://issues.apache.org/jira/browse/UIMA-5678
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> The environment of a service process should have USER set to the owner of the 
> service.  Perhaps the expansion of USER to USER=$USER should be done when a 
> service is registered, not when the process is started by the SM



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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" will be used
> 
>
> Key: UIMA-5649
> URL: https://issues.apache.org/jira/browse/UIMA-5649
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: 2.2.2-Ducc
>
>
> With UIMA-5405 the new ducc.uid property is added by ducc_post_install but 
> the migration script doesn't add it, and the default of "ducc" may be wrong.  
> Instead we can assume the ducc.uid is the userid that installed ducc



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 but the service spec has the 
correct setting for USER in the --environment option

> 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 Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> The environment of a service process should have USER set to the owner of the 
> service.  Perhaps the expansion of USER to USER=$USER should be done when a 
> service is registered, not when the process is started by the SM



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 process when a work-item 
> fails
> ---
>
> Key: UIMA-5700
> URL: https://issues.apache.org/jira/browse/UIMA-5700
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>Assignee: Jerry Cwiklik
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> Needed for an in-process pull service to prevent it from destroying 
> everything.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Burn Lewis (JIRA)]

 [ 
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 
> fails
> ---
>
> Key: UIMA-5700
> URL: https://issues.apache.org/jira/browse/UIMA-5700
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
>Assignee: Jerry Cwiklik
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> Needed for an in-process pull service to prevent it from destroying 
> everything.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] UIMA-AS 2.10.2 RC6

[Burn Lewis]

- 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 the service was deployed with the default id --- not a blocker
- Ran a large pipeline with both builds - OK
- Issues fixed - OK
- Spot checked uima-as docs - OK
- Spot checked README, etc - OK

[X] +1 OK to release

On Wed, Jan 31, 2018 at 11:34 AM, Marshall Schor  wrote:

> signatures OK
> compare svn tag with source release: OK
> build from source OK
> Install into Eclipse 4.7.0, create deployment descriptor OK
> issues fixed: OK
>
> README: line 472 http link incorrect - goes to 1 specific issue.
>   - Not a blocker I think.
> README: line 39 says Fixed dd2spring issues, but searching the issues for
> "dd2spring" in Jira returns empty result?
>   - Not a blocker I think.
> README.uimaj.txt has a link to issues fixed, which goes (of course!) to the
> uima-as issues fixed.
>   - Not a blocker I think.
>
> License / notice : no change from rc2
>
> ran quick-start tests OK (but broker window reported at end 2 messages of
> Transport Connection to: tcp://127.0.0.1:65064 failed:
> java.net.SocketException:
> Connection reset - which is expected.
>
> [X] +1 OK to release
>
> -Marshall Schor
>
>

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

[Burn Lewis (JIRA)]

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: UIMA
  Issue Type: Bug
  Components: DUCC
Reporter: Burn Lewis
Assignee: Jerry Cwiklik
 Fix For: 2.2.2-Ducc


Needed for an in-process pull service to prevent it from destroying everything.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] UIMA-AS 2.10.2 RC5

[Burn Lewis]

- 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) -TargetServiceId option on
RunRemoteAsyncAE does not send a targeted CAS.

[ ] +1 OK to release

~Burn

On Tue, Jan 2, 2018 at 11:21 AM, Jaroslaw Cwiklik 
wrote:

> "Many other" = "all services " were kaput? If so, it could be the broker
> failure (what version?) or something else. Sorry cant pinpoint this stuff
> with accuracy since the broken connection can be symptom of many problems.
> Is this system in the kaput state still?
>
> Jerry
>
> On Tue, Jan 2, 2018 at 11:16 AM, Eddie Epstein 
> wrote:
>
> > There were no long GCs for this service. Note (from above) that many
> other
> > services running older versions of uima-as were also showing the same
> > behavior.
> >
> > Eddie
> >
> > On Tue, Jan 2, 2018 at 9:21 AM, Jaroslaw Cwiklik 
> > wrote:
> >
> > > Looks like the client lost connection to the broker for some reason.
> Long
> > > GC perhaps? But eventually the service should have recovered. Any
> > > indication of connection
> > > recovery later?
> > >
> > > Jerry
> > >
> > > On Sun, Dec 24, 2017 at 11:34 AM, Eddie Epstein 
> > > wrote:
> > >
> > > > Jerry,
> > > >
> > > > Testing a real analytic running 28 sync pipelines as a DUCC managed
> > > UIMA-AS
> > > > service, the DUCC pinger is reporting failures for an idle service 2
> > or 3
> > > > times a day.
> > > >
> > > > sm.log, an error surrounded by good pings, the ping normally done
> > every 2
> > > > minutes:
> > > >
> > > > Dec 2017 07:49:42,740  INFO SM.PingDriver - 10668 T[3588945]
> > > > handleStatistics  Ping ok:  UIMA-AS:eae-r1.16:tcp://broker1:61616
> > > > Alive[true] Healthy[true] + Info: QDEPTH[0] AveNQ[0] Consum[3]
> Prod[1]
> > > > minNQ[0] maxNQ[0] expCnt[0] inFlt[0] DQ[1] NQ[1] NDisp[1]
> > > > MetaNode[192.168.7.101] MetaPid[71061:91]
> > > > Dec 2017 07:51:42,844  INFO SM.PingDriver - 10668 T[3588945]
> > > > handleStatistics  Ping ok:  UIMA-AS:eae-r1.16:tcp://broker1:61616
> > > > Alive[true] Healthy[true] + Info: QDEPTH[0] AveNQ[0] Consum[3]
> Prod[1]
> > > > minNQ[0] maxNQ[0] expCnt[0] inFlt[0] DQ[1] NQ[1] NDisp[1]
> > > > MetaNode[192.168.7.101] MetaPid[71061:91]
> > > > Dec 2017 07:54:02,912 ERROR SM.PingDriver - 10668 T[3588945]
> > > > handleStatistics  Missed_pings  1 endpoint
> > > > UIMA-AS:eae-r1.16:tcp://broker1:61616 Alive[false] Healthy[false] +
> > > Info:
> > > > QDEPTH[0] AveNQ[0] Consum[3] Prod[1] minNQ[0] maxNQ[0] expCnt[0]
> > inFlt[0]
> > > > DQ[1] NQ[1] NDisp[1] MetaNode[N/A] MetaPid[N/A]: Cannot issue getMeta
> > to:
> > > > eae-r1.16:tcp://broker1:61616: java.util.concurrent.TimeoutException
> > > > Dec 2017 07:56:03,016  INFO SM.PingDriver - 10668 T[3588945]
> > > > handleStatistics  Ping ok:  UIMA-AS:eae-r1.16:tcp://broker1:61616
> > > > Alive[true] Healthy[true] + Info: QDEPTH[0] AveNQ[89570] Consum[3]
> > > Prod[1]
> > > > minNQ[89570] maxNQ[89570] expCnt[0] inFlt[0] DQ[1] NQ[1] NDisp[1]
> > > > MetaNode[192.168.7.101] MetaPid[71061:91]
> > > >
> > > > The broker logfile, complaining about all three service listeners
> > around
> > > > the same time (the service runs on 192.168.7.101):
> > > >
> > > > 2017-12-24 07:54:48,257 [yMonitor Worker] WARN  Transport
> > > > - Transport Connection to: tcp://192.168.7.101:43895 failed:
> > > > org.apache.activemq.transport.InactivityIOException: Channel was
> > > inactive
> > > > for too (>3) long: tcp://192.168.7.101:43895
> > > > 2017-12-24 07:54:48,287 [yMonitor Worker] WARN  Transport
> > > > - Transport Connection to: tcp://192.168.7.101:43898 failed:
> > > > org.apache.activemq.transport.InactivityIOException: Channel was
> > > inactive
> > > > for too (>3) long: tcp://192.168.7.101:43898
> > > > 2017-12-24 07:54:48,288 [yMonitor Worker] WARN  Transport
> > > > - Transport Connection to: tcp://192.168.7.101:43899 failed:
> > > > org.apache.activemq.transport.InactivityIOException: Channel was
> > > inactive
> > > > for too (>3) long: tcp://192.168.7.101:43899
> > > >
> > > > The service logfile also reporting problems for all three listeners:
> > > >
> > > > 07:55:12.457 - 91:
> > > > org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
> > > > ainer.onException:
> > > > WARNING: Service: Processing2 Runtime Exception
> > > > 07:55:12.457 - 91:
> > > > org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
> > > > ainer.onException:
> > > > WARNING: Jms Listener Failed. Endpoint: eae-r1.16 Managed By:
> > > > tcp://broker1:61616 Reason: javax.jms.JMSException:
> > java.io.EOFException
> > > > 07:55:12.457 - 91:
> > > > org.apache.uima.adapter.jms.activemq.UimaDefaultMessageListenerCont
> > > ainer.
> > > > 

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

[Burn Lewis (JIRA)]

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 Type: Bug
  Components: DUCC
Reporter: Burn Lewis
 Fix For: 2.2.2-Ducc


The environment of a service process should have USER set to the owner of the 
service.  Perhaps the expansion of USER to USER=$USER should be done when a 
service is registered, not when the process is started by the SM



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: UIMA-AS Client API Change Discussion

[Burn Lewis]

I would vote against deprecating existing methods.
I think the issue is do we expect to add more arguments in the future if
another variant is needed.
If not then adding 2 new methods is consistent with past extensions ... but
I do see a 3rd sendAndReceiveCAS method that is not in the Javadocs.
Alternatively Lou's 1 new method would provide for future extensions.  The
2nd arg could be a map, just as the initialize method takes a map:

   String sendCAS ( CAS cas, Map options )

Burn


On Tue, Dec 12, 2017 at 10:33 AM, Marshall Schor <m...@schor.com> wrote:

> Re: 2nd & 3rd proposal, the client would supply an instance of
> "ProcessingOptions".  I assume the user would create this using new
> ProcessingOptions() and then call the setters it wants.  Or perhaps there
> would
> be a short-hand positional-arg constructor, as well.
>
> Overall, it seems to me that it would be less disruptive to the API
> stability,
> and easier for users to learn and use, to just add an overloaded call
> (proposal
> #1), and not deprecate anything.   I think users would appreciate not
> having to
> update older code.
>
> -Marshall
>
> On 12/11/2017 5:42 PM, Jaroslaw Cwiklik wrote:
> > Hi, I need to extend UIMA-AS client API as defined by
> > interface UimaAsynchronousEngine.java
> >
> > The new feature I've been working on, should allow a client to send a CAS
> > to a specific instance of a service. Such targeting is optional and could
> > be useful to test if a service is viable (processing can be done).
> >
> > To support targeting, a service uses a JMS selector which expects a
> message
> > property that uniquely identifies the service. By default, the selector
> > uses  IP:PID as a unique identifier, but a service deployer can define a
> > custom identifier using -D property on the  service command line.
> >
> > An application client must be able to invoke a UIMA-AS client method
> which
> > takes a CAS, unique id of a service to target, and other properties. The
> > targeting is again optional and used for special use cases.
> >
> > Current UIMA-AS client uses two styles of calls: asynchronous and
> > synchronous
> >
> > sendCAS(CAS cas) - this is an asynchronous style
> >
> > and there are two APIs for synchronous style:
> >
> > sendAndReceive(CAS cas)
> > sendAndReceiveCAS(CAS cas, List
> > componentMetricsList)
> >
> > To support targeting, I can overload the above creating two new methods
> >
> > sendCAS(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);
> >
> > where
> >
> > ProcessingOptions() {
> >   void setAsynchronous();  // if this is not called the default is
> > synchronous
> >   void setMetrics(List list);  //null
> for
> > asynchronous style
> >   void setTargetInstance(String id);  // if not called ,targeting is not
> > done
> > }
> >
> > Burn Lewis commented on this proposal with:
> >
> > "Has the advantage of being extendable without having to add another send
> > method.
> >
> > Could be a map with a specified set of legal keys but a special class is
> > good too ... especially if had extra constructors, e.g. for a targeted
> > async request:
> >
> > submit ( cas, new ProcessingOptions(true, null, "127.0.0.1:12345") )"
> >
> > If submit() is a preferred choice should the sendCAS() and
> sendAndReceive()
> > be deprecated to encourage new code to use more flexible API? Or should
> we
> > just document that submit() is only
> > for targeting services?
> >
> > Are there any suggestions perhaps which should be considered?
> >
> > Jerry
> >
>
>

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

[Burn Lewis (JIRA)]

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 Type: Bug
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
Priority: Minor
 Fix For: 2.2.2-Ducc


It should check that the compiled ducc-id is correct



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

 [ 
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

> 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/UIMA-5649
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Burn Lewis
>Assignee: Burn Lewis
>Priority: Minor
> Fix For: 2.2.2-Ducc
>
>
> With UIMA-5405 the new ducc.uid property is added by ducc_post_install but 
> the migration script doesn't add it, and the default of "ducc" may be wrong.  
> Instead we can assume the ducc.uid is the userid that installed ducc



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

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/UIMA-5649
 Project: UIMA
  Issue Type: Bug
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
Priority: Minor
 Fix For: 2.2.2-Ducc


With UIMA-5405 the new ducc.uid property is added by ducc_post_install but the 
migration script doesn't add it, and the default of "ducc" may be wrong.  
Instead we can assume the ducc.uid is the userid that installed ducc



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis]

- 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 "UIMA V2 operation not
supported in V3" ... perhaps it should refer to a section in the docs about
changes to internal classes and suggested alternatives.

 - migration of a large set of projects is painful -
When sourcesRoots contains multiple projects the converted classes are put
in the same folder making it difficult to copy them to the appropriate
project.  Perhaps an in-place option could be supported which could be used
after verifying that an earlier migration has succeeded,  or by relying on
a source control system to undo any unwanted changes.  This option could
also delete the obsolete xxx_Type classes.
Also the migrated source should include a comment recording the migration,
and should retain comments such as. copyright headers.
Would it help to suggest re-running jcasgen instead of converting the jcas
classes?

Burn




On Tue, Nov 7, 2017 at 12:25 PM, Jaroslaw Cwiklik 
wrote:

> working on it now ... will vote this afternoon
>
> -Jerry
>
> On Tue, Nov 7, 2017 at 8:42 AM, Marshall Schor  wrote:
>
> > gentle reminder ... one more vote needed ...  -Marshall
> >
> >
> > On 11/2/2017 10:15 AM, Marshall Schor wrote:
> > > Hi everyone,
> > >
> > > Here's rc8 for uimaj 3.0.0-beta.
> > >
> > > The changes since rc7 include some xml constants fixups to not depend
> on
> > java
> > > classes that may not be present in various versions of Java.
> > >
> > > Also included are general improvements in adding generic typing to many
> > UIMA
> > > structures, updates to add missing javadocs, missing APIs in the jcas
> > interface
> > > for getting "empty" lists, and some upgrades to the main documentation
> > and
> > > examples to better reflect v3 idioms.
> > >
> > > The updates to generic typing are designed to not break existing code,
> > and it
> > > seems to be OK as far as I was able to test; it would be great if you
> > could test
> > > this against other big projects (like dk-pro) to see if anything got
> > missed.
> > >
> > > Here are the Jiras:
> > >
> > > https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%2012310570%20AND%20fixVersion%20%3D%2012339590%
> > 20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
> > >
> > > Maven artifacts:
> > > https://repository.apache.org/content/repositories/orgapacheuima-1165/
> > >
> > > Source and binary zip/tar staged to:
> > > https://dist.apache.org/repos/dist/dev/uima/uimaj/3.0.0-
> > beta-rc8/artifacts/
> > >
> > > Eclipse update subsite:
> > > https://dist.apache.org/repos/dist/dev/uima/uimaj/3.0.0-
> > beta-rc8/uimaj-v3-pre-production/
> > >
> > > SVN tag: https://svn.apache.org/repos/asf/uima/uv3/uimaj-v3/tags/
> > uimaj-3.0.0-beta/
> > >
> > > Please vote on release:
> > >
> > > [ ] +1 OK to release
> > > [ ] 0 Don't care
> > > [ ] -1 Not OK to release, because ...
> > >
> > > Thanks.
> > >
> > > -Marshall
> > >
> > >
> >
> >
>

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

[Burn Lewis (JIRA)]

 [ 
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 be 
implemented by the subclass:  getLastSerializedError & useThreadAffinity.

> 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
>  Components: DUCC
>    Reporter: Burn Lewis
>Assignee: Burn Lewis
> Fix For: 2.2.2-Ducc
>
>
> HttpWorkerThread gets class not found for getLastSerializedError as it is 
> protected in DuccAbstractProcessContainer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: 2.2.2-Ducc


HttpWorkerThread gets class not found for getLastSerializedError as it is 
protected in DuccAbstractProcessContainer



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] uimaj-2.10.2 rc2

[Burn Lewis]

   - 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,
>
> uimaj-2.10.2 rc2 is posted and ready for voting.
>
> There were four minor changes:
> 1) A json support jar from the uima binary distribution was added to the
> example eclipse project "classpath"
> 2) The example eclipse project's classpath definition of where the
> Javadocs was corrected - the javadocs should now be available.
> 3) The xml support was made more independent of particular Java version
> levels.
> 4) A test case which depended on the internals of Java string
> implementation was commented out - it would work on some Java
> implementations, and fail on others.
>
>
> The issues fixed are here:
> https://issues.apache.org/jira/projects/UIMA/versions/12341420
>
> The source and binary tar/zips are here:
> https://dist.apache.org/repos/dist/dev/uima/uimaj/2.10.2-rc2/artifacts/
>
> The eclipse update subsite is here:
> https://dist.apache.org/repos/dist/dev/uima/uimaj/2.10.2-rc2/uimaj/
>
> The maven staging repo is here:
> https://repository.apache.org/content/repositories/orgapacheuima-1164/
>
> SVN tag: https://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.10.2/
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0   Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> -Marshall
>
>

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

[Burn Lewis]

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/UIMA-5605?page=
> com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Burn Lewis reassigned UIMA-5605:
> ----
>
> Assignee: Burn Lewis
>
> > DUCC scheduler ArrayIndexOutOfBoundsException
> > -
> >
> > Key: UIMA-5605
> > URL: https://issues.apache.org/jira/browse/UIMA-5605
> > Project: UIMA
> >  Issue Type: Bug
> >  Components: DUCC
> >Affects Versions: 2.2.1-Ducc
> >Reporter: Jörg Waitelonis
> >Assignee: Burn Lewis
> > Fix For: 2.2.2-Ducc
> >
> >
> > The scheduler stops scheduling and ducc-mon indicates inresposive
> ResourceManager.
> > rm.log (Trace):
> > 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A
> detectFragmentation  Freed shares 246 on machine xxx.xxx.xx
> > 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A
> detectFragmentation  Update v before: NP[ --default-- ] v:   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0 0   0   0   0   0   0   0
> > 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > 05 Okt 2017 11:29:13,336 FATAL RM.ResourceManagerComponent- N/A
> runScheduler
> > java.lang.ArrayIndexOutOfBoundsException
> > An ArrayIndexOutOfBoundsException can occur in the NodepoolScheduler
> class at line 2422:
> > vmach_j[free]++;
> > Quickfix: comment it out. It seems only be used for logging (trace).
> >
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

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

[Burn Lewis (JIRA)]

 [ 
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 pull services can locate their server
> -
>
> Key: UIMA-5551
> URL: https://issues.apache.org/jira/browse/UIMA-5551
> Project: UIMA
>  Issue Type: New Feature
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
> Fix For: 2.2.2-Ducc
>
>
> Optionally allow pull services to use a registry to locate resources such as 
> their server and other services such as a database.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

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

Burn Lewis closed UIMA-5605.


> DUCC scheduler ArrayIndexOutOfBoundsException
> -
>
> Key: UIMA-5605
> URL: https://issues.apache.org/jira/browse/UIMA-5605
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 2.2.1-Ducc
>Reporter: Jörg Waitelonis
>Assignee: Burn Lewis
> Fix For: 2.2.2-Ducc
>
>
> The scheduler stops scheduling and ducc-mon indicates inresposive 
> ResourceManager.
> rm.log (Trace):
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Freed shares 246 on machine xxx.xxx.xx
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Update v before: NP[ --default-- ] v:   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0 0   0   0   0   0   0   0  
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0 
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0 
> 05 Okt 2017 11:29:13,336 FATAL RM.ResourceManagerComponent- N/A runScheduler 
> java.lang.ArrayIndexOutOfBoundsException
> An ArrayIndexOutOfBoundsException can occur in the NodepoolScheduler class at 
> line 2422:
> vmach_j[free]++;  
> Quickfix: comment it out. It seems only be used for logging (trace).
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

 [ 
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 likely to occur when using the default quantum of 1GB as small changes 
in memory used by "system" processes might change DUCC's count of available 
shares on the machine.

> DUCC scheduler ArrayIndexOutOfBoundsException
> -
>
> Key: UIMA-5605
> URL: https://issues.apache.org/jira/browse/UIMA-5605
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 2.2.1-Ducc
>Reporter: Jörg Waitelonis
> Fix For: 2.2.2-Ducc
>
>
> The scheduler stops scheduling and ducc-mon indicates inresposive 
> ResourceManager.
> rm.log (Trace):
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Freed shares 246 on machine xxx.xxx.xx
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Update v before: NP[ --default-- ] v:   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0 0   0   0   0   0   0   0  
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0 
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0 
> 05 Okt 2017 11:29:13,336 FATAL RM.ResourceManagerComponent- N/A runScheduler 
> java.lang.ArrayIndexOutOfBoundsException
> An ArrayIndexOutOfBoundsException can occur in the NodepoolScheduler class at 
> line 2422:
> vmach_j[free]++;  
> Quickfix: comment it out. It seems only be used for logging (trace).
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

 [ 
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 ArrayIndexOutOfBoundsException
> -
>
> Key: UIMA-5605
> URL: https://issues.apache.org/jira/browse/UIMA-5605
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 2.2.1-Ducc
>Reporter: Jörg Waitelonis
>Assignee: Burn Lewis
> Fix For: 2.2.2-Ducc
>
>
> The scheduler stops scheduling and ducc-mon indicates inresposive 
> ResourceManager.
> rm.log (Trace):
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Freed shares 246 on machine xxx.xxx.xx
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Update v before: NP[ --default-- ] v:   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0 0   0   0   0   0   0   0  
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0 
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0 
> 05 Okt 2017 11:29:13,336 FATAL RM.ResourceManagerComponent- N/A runScheduler 
> java.lang.ArrayIndexOutOfBoundsException
> An ArrayIndexOutOfBoundsException can occur in the NodepoolScheduler class at 
> line 2422:
> vmach_j[free]++;  
> Quickfix: comment it out. It seems only be used for logging (trace).
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

 [ 
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 scheduler ArrayIndexOutOfBoundsException
> -
>
> Key: UIMA-5605
> URL: https://issues.apache.org/jira/browse/UIMA-5605
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 2.2.1-Ducc
>Reporter: Jörg Waitelonis
> Fix For: 2.2.2-Ducc
>
>
> The scheduler stops scheduling and ducc-mon indicates inresposive 
> ResourceManager.
> rm.log (Trace):
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Freed shares 246 on machine xxx.xxx.xx
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Update v before: NP[ --default-- ] v:   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0 0   0   0   0   0   0   0  
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0 
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0 
> 05 Okt 2017 11:29:13,336 FATAL RM.ResourceManagerComponent- N/A runScheduler 
> java.lang.ArrayIndexOutOfBoundsException
> An ArrayIndexOutOfBoundsException can occur in the NodepoolScheduler class at 
> line 2422:
> vmach_j[free]++;  
> Quickfix: comment it out. It seems only be used for logging (trace).
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

 [ 
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 ArrayIndexOutOfBounds
> ---
>
> Key: UIMA-5606
> URL: https://issues.apache.org/jira/browse/UIMA-5606
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
> Fix For: 2.2.2-Ducc
>
>
> 05 Oct 2017 09:51:13,701 FATAL RM.ResourceManagerComponent- N/A runScheduler 
> java.lang.ArrayIndexOutOfBoundsException
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.detectFragmentation(NodepoolScheduler.java:2422)
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.insureFullEviction(NodepoolScheduler.java:2509)
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.schedule(NodepoolScheduler.java:2678)
>   at 
> org.apache.uima.ducc.rm.scheduler.Scheduler.schedule(Scheduler.java:1072)
>   at 
> org.apache.uima.ducc.rm.ResourceManagerComponent.runScheduler(ResourceManagerComponent.java:304)
>   at 
> org.apache.uima.ducc.rm.ResourceManagerComponent.run(ResourceManagerComponent.java:279)
>   at java.lang.Thread.run(Thread.java:809)
> NodepoolScheduler 2422:
>  vmach_j[free]++; // This is the largest potential 
> share that can be made on this machine,
> This code appears to be only used to produce trace level messages



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

 [ 
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 crashed with ArrayIndexOutOfBounds
> ---
>
> Key: UIMA-5606
> URL: https://issues.apache.org/jira/browse/UIMA-5606
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
> Fix For: 2.2.2-Ducc
>
>
> 05 Oct 2017 09:51:13,701 FATAL RM.ResourceManagerComponent- N/A runScheduler 
> java.lang.ArrayIndexOutOfBoundsException
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.detectFragmentation(NodepoolScheduler.java:2422)
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.insureFullEviction(NodepoolScheduler.java:2509)
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.schedule(NodepoolScheduler.java:2678)
>   at 
> org.apache.uima.ducc.rm.scheduler.Scheduler.schedule(Scheduler.java:1072)
>   at 
> org.apache.uima.ducc.rm.ResourceManagerComponent.runScheduler(ResourceManagerComponent.java:304)
>   at 
> org.apache.uima.ducc.rm.ResourceManagerComponent.run(ResourceManagerComponent.java:279)
>   at java.lang.Thread.run(Thread.java:809)
> NodepoolScheduler 2422:
>  vmach_j[free]++; // This is the largest potential 
> share that can be made on this machine,
> This code appears to be only used to produce trace level messages



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

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
  Issue Type: Bug
  Components: DUCC
Reporter: Burn 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
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

[ 
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 should 
treat them as gone.

> UIMA-DUCC: Agent fails to kill a child process sometimes
> 
>
> Key: UIMA-5611
> URL: https://issues.apache.org/jira/browse/UIMA-5611
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Jerry Cwiklik
>Assignee: Jerry Cwiklik
> Fix For: 2.2.2-Ducc
>
>
> Improve detection of child processes which fail to stop after kill -9 was 
> sent. If kill -9 is sent by an agent while a child process is experiencing an 
> OOM, the signal is not acted upon and the process remains running.
> An agent should retry kill -9 on regular basis (configured in 
> ducc.properties) if a process is still standing after kill -9.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis]

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>
wrote:

>
>  [ 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 ArrayIndexOutOfBoundsException
> > -
> >
> > Key: UIMA-5605
> > URL: https://issues.apache.org/jira/browse/UIMA-5605
> > Project: UIMA
> >  Issue Type: Bug
> >  Components: DUCC
> >Affects Versions: 2.2.1-Ducc
> >Reporter: Jörg W
> > Fix For: future-DUCC
> >
> >
> > The scheduler stops scheduling and ducc-mon indicates inresposive
> ResourceManager.
> > rm.log (Trace):
> > 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A
> detectFragmentation  Freed shares 246 on machine xxx.xxx.xx
> > 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A
> detectFragmentation  Update v before: NP[ --default-- ] v:   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0 0   0   0   0   0   0   0
> > 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>  0   0   0   0   0   0   0   0   0   0   0   0   0   0
> > 05 Okt 2017 11:29:13,336 FATAL RM.ResourceManagerComponent- N/A
> runScheduler
> > java.lang.ArrayIndexOutOfBoundsException
> > An ArrayIndexOutOfBoundsException can occur in the NodepoolScheduler
> class at line 2422:
> > vmach_j[free]++;
> > Quickfix: comment it out. It seems only be used for logging (trace).
> >
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

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

[Burn Lewis (JIRA)]

 [ 
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 crashed with ArrayIndexOutOfBounds
> ---
>
> Key: UIMA-5606
> URL: https://issues.apache.org/jira/browse/UIMA-5606
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>    Reporter: Burn Lewis
> Fix For: future-DUCC
>
>
> 05 Oct 2017 09:51:13,701 FATAL RM.ResourceManagerComponent- N/A runScheduler 
> java.lang.ArrayIndexOutOfBoundsException
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.detectFragmentation(NodepoolScheduler.java:2422)
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.insureFullEviction(NodepoolScheduler.java:2509)
>   at 
> org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.schedule(NodepoolScheduler.java:2678)
>   at 
> org.apache.uima.ducc.rm.scheduler.Scheduler.schedule(Scheduler.java:1072)
>   at 
> org.apache.uima.ducc.rm.ResourceManagerComponent.runScheduler(ResourceManagerComponent.java:304)
>   at 
> org.apache.uima.ducc.rm.ResourceManagerComponent.run(ResourceManagerComponent.java:279)
>   at java.lang.Thread.run(Thread.java:809)
> NodepoolScheduler 2422:
>  vmach_j[free]++; // This is the largest potential 
> share that can be made on this machine,
> This code appears to be only used to produce trace level messages



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

 [ 
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 ArrayIndexOutOfBoundsException
> -
>
> Key: UIMA-5605
> URL: https://issues.apache.org/jira/browse/UIMA-5605
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Affects Versions: 2.2.1-Ducc
>Reporter: Jörg W
> Fix For: future-DUCC
>
>
> The scheduler stops scheduling and ducc-mon indicates inresposive 
> ResourceManager.
> rm.log (Trace):
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Freed shares 246 on machine xxx.xxx.xx
> 05 Okt 2017 11:29:13,336 TRACE RM.NodepoolScheduler- N/A detectFragmentation  
> Update v before: NP[ --default-- ] v:   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0 0   0   0   0   0   0   0  
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0   0
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   0   0   0   0   0   0   0   0   0   0 
> 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 
>   0   0   0   0   0   0   0   0   0   0   0   0 
> 05 Okt 2017 11:29:13,336 FATAL RM.ResourceManagerComponent- N/A runScheduler 
> java.lang.ArrayIndexOutOfBoundsException
> An ArrayIndexOutOfBoundsException can occur in the NodepoolScheduler class at 
> line 2422:
> vmach_j[free]++;  
> Quickfix: comment it out. It seems only be used for logging (trace).
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Reporter: Burn Lewis
 Fix For: future-DUCC


05 Oct 2017 09:51:13,701 FATAL RM.ResourceManagerComponent- N/A runScheduler 
java.lang.ArrayIndexOutOfBoundsException
at 
org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.detectFragmentation(NodepoolScheduler.java:2422)
at 
org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.insureFullEviction(NodepoolScheduler.java:2509)
at 
org.apache.uima.ducc.rm.scheduler.NodepoolScheduler.schedule(NodepoolScheduler.java:2678)
at 
org.apache.uima.ducc.rm.scheduler.Scheduler.schedule(Scheduler.java:1072)
at 
org.apache.uima.ducc.rm.ResourceManagerComponent.runScheduler(ResourceManagerComponent.java:304)
at 
org.apache.uima.ducc.rm.ResourceManagerComponent.run(ResourceManagerComponent.java:279)
at java.lang.Thread.run(Thread.java:809)

NodepoolScheduler 2422:
 vmach_j[free]++; // This is the largest potential 
share that can be made on this machine,

This code appears to be only used to produce trace level messages



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis]

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).
> ducc.broker.url.decoration=jms.useCompression=true
> prefetchPolicy.all=0
>
> Note: jms.prefetchPolicy.all=0
>
> This sets limits for all consumer types (topic and queue consumers)
>
> The earlier proposed decoration jms.prefetchPolicy.queuePrefetch=0 only
> effects
> consumers on a queue. Ducc daemons communicate mostly via topics.
>
>
> On Thu, Sep 28, 2017 at 6:36 PM, Jerry Cwiklik (JIRA)  >
> wrote:
>
> >
> > [ https://issues.apache.org/jira/browse/UIMA-5587?page=
> > com.atlassian.jira.plugin.system.issuetabpanels:comment-
> > tabpanel=16185023#comment-16185023 ]
> >
> > Jerry Cwiklik commented on UIMA-5587:
> > -
> >
> > The fix for the prefetch needs to go into default.ducc.properties
> >
> > # # The broker *client* url decoration (ie - DUCC daemons).
> > ducc.broker.url.decoration=jms.useCompression=true
> > prefetchPolicy.queuePrefetch=0
> >
> > Note: jms.prefetchPolicy.queuePrefetch=0
> >
> > With the above, a JMS consumer does not cache any msgs and instead asks a
> > broker for a single message at a time. This change effects all JMS
> > consumers  (Ducc daemons). Real services should use application broker
> not
> > the Ducc broker. I have not delivered any changes yet giving all a chance
> > to review this proposal.
> >
> > > DUCC Process Manager (PM) takes OOM on Apache DUCC demo
> > > ---
> > >
> > > Key: UIMA-5587
> > > URL: https://issues.apache.org/jira/browse/UIMA-5587
> > > Project: UIMA
> > >  Issue Type: Bug
> > >  Components: DUCC
> > >Reporter: Lou DeGenaro
> > >Assignee: Jerry Cwiklik
> > >Priority: Minor
> > > Fix For: future-DUCC
> > >
> > >
> > > Apache DUCC demo has PM that runs with reduced memory -Xmx200M
> > > On at least 2 occasions PM has taken OOM.  Core dumps have resulted
> that
> > indicate that PM is flooded with multiple OR publications that is
> supposed
> > to be handled by "BlastGuard"?
> > > Investigate what storage is being used for and if multiple OR messages
> > are being processed in parallel.  Perhaps Camel should be configured to
> > process OR message sequentially if it isn't already.
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.4.14#64029)
> >
>

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

[Burn Lewis (JIRA)]

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
  Components: DUCC
Reporter: Burn Lewis
Priority: Minor
 Fix For: future-DUCC


When preempting work for a new job the "shrinkBy" method evicts shares with the 
least investment from jobs with an excess of resources.  Later during 
defragmentation in takeFromTheRich it gives shares to a needy job by taking 
from the richest user in the required nodepool.  This can result in excessive 
preemption, double what is necessary, and the shares evicted by shrinkBy may 
not be in the node pool of the needy job, and may not free up enough contiguous 
space.  Perhaps the defrag step should adjust the evicted list for the rich 
jobs to be those in the nodepools of the needy job. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

[ 
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 file 
specified by system property "ducc.service.configuration" that is used to 
locate the registry and the configuration parameters need by the pull service & 
its server, i.e. registered name of server, server port, service type.  If a 
service loses contact with its server or none is available it will wait until 
one is registered. 
Note that JPs are given their JD url so do not use the registry.
 

> Add registry support so pull services can locate their server
> -
>
> Key: UIMA-5551
> URL: https://issues.apache.org/jira/browse/UIMA-5551
> Project: UIMA
>  Issue Type: New Feature
>  Components: DUCC
>Reporter: Burn Lewis
>Assignee: Burn Lewis
> Fix For: future-DUCC
>
>
> Optionally allow pull services to use a registry to locate resources such as 
> their server and other services such as a database.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

 [ 
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 server
> -
>
> Key: UIMA-5551
> URL: https://issues.apache.org/jira/browse/UIMA-5551
> Project: UIMA
>  Issue Type: New Feature
>  Components: DUCC
>    Reporter: Burn Lewis
>    Assignee: Burn Lewis
> Fix For: future-DUCC
>
>
> Optionally allow pull services to use a registry to locate resources such as 
> their server and other services such as a database.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

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
  Issue Type: Improvement
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn 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
(v6.4.14#64029)

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

[Burn Lewis (JIRA)]

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: Improvement
  Components: DUCC
Reporter: Burn Lewis
Priority: Minor
 Fix For: future-DUCC


Currently a long stack trace ends with "Connection refused"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)