You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Lou DeGenaro (Jira)" <de...@uima.apache.org> on 2019/12/17 14:48:00 UTC

[jira] [Created] (UIMA-6163) DUCC Agent unable to accept Orchestrator publication when new field added

Lou DeGenaro created UIMA-6163:
----------------------------------

             Summary: DUCC Agent unable to accept Orchestrator publication when new field added
                 Key: UIMA-6163
                 URL: https://issues.apache.org/jira/browse/UIMA-6163
             Project: UIMA
          Issue Type: Improvement
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Lou DeGenaro
             Fix For: 3.0.1-Ducc


If a new field is added in OR publication, for example to communicate information from OR to RM that is not needed by Agent, an older Agent will unnecessarily take an exception when trying to marshal a more recent OR deployment.

Example Agent log:

---- Debugging information ----
message : No such field org.apache.uima.ducc.transport.event.common.DuccSchedulingInfo.machineList
field : machineList
class : org.apache.uima.ducc.transport.event.common.DuccSchedulingInfo
required-type : org.apache.uima.ducc.transport.event.common.DuccSchedulingInfo
converter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
path : /org.apache.uima.ducc.transport.event.DuccWorkReplyEvent/dw/duccSchedulingInfo/machineList
class[1] : org.apache.uima.ducc.transport.event.common.DuccWorkJob
class[2] : org.apache.uima.ducc.transport.event.DuccWorkReplyEvent
version : 1.4.10
-------------------------------



--
This message was sent by Atlassian Jira
(v8.3.4#803005)