[
https://issues.apache.org/jira/browse/UIMA-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898300#comment-13898300
]
Lou DeGenaro edited comment on UIMA-3610 at 2/11/14 9:01 PM:
-------------------------------------------------------------
In addition, the JD will log at the INFO level into jd.out.log when the number
of threads (available work item slots) it is queuing to changes:
jd.out.log:11 Feb 2014 15:27:21,878 30 INFO client.DynamicThreadPoolExecutor
setCorePoolSize 1 changing core pool size to 2 from 1
jd.out.log:11 Feb 2014 15:27:51,903 30 INFO client.DynamicThreadPoolExecutor
setCorePoolSize 1 changing core pool size to 4 from 2
jd.out.log:11 Feb 2014 15:28:01,915 30 INFO client.DynamicThreadPoolExecutor
setCorePoolSize 1 changing core pool size to 8 from 4
jd.out.log:11 Feb 2014 15:29:01,960 30 INFO client.DynamicThreadPoolExecutor
setCorePoolSize 1 changing core pool size to 2 from 8
was (Author: lou.degenaro):
In addition, the JD will log at the INFO level into jd.out.log when the number
of threads (available work item slots) is it queuing to changes:
jd.out.log:11 Feb 2014 15:27:21,878 30 INFO client.DynamicThreadPoolExecutor
setCorePoolSize 1 changing core pool size to 2 from 1
jd.out.log:11 Feb 2014 15:27:51,903 30 INFO client.DynamicThreadPoolExecutor
setCorePoolSize 1 changing core pool size to 4 from 2
jd.out.log:11 Feb 2014 15:28:01,915 30 INFO client.DynamicThreadPoolExecutor
setCorePoolSize 1 changing core pool size to 8 from 4
jd.out.log:11 Feb 2014 15:29:01,960 30 INFO client.DynamicThreadPoolExecutor
setCorePoolSize 1 changing core pool size to 2 from 8
> DUCC Job Driver (JD) should unambiguously record to log UIMA-AS client
> sendAndReceive interactions
> --------------------------------------------------------------------------------------------------
>
> Key: UIMA-3610
> URL: https://issues.apache.org/jira/browse/UIMA-3610
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Affects Versions: 1.0-Ducc
> Reporter: Lou DeGenaro
> Assignee: Lou DeGenaro
> Priority: Minor
>
> Justification:
> When problems arise during interactions between JD and UIMA-AS cleint it
> would be very useful to know with 100% certainty which events have/have not
> occurred for each CAS. JD processing presently does some reasoning before
> actually recording to log.
> With this change, JD will log at the INFO level into jd.out.log the following:
> 1. sendAndReceive immediately before call
> 2. sendAndReceive immediately upon return
> 3. sendAndReceive immediately upon callback for onBeforeMessageSend
> 4. sendAndReceive immediately upon callback for onBeforeProcessCAS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
