Build failed in Jenkins: UIMA-v3-sdk #279

2017-10-11 Thread Apache Jenkins Server 
See 


Changes:

[schor] [maven-release-plugin] prepare for next development iteration

[schor] [maven-release-plugin] prepare release 
uimaj-eclipse-update-site-3.0.0-beta

[schor] [UIMA-5613] cleanup pom to use relative paths instead of hard-coded ones

[schor] no Jira update maven release management plugin version to current (lost 
in subsequent update, redoing)

[schor] [maven-release-plugin] rollback the release of 
uimaj-eclipse-update-site-3.0.0-beta

[schor] [UIMA-5613] cleanup pom to use relative paths instead of hard-coded ones

--
[...truncated 1.94 MB...]
[INFO] artifact org.eclipse.equinox:preferences: checking for updates from 
central
[INFO] artifact org.eclipse.equinox:registry: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:registry: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.equinox:app: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:app: checking for updates from central
[INFO] artifact org.eclipse.equinox:registry: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:registry: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.core:resources: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.core:resources: checking for updates from central
[INFO] artifact org.eclipse.core:expressions: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.core:expressions: checking for updates from central
[INFO] artifact org.eclipse.core:runtime: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.core:runtime: checking for updates from central
[INFO] artifact org.eclipse.core:filesystem: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.core:filesystem: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.equinox:registry: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:registry: checking for updates from central
[INFO] artifact org.eclipse:osgi: checking for updates from eclipsePlugins
[INFO] artifact org.eclipse:osgi: checking for updates from central
[INFO] artifact org.eclipse.core:runtime: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.core:runtime: checking for updates from central
[INFO] artifact org.eclipse:ui: checking for updates from eclipsePlugins
[INFO] artifact org.eclipse:ui: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.swt:org.eclipse.swt.win32.win32.x86: checking for 
updates from eclipsePlugins
[INFO] artifact org.eclipse.swt:org.eclipse.swt.win32.win32.x86: checking for 
updates from central
[INFO] artifact org.eclipse.ui:ide: checking for updates from eclipsePlugins
[INFO] artifact org.eclipse.ui:ide: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse:osgi: checking for updates from eclipsePlugins
[INFO] artifact org.eclipse:osgi: checking for updates from central
[INFO] artifact org.eclipse.core:commands: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.core:commands: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.ui:views: checking for updates from eclipsePlugins
[INFO] artifact org.eclipse.ui:views: checking for updates from central
[INFO] artifact org.eclipse.ui.workbench:texteditor: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.ui.workbench:texteditor: checking for updates from 
central
[INFO] artifact org.eclipse.jface:text: checking for updates from eclipsePlugins
[INFO] artifact org.eclipse.jface:text: checking for updates from central

Re: testing uv3 with ...?

2017-10-11 Thread Richard Eckart de Castilho 
On 11.10.2017, at 16:01, Marshall Schor  wrote:
> 
> fixed in trunk.  Thanks for testing :-)
> 
> On 10/11/2017 9:50 AM, Marshall Schor wrote:
>> I think I found the cause: a faulty implementation of load(asInputStream, 
>> aCAS,
>> typeSystem).
>> 
>> Looking at the code, the 3rd argument is not used!  It looks like something
>> happened when migrating from V2 -> V3 code base, because it's OK in the v2 
>> code
>> base.  Maybe I can blame the cat (she sometimes jumps up onto my desk, 
>> landing
>> on my keyboard, and randomly pressing keys...) :-)
>> 
>> Apologies, and thank goodness for testing...

Now I'm seeing a new exception in the units tests using the three-argument 
signature:

org.apache.uima.cas.CASRuntimeException: Type Systems must be committed before 
calling this method.
at 
org.apache.uima.cas.impl.CasTypeSystemMapper.(CasTypeSystemMapper.java:101)
at 
org.apache.uima.cas.impl.TypeSystemImpl.lambda$0(TypeSystemImpl.java:1853)
at java.util.Map.computeIfAbsent(Map.java:957)
at 
org.apache.uima.cas.impl.TypeSystemImpl.getTypeSystemMapperInner(TypeSystemImpl.java:1852)
at 
org.apache.uima.cas.impl.TypeSystemImpl.getTypeSystemMapper(TypeSystemImpl.java:1841)
at 
org.apache.uima.cas.impl.BinaryCasSerDes6.(BinaryCasSerDes6.java:545)
at 
org.apache.uima.cas.impl.BinaryCasSerDes6.(BinaryCasSerDes6.java:639)
at 
org.apache.uima.cas.impl.BinaryCasSerDes.reinit(BinaryCasSerDes.java:593)
at org.apache.uima.util.CasIOUtils.load(CasIOUtils.java:382)
at org.apache.uima.util.CasIOUtils.load(CasIOUtils.java:344)
at 
de.tudarmstadt.ukp.dkpro.core.io.bincas.BinaryCasReader.getNext(BinaryCasReader.java:194)
at 
de.tudarmstadt.ukp.dkpro.core.io.bincas.BinaryCasWriterReaderTest.read(BinaryCasWriterReaderTest.java:561)
at 
de.tudarmstadt.ukp.dkpro.core.io.bincas.BinaryCasWriterReaderTest.test6Lenient(BinaryCasWriterReaderTest.java:164)
...

Mind, I actually do explicitly call typeSystem.commit() on the type system 
passed as the third argument before passing it.

Any immediate ideas?

Best,

-- Richard

Build failed in Jenkins: UIMA-uimaFIT v3 #62

2017-10-11 Thread Apache Jenkins Server 
See 

--
[...truncated 3.99 MB...]
/home/jenkins/jenkins-slave/maven-repositories/1/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
/home/jenkins/jenkins-slave/maven-repositories/1/org/bitbucket/mstrobel/procyon-compilertools/0.5.32/procyon-compilertools-0.5.32.jar
/home/jenkins/jenkins-slave/maven-repositories/1/org/sonatype/aether/aether-impl/1.7/aether-impl-1.7.jar

[DEBUG] Found Java API link: http://docs.oracle.com/javase/8/docs/api/
[DEBUG] /usr/local/asfpackages/java/jdk1.8.0_144/jre/../bin/javadoc @options 
@packages
[INFO] 
25 warnings
[WARNING] Javadoc Warnings
[WARNING] 
:81:
 warning: no @param for args
[WARNING] public static void main(String[] args) throws Exception {
[WARNING] ^
[WARNING] 
:81:
 warning: no @throws for java.lang.Exception
[WARNING] public static void main(String[] args) throws Exception {
[WARNING] ^
[WARNING] 
:82:
 warning: no @param for args
[WARNING] public static void main(String[] args) throws Exception {
[WARNING] ^
[WARNING] 
:82:
 warning: no @throws for java.lang.Exception
[WARNING] public static void main(String[] args) throws Exception {
[WARNING] ^
[WARNING] 
:72:
 warning: no @param for args
[WARNING] public static void main(String[] args) throws Exception {
[WARNING] ^
[WARNING] 
:72:
 warning: no @throws for java.lang.Exception
[WARNING] public static void main(String[] args) throws Exception {
[WARNING] ^
[WARNING] 
:36:
 warning: no @param for 
[WARNING] public static  T initializeBean(AutowireCapableBeanFactory 
aBeanFactory, T aBean, String aName) {
[WARNING] ^
[WARNING] 
:36:
 warning: no @param for aBeanFactory
[WARNING] public static  T initializeBean(AutowireCapableBeanFactory 
aBeanFactory, T aBean, String aName) {
[WARNING] ^
[WARNING] 
:36:
 warning: no @param for aBean
[WARNING] public static  T initializeBean(AutowireCapableBeanFactory 
aBeanFactory, T aBean, String aName) {
[WARNING] ^
[WARNING] 
:36:
 warning: no @param for aName
[WARNING] public static  T initializeBean(AutowireCapableBeanFactory 
aBeanFactory, T aBean, String aName) {
[WARNING] ^
[WARNING] 
:36:
 warning: no @return
[WARNING] public static  T initializeBean(AutowireCapableBeanFactory 
aBeanFactory, T aBean, String aName) {
[WARNING] ^
[WARNING] 
:46:
 warning: no @param for aResource
[WARNING] public static Resource initResource(Resource aResource, 
ApplicationContext aApplicationContext) {
[WARNING] ^
[WARNING] 
:46:
 warning: no @param for aApplicationContext
[WARNING] public static Resource initResource(Resource aResource, 
ApplicationContext aApplicationContext) {
[WARNING] ^
[WARNING] 
:46:
 warning: no @return
[WARNING] public static Resource initResource(Resource aResource, 
ApplicationContext aApplicationContext) {
[WARNING] ^

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

2017-10-11 Thread Jerry Cwiklik (JIRA) 

[ 
https://issues.apache.org/jira/browse/UIMA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200450#comment-16200450
 ] 

Jerry Cwiklik edited comment on UIMA-5611 at 10/11/17 9:03 PM:
---

An agent should check status of a process after kill -9 is issued to detect if 
its defunct. It should exec a ps command and parse the output to test for 
defunct bit. If one is detected, the agent should mark such process as Stopped 
and add Reason=Defunct.


was (Author: cwiklik):
An agent should check status of a process after kill -9 is issued to detect a 
defunct process. It should exec a ps command and parse the output to test for 
defunct. if one is detected, the agent should mark such process as Stopped and 
add Reason=Defunct.

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

[jira] [Commented] (UIMA-5562) UIMA AS fails with HttpConnector

2017-10-11 Thread Jerry Cwiklik (JIRA) 

[ 
https://issues.apache.org/jira/browse/UIMA-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200947#comment-16200947
 ] 

Jerry Cwiklik commented on UIMA-5562:
-

John, I was able to reproduce the problem. The workaround for now is 
prefetch=1. Since this is an AMQ problem the fix is to upgrade UIMA-AS to AMQ 
5.15.1 or newer. 

> UIMA AS fails with HttpConnector
> 
>
> Key: UIMA-5562
> URL: https://issues.apache.org/jira/browse/UIMA-5562
> Project: UIMA
>  Issue Type: Bug
>  Components: Async Scaleout
>Affects Versions: 2.9.0AS
> Environment: Windows 7 and Linux
>Reporter: John
>Priority: Blocker
> Attachments: myTestScenario.bat
>
>
> Hi,
> if I try to use UIMA AS with ActiveMQ http-connector, which is provided in 
> default configuration, I do get a timeout.
> Steps to reproduce:
> # Unzip http://www-eu.apache.org/dist/uima/uima-as-2.9.0/uima-as-2.9.0-bin.zip
> # Set InputDirectory in 
> {{apache-uima-2.9.0/examples/descriptors/collection_reader/FileSystemCollectionReader.xml}}
>  to correct absolute path 
> # Copy attached Batch-File into directory
> # Start it, wait and press 3 times Enter
> If I set BROKER_URL to tcp://localhost:61616 in the Batch-Script, the 
> documents are processed successfully.
> With value http://localhost:8080 I get the following exception.
> {code}
> Error on getMeta call to remote service:
> org.apache.uima.aae.error.UimaASMetaRequestTimeout: UIMA AS Client Timed Out 
> Waiting For GetMeta Reply From a Service On Queue:MeetingDetectorTaeQueue
> at 
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.notifyOnTimout(BaseUIMAAsynchronousEngineCommon_impl.java:2350)
> at 
> org.apache.uima.adapter.jms.client.ClientServiceDelegate.handleError(ClientServiceDelegate.java:192)
> at org.apache.uima.aae.delegate.Delegate$2.run(Delegate.java:839)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> Terminating Client...
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stop() - 
> Stop
> ping UIMA-AS Client
> javax.jms.JMSException: A consumer is consuming from the temporary destination
> at 
> org.apache.activemq.ActiveMQConnection.deleteTempDestination(ActiveMQConnection.java:2061)
> at 
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stopConnection(BaseUIMAAsynchronousEngine_impl.java:324)
> at 
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_impl.stop(BaseUIMAAsynchronousEngine_impl.java:345)
> at 
> org.apache.uima.examples.as.RunRemoteAsyncAE$StatusCallbackListenerImpl.stop(RunRemoteAsyncAE.java:367)
> at 
> org.apache.uima.examples.as.RunRemoteAsyncAE$StatusCallbackListenerImpl.initializationComplete(RunRemoteAsyncAE.java:360)
> at 
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.notifyListeners(BaseUIMAAsynchronousEngineCommon_impl.java:1220)
> at 
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl.notifyOnTimout(BaseUIMAAsynchronousEngineCommon_impl.java:2351)
> at 
> org.apache.uima.adapter.jms.client.ClientServiceDelegate.handleError(ClientServiceDelegate.java:192)
> at org.apache.uima.aae.delegate.Delegate$2.run(Delegate.java:839)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}



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

[VOTE] uimaj sdk 3.0.0 beta rc4

2017-10-11 Thread Marshall Schor 
Here's RC4 for uimaj-sdk 3.0.0-beta.

The fixes since the recent rc3 are UIMA-5584 and newer;
you can view all 77 Jiras for this version here:

https://issues.apache.org/jira/issues/?jql=project%20%3D%2012310570%20AND%20fixVersion%20%3D%2012339590%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

shows all 77 changes, ordered by key descending.

The main fixes are:

- rename of the getEmpty  array / list of various types
  to be shorter, dropping the "get"
- Properly handle DocumentAnnotation subclasses during deserialization
- Fix bugs in deserialized form4 sofas indexing
- Fix toString for feature structures, add a v2 compatibility flag and mode
- Set proper classloaders when reiniting type systems during some 
deserializations
- fix bugs in how sofa features set during deserialization
- add capability to do extended-for on all FSs of a type in a view
- fix initialization sequencing for JCas classes, when loaded before Type 
System Init
- allow setExtensionClassLoader to not wrap passed in UIMAClassLoader
- fix toString for FeatureStructures to use always \n and not \r\n sometimes 
(breaks some test cases)
- fix typo in merging from v2 of CasUtilsIO for loading with a passed in type 
system (type system was being ignored)

 The v3 users guide has many updates and corrections;
any reviews appreciated 

Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheuima-1158/

Source and binary zip/tar staged to:
https://dist.apache.org/repos/dist/dev/uima/uimaj/3.0.0-rc4/artifacts/

Eclipse update site (no need to download,
just use this as the link in Eclipse's install):
https://dist.apache.org/repos/dist/dev/uima/uimaj/3.0.0-rc4/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

Jenkins build is back to normal : UIMA-Ruta-v3 #10

2017-10-11 Thread Apache Jenkins Server 
See

Build failed in Jenkins: UIMA-Ruta-v3 #9

2017-10-11 Thread Apache Jenkins Server 
See 

--
[...truncated 3.05 MB...]
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
averbis-osgi-releases
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
averbis-osgi-releases
[INFO] artifact org.eclipse.equinox:app: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:app: checking for updates from central
[INFO] artifact org.eclipse.equinox:app: checking for updates from 
averbis-osgi-releases
[INFO] artifact org.eclipse.equinox:registry: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:registry: checking for updates from central
[INFO] artifact org.eclipse.equinox:registry: checking for updates from 
averbis-osgi-releases
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
averbis-osgi-releases
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:common: checking for updates from central
[INFO] artifact org.eclipse.equinox:common: checking for updates from 
averbis-osgi-releases
[INFO] artifact org.eclipse.equinox:app: checking for updates from 
eclipsePlugins
[INFO] artifact org.eclipse.equinox:app: checking for updates from central
[INFO] artifact org.eclipse.equinox:app: checking for updates from 
averbis-osgi-releases
[INFO] 
[INFO] --- cobertura-maven-plugin:2.7:instrument (default-cli) @ ruta ---
[INFO] Skipping cobertura mojo for project with packaging type 'pom'
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.7:cobertura (default-cli) < [cobertura]test 
@ ruta <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.7:cobertura (default-cli) @ ruta ---
[INFO] 
[INFO] >>> maven-javadoc-plugin:2.9.1:javadoc (default-cli) > generate-sources 
@ ruta >>>
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-versions) @ ruta ---
[INFO] 
[INFO] --- build-helper-maven-plugin:1.8:parse-version (parse-project-version) 
@ ruta ---
[INFO] 
[INFO] --- uima-build-helper-maven-plugin:7:parse-date-time (set buildYear and 
buildMonth) @ ruta ---
[WARNING] Failed to getClass for org.apache.maven.plugin.javadoc.JavadocReport
[INFO] 
[INFO] <<< maven-javadoc-plugin:2.9.1:javadoc (default-cli) < generate-sources 
@ ruta <<<
[INFO] 
[INFO] --- maven-javadoc-plugin:2.9.1:javadoc (default-cli) @ ruta ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache UIMA Ruta: ruta-parent .. SUCCESS [01:51 min]
[INFO] Apache UIMA Ruta: ruta-basic-type .. SUCCESS [01:32 min]
[INFO] Apache UIMA Ruta: ruta-typesystem .. SUCCESS [01:16 min]
[INFO] Apache UIMA Ruta: ruta-core  SUCCESS [02:31 min]
[INFO] Apache UIMA Ruta: ruta-core-ext  SUCCESS [ 53.463 s]
[INFO] Apache UIMA Ruta: ruta-ep-parent ... SUCCESS [06:17 min]
[INFO] Apache UIMA Ruta Eclipse: ruta-ep-engine ... SUCCESS [ 53.047 s]
[INFO] Apache UIMA Ruta Eclipse: ruta-ep-ide .. SUCCESS [05:40 min]
[INFO] Apache UIMA Ruta Eclipse: ruta-ep-ide-ui ... SUCCESS [09:43 min]
[INFO] Apache UIMA Ruta Eclipse: ruta-ep-caseditor  SUCCESS [05:36 min]
[INFO] Apache UIMA Ruta Eclipse: ruta-ep-addons ... SUCCESS [05:09 min]
[INFO] Apache UIMA Ruta Eclipse: ruta-ep-textruler  SUCCESS [05:57 min]
[INFO] Apache UIMA Ruta Eclipse: ruta-ep-core-ext . SUCCESS [04:57 min]
[INFO] Apache UIMA Maven: ruta-maven-plugin ... SUCCESS [01:49 min]
[INFO] Apache UIMA Maven: ruta-maven-archetype  SUCCESS [ 31.163 s]
[INFO] Apache UIMA Ruta Documentation . SUCCESS [ 50.629 s]
[INFO] Apache UIMA Ruta Eclipse: ruta-eclipse-feature . SUCCESS [ 31.822 s]
[INFO] Apache UIMA Ruta: ruta-ep-example-extensions ... SUCCESS [04:32 min]
[INFO] Apache UIMA Ruta: ruta-maven-example ... SUCCESS [01:04 min]
[INFO] Apache UIMA Ruta: ruta . SUCCESS [ 40.547 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 01:03 h
[INFO] Finished at: 2017-10-11T16:39:29+00:00
[INFO] Final Memory: 190M/695M
[INFO] 
Waiting for Jenkins to finish collecting data
[JENKINS] Archiving 
 to

Re: [jira] [Created] (UIMA-5614) support Eclipse Jar signing in build

2017-10-11 Thread Marshall Schor 
my browser glitched - 5614 is a dup of 5613.  I just deleted the 5614 issue
completely.

-Marshall


On 10/11/2017 10:20 AM, Marshall Schor (JIRA) wrote:
> Marshall Schor created UIMA-5614:
> 
>
>  Summary: support Eclipse Jar signing in build
>  Key: UIMA-5614
>  URL: https://issues.apache.org/jira/browse/UIMA-5614
>  Project: UIMA
>   Issue Type: Bug
>   Components: Build, Packaging and Test, Eclipse plugins
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
>
> Change the eclipse update site build mechanism to support code signing.  
> Document on the main website.  
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>

[jira] [Deleted] (UIMA-5614) support Eclipse Jar signing in build

2017-10-11 Thread Marshall Schor (JIRA) 

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

Marshall Schor deleted UIMA-5614:
-


> support Eclipse Jar signing in build
> 
>
> Key: UIMA-5614
> URL: https://issues.apache.org/jira/browse/UIMA-5614
> Project: UIMA
>  Issue Type: Bug
>Reporter: Marshall Schor
>Assignee: Marshall Schor
>
> Change the eclipse update site build mechanism to support code signing.  
> Document on the main website.  



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

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

2017-10-11 Thread Jerry Cwiklik (JIRA) 

[ 
https://issues.apache.org/jira/browse/UIMA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200450#comment-16200450
 ] 

Jerry Cwiklik edited comment on UIMA-5611 at 10/11/17 3:28 PM:
---

An agent should check status of a process after kill -9 is issued to detect a 
defunct process. It should exec a ps command and parse the output to test for 
defunct. if one is detected, the agent should mark such process as Stopped and 
add Reason=Defunct.


was (Author: cwiklik):
An agent should check status of a process after kill -9 is issued to detect 
defunct a process. It should exec a ps command and parse the output to test for 
defunct. if one is detected, the agent should mark such process as Stopped and 
add Reason=Defunct.

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

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

2017-10-11 Thread Jerry Cwiklik (JIRA) 

[ 
https://issues.apache.org/jira/browse/UIMA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16200450#comment-16200450
 ] 

Jerry Cwiklik commented on UIMA-5611:
-

An agent should check status of a process after kill -9 is issued to detect 
defunct a process. It should exec a ps command and parse the output to test for 
defunct. if one is detected, the agent should mark such process as Stopped and 
add Reason=Defunct.

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

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

2017-10-11 Thread 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] [Created] (UIMA-5614) support Eclipse Jar signing in build

2017-10-11 Thread Marshall Schor (JIRA) 
Marshall Schor created UIMA-5614:


 Summary: support Eclipse Jar signing in build
 Key: UIMA-5614
 URL: https://issues.apache.org/jira/browse/UIMA-5614
 Project: UIMA
  Issue Type: Bug
  Components: Build, Packaging and Test, Eclipse plugins
Reporter: Marshall Schor
Assignee: Marshall Schor


Change the eclipse update site build mechanism to support code signing.  
Document on the main website.  



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

[jira] [Created] (UIMA-5613) support Eclipse Jar signing in build

2017-10-11 Thread Marshall Schor (JIRA) 
Marshall Schor created UIMA-5613:


 Summary: support Eclipse Jar signing in build
 Key: UIMA-5613
 URL: https://issues.apache.org/jira/browse/UIMA-5613
 Project: UIMA
  Issue Type: Bug
  Components: Build, Packaging and Test, Eclipse plugins
Reporter: Marshall Schor
Assignee: Marshall Schor


Change the eclipse update site build mechanism to support code signing.  
Document on the main website.  



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

Re: testing uv3 with ...?

2017-10-11 Thread Marshall Schor 
fixed in trunk.  Thanks for testing :-)

-Marshall


On 10/11/2017 9:50 AM, Marshall Schor wrote:
> I think I found the cause: a faulty implementation of load(asInputStream, 
> aCAS,
> typeSystem).
>
> Looking at the code, the 3rd argument is not used!  It looks like something
> happened when migrating from V2 -> V3 code base, because it's OK in the v2 
> code
> base.  Maybe I can blame the cat (she sometimes jumps up onto my desk, landing
> on my keyboard, and randomly pressing keys...) :-)
>
> Apologies, and thank goodness for testing...
>
> -Marshall
>
> On 10/10/2017 4:45 PM, Richard Eckart de Castilho wrote:
>> On 10.10.2017, at 22:03, Richard Eckart de Castilho  wrote:
>>> On 09.10.2017, at 16:35, Marshall Schor  wrote:
 I think this will need a test case - can you provide one?
>>> I can see the extended error message and will try to produce a reduced unit 
>>> test.
>>>
>>> org.apache.uima.cas.CASRuntimeException: Deserializing Compressed Form 6, a 
>>> type code: 71 has no corresponding type. currentFsId: 1 nbrFSs: 0 
>>> nextFsAddr: 1 
>>> at 
>>> org.apache.uima.cas.impl.BinaryCasSerDes6.deserializeAfterVersion(BinaryCasSerDes6.java:1812)
>>> at 
>>> org.apache.uima.cas.impl.BinaryCasSerDes.reinit(BinaryCasSerDes.java:594)
>>> at org.apache.uima.util.CasIOUtils.load(CasIOUtils.java:382)
>>> at org.apache.uima.util.CasIOUtils.load(CasIOUtils.java:344)
>>>...
>> This seems to happen only when CasIOUtils.load(casInputStream, aCAS, 
>> typeSystem) is used.
>> I tried to set up a minimal test which serializes a CAS into one byte-array 
>> for the contents
>> and a second one for the type system, then deserializes this into a new CAS 
>> using the
>> method above. However, this doesn't seem to trigger the problem. So it might 
>> be related
>> to the fact that in the failing DKPro Core test, there are also two 
>> collection reader components
>> and an analysis engine (actually a writing component) involved.
>>
>> I'll try to expand the test until it fails. If you have any additional 
>> pointers, please
>> let me know.
>>
>> Cheers,
>>
>> -- Richard
>

Re: testing uv3 with ...?

2017-10-11 Thread Marshall Schor 
I think I found the cause: a faulty implementation of load(asInputStream, aCAS,
typeSystem).

Looking at the code, the 3rd argument is not used!  It looks like something
happened when migrating from V2 -> V3 code base, because it's OK in the v2 code
base.  Maybe I can blame the cat (she sometimes jumps up onto my desk, landing
on my keyboard, and randomly pressing keys...) :-)

Apologies, and thank goodness for testing...

-Marshall

On 10/10/2017 4:45 PM, Richard Eckart de Castilho wrote:
> On 10.10.2017, at 22:03, Richard Eckart de Castilho  wrote:
>> On 09.10.2017, at 16:35, Marshall Schor  wrote:
>>> I think this will need a test case - can you provide one?
>> I can see the extended error message and will try to produce a reduced unit 
>> test.
>>
>> org.apache.uima.cas.CASRuntimeException: Deserializing Compressed Form 6, a 
>> type code: 71 has no corresponding type. currentFsId: 1 nbrFSs: 0 
>> nextFsAddr: 1 
>>  at 
>> org.apache.uima.cas.impl.BinaryCasSerDes6.deserializeAfterVersion(BinaryCasSerDes6.java:1812)
>>  at 
>> org.apache.uima.cas.impl.BinaryCasSerDes.reinit(BinaryCasSerDes.java:594)
>>  at org.apache.uima.util.CasIOUtils.load(CasIOUtils.java:382)
>>  at org.apache.uima.util.CasIOUtils.load(CasIOUtils.java:344)
>>...
> This seems to happen only when CasIOUtils.load(casInputStream, aCAS, 
> typeSystem) is used.
> I tried to set up a minimal test which serializes a CAS into one byte-array 
> for the contents
> and a second one for the type system, then deserializes this into a new CAS 
> using the
> method above. However, this doesn't seem to trigger the problem. So it might 
> be related
> to the fact that in the failing DKPro Core test, there are also two 
> collection reader components
> and an analysis engine (actually a writing component) involved.
>
> I'll try to expand the test until it fails. If you have any additional 
> pointers, please
> let me know.
>
> Cheers,
>
> -- Richard