Cancelling RC2 due to runtime issues found on the JD when running a job
(1.job) from ducc examples.

Issue#1
===========
JD throws an exception:
Feb 14, 2019 9:50:40 AM org.apache.uima.ducc.test.randomsleep.FixedSleepCR
getNext(328)
INFO: getNext
org.apache.uima.analysis_engine.AnalysisEngineProcessException: Annotator
class org.apache.uima.ducc.CasHelper requires Type
org.apache.uima.ducc.Workitem, which was not found in the CAS.
at org.apache.uima.ducc.CasHelper.getId(CasHelper.java:47)
at
org.apache.uima.ducc.user.jd.JdUserCollectionReader._getJdUserMetaCas(JdUserCollectionReader.java:169)
at
org.apache.uima.ducc.user.jd.JdUserCollectionReader.getJdUserMetaCas(JdUserCollectionReader.java:147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at
org.apache.uima.ducc.container.common.classloader.ContextSwitch.call(ContextSwitch.java:42)
at
org.apache.uima.ducc.container.jd.classload.ProxyJobDriverCollectionReader.getMetaCas(ProxyJobDriverCollectionReader.java:171)
at
org.apache.uima.ducc.container.jd.cas.CasManager.getMetaCas(CasManager.java:74)

Issue#2
=========
Despite above exceptions, the JD continues to serve JP work and duccmon
shows all work as completed (15 WIs). The job shows no errors.


On Thu, Feb 14, 2019 at 12:48 PM Jaroslaw Cwiklik <uim...@gmail.com> wrote:

> Yes, there are license and notice updates.
> I need to vote this RC down. Found some runtime issues.
>
> On Thu, Feb 14, 2019 at 12:03 PM Marshall Schor <m...@schor.com> wrote:
>
>> Hi Jerry,
>>
>> Did any of the upgrades to the dependencies you listed:
>>
>> Cassandra Server v.3.11.3,
>> Cassandra Driver v.3.6.0,
>> Jetty v.9.4.14.v20181114,
>> guava v.18.0,
>> joda v.2.4,
>> commons.lang v.3.1,
>> commons.math v.3.2,
>> netty v.4.0.44,
>> snappy v.1.1.1.7
>>
>> have any licensing / notice changes?
>>
>> -Marshall
>>
>>

Reply via email to