new powerpoint presentation for uima v3 for review
Hi, I posted a powerpoint presentation for UIMA v3 here: https://uima.apache.org/downloads/uv3/UIMA_V3_Programmers_Solutions.pptx Feedback would be appreciated :-) Cheers. -Marshall P.S., still waiting for the 3rd vote on uima v3.0.0-beta rc8...
[jira] [Updated] (UIMA-5417) dd2spring should always ignore the scaleout value for sync UIMA-AS DDs
[ https://issues.apache.org/jira/browse/UIMA-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik updated UIMA-5417: Fix Version/s: (was: 2.10.2AS) future-Uima-AS > dd2spring should always ignore the scaleout value for sync UIMA-AS DDs > -- > > Key: UIMA-5417 > URL: https://issues.apache.org/jira/browse/UIMA-5417 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Burn Lewis >Priority: Minor > Fix For: future-Uima-AS > > > This is about dd2spring treatment of the scaleout element, in one particular > unusual use case. DD2Spring already has code to ignore the scaleout value, > if the top-level-aggregate is marked "async=true". This is because that > scaleout is only applicable for the case where async=false, and uima-as is > scaling the top-level-aggregate by having multiple threads (= pipelines) > replicating the top level aggregate. > When async=true, the scaleout element is ignored, because uima-as will be > (potentially) scaling out each async delegate separately. > The use case here is all about "defaulting" the async=true/false. The > current dd2spring code, if no specification is made for async=, defaults to > async=false, unless the deployment descriptor has individual specs for the > delgates, in which case it defaults to async=true. For this last case, > dd2spring is missing the the code to ignore the scaleout parameter (if set > > 1). This Jira is to add that check for that use case. > It lets the scaleout value change the caspool size when the async attribute > is defaulted to true (because the delegates element is specified, which > implies async="true") > . > The current dd2spring code correctly ignores the scaleout element when the > async attribute is explicitly set to "true" ... and it needs to do the same > when the default is "true". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (UIMA-5466) UIMA-AS doesn't load deployment descriptors from the classpath or datapath
[ https://issues.apache.org/jira/browse/UIMA-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik updated UIMA-5466: Fix Version/s: (was: 2.10.2AS) > UIMA-AS doesn't load deployment descriptors from the classpath or datapath > -- > > Key: UIMA-5466 > URL: https://issues.apache.org/jira/browse/UIMA-5466 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Burn Lewis >Priority: Minor > Fix For: future-Uima-AS > > > The top-level analysis engine descriptor and all others ARE loaded from the > class & data paths. The documentation does not explicitly say that DDs must > be in the filesystem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (UIMA-5466) UIMA-AS doesn't load deployment descriptors from the classpath or datapath
[ https://issues.apache.org/jira/browse/UIMA-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik updated UIMA-5466: Fix Version/s: future-Uima-AS > UIMA-AS doesn't load deployment descriptors from the classpath or datapath > -- > > Key: UIMA-5466 > URL: https://issues.apache.org/jira/browse/UIMA-5466 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Burn Lewis >Priority: Minor > Fix For: future-Uima-AS > > > The top-level analysis engine descriptor and all others ARE loaded from the > class & data paths. The documentation does not explicitly say that DDs must > be in the filesystem. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (UIMA-5641) Errors in custom containers cause class not found
[ https://issues.apache.org/jira/browse/UIMA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis closed UIMA-5641. Resolution: Fixed Access changed to public. Two methods in DuccAbstractProcessContainer must 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] [Closed] (UIMA-5386) UIMA-AS: performance breakdown wrong for sync aggregates
[ https://issues.apache.org/jira/browse/UIMA-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-5386. --- Resolution: Fixed Assignee: Jerry Cwiklik Fixed unique name by stripping thread number > UIMA-AS: performance breakdown wrong for sync aggregates > > > Key: UIMA-5386 > URL: https://issues.apache.org/jira/browse/UIMA-5386 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Jerry Cwiklik > Fix For: 2.10.2AS > > > See Ducc related issue: > https://issues.apache.org/jira/browse/UIMA-5311?filter=12329459 > Implement the fix as described in the above JIRA in the UIMA-AS code. -- 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 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)
[jira] [Updated] (UIMA-5599) DUCC JD node allocation and watching improvements
[
https://issues.apache.org/jira/browse/UIMA-5599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro updated UIMA-5599:
---
Description:
1. Services only DUCC, meaning no JD allocation - {color:#d04437}tbd{color}
2. DUCC Watcher warning - {color:#14892c}done{color}
a) No JD allocation
-b) Insufficient JD allocation-
3. Give example of cron job for DUCC Watcher in doc - {color:#14892c}done{color}
4. Allow mailhost to be specified on command line - {color:#d04437}tbd{color}
was:
1. Services only DUCC, meaning no JD allocation - {color:#d04437}tbd{color}
2. DUCC Watcher warning - {color:#14892c}done{color}
a) No JD allocation
-b) Insufficient JD allocation-
3. Give example of cron job for DUCC Watcher in doc - {color:#14892c}done{color}
> DUCC JD node allocation and watching improvements
> -
>
> Key: UIMA-5599
> URL: https://issues.apache.org/jira/browse/UIMA-5599
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
> Fix For: 2.2.2-Ducc
>
>
> 1. Services only DUCC, meaning no JD allocation - {color:#d04437}tbd{color}
> 2. DUCC Watcher warning - {color:#14892c}done{color}
> a) No JD allocation
> -b) Insufficient JD allocation-
> 3. Give example of cron job for DUCC Watcher in doc -
> {color:#14892c}done{color}
> 4. Allow mailhost to be specified on command line - {color:#d04437}tbd{color}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (UIMA-5640) UIMA-DUCC: JP/Service wrapper should not sleep when Work Item is not available
Jerry Cwiklik created UIMA-5640: --- Summary: UIMA-DUCC: JP/Service wrapper should not sleep when Work Item is not available Key: UIMA-5640 URL: https://issues.apache.org/jira/browse/UIMA-5640 Project: UIMA Issue Type: Improvement Components: DUCC Reporter: Jerry Cwiklik Assignee: Jerry Cwiklik Fix For: 2.2.2-Ducc Currently when JD/Protocol Handler runs out of work it returns null back in response to GET. In this case, the service wrapper sleeps for a fixed amount of time and tries again. The sleeping should be done in the client (JD/Protocol Handler) to reduce latency. Instead of waiting for a fixed amount of time, the client code can use notification/interrupt to wake up a sleeping GET thread when a new work items becomes available. The service wrapper will block in http get request until a reply comes or the get request times out. On timeout, the service will immediately call the client (JD/Protocol Handler). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
