We use the Jira "Release Notes" service to create the release-notes for our release; this in turn, depends on having the "Fixed in xxxxx" field correctly filled in. The many updates today to closed Jiras was due to a review of those, looking for cases where that field wasn't set, and then setting it to the proper component. -Marshall
This candidate is located at http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC7/ and includes uimaj uima-as sandbox uimacpp (this is a rebuild by Eddie, copied from p.a.o/~eae, rel 02) eclipse-update-site Let's see if this one will make it ... :-) -Marshall
[ https://issues.apache.org/jira/browse/UIMA-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1154:
---------------------------------
Fix Version/s: (was: 2.3S)
2.3AS
> UIMA-AS extended tests hang when running with IBM JVM 1.6 service release 1
> ---------------------------------------------------------------------------
>
> Key: UIMA-1154
> URL: https://issues.apache.org/jira/browse/UIMA-1154
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> When running extended tests in eclipse( version: 3.4.0) on Linux with IBM jvm 1.6 service
release 1, some of the tests are not completing due to a hang. Both the trunk code (before
the merge) and the merged code (from the branch) seem to exhibit this problem although on
different tests. The code from the trunk (before the merge) hangs on testcase: testTerminateOnFlowControllerException,
while the merged code hangs on testAggregateProcessCallWithLongDelay. The hangs are also
observed on Windows with IBM Jvm 1.6 service release 1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein closed UIMA-1684.
-------------------------------
Resolution: Fixed
> UIMA-CPP readme-s refer to 2.2.2
> --------------------------------
>
> Key: UIMA-1684
> URL: https://issues.apache.org/jira/browse/UIMA-1684
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Marshall Schor
> Assignee: Eddie Epstein
> Priority: Minor
>
> These need updating to 2.3.0 and review for correctness at this level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-1321:
--------------------------------
Affects Version/s: (was: 2.3)
2.3C
> UIMA C++ 2.2.2: compile error: call of overloaded 'addParam(XMLFileLoc)' is ambiguous
> -------------------------------------------------------------------------------------
>
> Key: UIMA-1321
> URL: https://issues.apache.org/jira/browse/UIMA-1321
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Affects Versions: 2.3C
> Environment: Ubuntu Linux (kernel 2.6), Intel x86 32-bit, GNU G++ 4.2.4
> Reporter: Jochen L. Leidner
> Priority: Minor
>
> Hi,
> I tried to compile the packaged release of the C++ implementation of the framework using
GNU C++ 4 on Ubuntu Linux,
> and got the following error:
> In file included from ./uima/resmgr.hpp:54,
> from ./uima/importdescription.hpp:46,
> from ./uima/typesystemdescription.hpp:44,
> from ./uima/taespecifier.hpp:45,
> from ./uima/engine.hpp:48,
> from ./uima/annotator_context.hpp:48,
> from ../cas/xcasdeserializer_handler.cpp:54:
> ./uima/location.hpp: In constructor 'uima::util::Location::Location()':
> ./uima/location.hpp:140: warning: deprecated conversion from string constant to 'char*'
> ../cas/xcasdeserializer_handler.cpp: In member function 'virtual void uima::XCASDeserializerHandler::error(const
xercesc_3_0::SAXParseException&)':
> ../cas/xcasdeserializer_handler.cpp:923: error: call of overloaded 'addParam(XMLFileLoc)'
is ambiguous
> ./uima/exceptions.hpp:172: note: candidates are: void uima::ErrorMessage::addParam(const
char*) <near match>
> ./uima/exceptions.hpp:174: note: void uima::ErrorMessage::addParam(const
std::string&) <near match>
> ./uima/exceptions.hpp:176: note: void uima::ErrorMessage::addParam(const
UChar*) <near match>
> ./uima/exceptions.hpp:178: note: void uima::ErrorMessage::addParam(const
icu_4_0::UnicodeString&)
> ./uima/exceptions.hpp:182: note: void uima::ErrorMessage::addParam(long
int)
> ./uima/exceptions.hpp:184: note: void uima::ErrorMessage::addParam(long
unsigned int)
> ./uima/exceptions.hpp:186: note: void uima::ErrorMessage::addParam(int)
> ./uima/exceptions.hpp:188: note: void uima::ErrorMessage::addParam(unsigned
int)
> ./uima/exceptions.hpp:190: note: void uima::ErrorMessage::addParam(double)
> ../cas/xcasdeserializer_handler.cpp:924: error: call of overloaded 'addParam(XMLFileLoc)'
is ambiguous
> ./uima/exceptions.hpp:172: note: candidates are: void uima::ErrorMessage::addParam(const
char*) <near match>
> ./uima/exceptions.hpp:174: note: void uima::ErrorMessage::addParam(const
std::string&) <near match>
> ./uima/exceptions.hpp:176: note: void uima::ErrorMessage::addParam(const
UChar*) <near match>
> ./uima/exceptions.hpp:178: note: void uima::ErrorMessage::addParam(const
icu_4_0::UnicodeString&)
> ./uima/exceptions.hpp:182: note: void uima::ErrorMessage::addParam(long
int)
> ./uima/exceptions.hpp:184: note: void uima::ErrorMessage::addParam(long
unsigned int)
> ./uima/exceptions.hpp:186: note: void uima::ErrorMessage::addParam(int)
> ./uima/exceptions.hpp:188: note: void uima::ErrorMessage::addParam(unsigned
int)
> ./uima/exceptions.hpp:190: note: void uima::ErrorMessage::addParam(double)
> [...]
> When commenting out all calls to msg.addParam() in the sources, the shared libraries
build fine.
> Any ideas?
> Thanks,
> Jochen
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein closed UIMA-799.
------------------------------
> C++ service reconnect to JMS provider
> -------------------------------------
>
> Key: UIMA-799
> URL: https://issues.apache.org/jira/browse/UIMA-799
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Bhavani Iyer
> Assignee: Bhavani Iyer
> Fix For: 2.3C
>
> Attachments: UIMACPP-799.patch
>
>
> The service wrapper currently fails when connection to the JMS provider is broken. It
should attempt to reestablish the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-799:
-------------------------------
Fix Version/s: 2.3C
> C++ service reconnect to JMS provider
> -------------------------------------
>
> Key: UIMA-799
> URL: https://issues.apache.org/jira/browse/UIMA-799
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Bhavani Iyer
> Assignee: Bhavani Iyer
> Fix For: 2.3C
>
> Attachments: UIMACPP-799.patch
>
>
> The service wrapper currently fails when connection to the JMS provider is broken. It
should attempt to reestablish the connection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1518:
---------------------------------
Fix Version/s: 2.3S
> improve SandboxDistr assembly
> -----------------------------
>
> Key: UIMA-1518
> URL: https://issues.apache.org/jira/browse/UIMA-1518
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Trivial
> Fix For: 2.3S
>
>
> Same changes as UIMA-1510
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1604:
---------------------------------
Fix Version/s: 2.3AS
> Add ShutdownHook to Uima As Service Wrapper
> -------------------------------------------
>
> Key: UIMA-1604
> URL: https://issues.apache.org/jira/browse/UIMA-1604
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> Uima AS service should implement a ShutdownHook to enable cleanup when the service is
killed via kill command. The action taken by the shutdown hook should be quiesce and stop.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-797:
-------------------------------
Fix Version/s: 2.3C
> JMX timing statistics reported by services
> ------------------------------------------
>
> Key: UIMA-797
> URL: https://issues.apache.org/jira/browse/UIMA-797
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Bhavani Iyer
> Assignee: Bhavani Iyer
> Fix For: 2.3C
>
>
> There needs to be a consistent approach to how timing statistics, e.g., processting time,
idle time, serialization time, are reported by a service. These should be averaged
> over the number of instances and in milliseconds.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-1079:
--------------------------------
Fix Version/s: 2.3C
> uima-as-distr build examples includes C++ example deployment - should be in uimacpp build
> -----------------------------------------------------------------------------------------
>
> Key: UIMA-1079
> URL: https://issues.apache.org/jira/browse/UIMA-1079
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout, C++ Framework
> Affects Versions: 2.2.2AS
> Reporter: Marshall Schor
> Assignee: Eddie Epstein
> Priority: Trivial
> Fix For: 2.3C
>
>
> Not fixing for 2.2.2AS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-1192:
--------------------------------
Fix Version/s: 2.3C
> runAECpp should include -lenient option
> ---------------------------------------
>
> Key: UIMA-1192
> URL: https://issues.apache.org/jira/browse/UIMA-1192
> Project: UIMA
> Issue Type: Improvement
> Components: C++ Framework
> Affects Versions: 2.2.2
> Reporter: Eddie Epstein
> Assignee: Eddie Epstein
> Priority: Minor
> Fix For: 2.3C
>
>
> "-lenient" is an important option in the UIMA runAE tool, and should be added to the
UIMACPP version of the tool.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-881:
-------------------------------
Fix Version/s: 2.3C
> runAECpp should output XMI
> --------------------------
>
> Key: UIMA-881
> URL: https://issues.apache.org/jira/browse/UIMA-881
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Bhavani Iyer
> Fix For: 2.3C
>
> Attachments: UIMA-881.patch
>
>
> runAECpp currently writes out XCAS. It should always output XMI.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-886:
-------------------------------
Fix Version/s: 2.3C
> Support fro fast GETMETA
> ------------------------
>
> Key: UIMA-886
> URL: https://issues.apache.org/jira/browse/UIMA-886
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Bhavani Iyer
> Assignee: Bhavani Iyer
> Fix For: 2.3C
>
> Attachments: UIMA-886.patch
>
>
> Part of the initialization of a UIMA AS client is sending a request for metadata. The
service is required to give highest priority to GETMETA requests arnd respond immediately.
This is already supported in the Java implementaion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-1620:
--------------------------------
Fix Version/s: 2.3C
> Add options runAECpp to enable testing of annotator in a multithreaded setup.
> ------------------------------------------------------------------------------
>
> Key: UIMA-1620
> URL: https://issues.apache.org/jira/browse/UIMA-1620
> Project: UIMA
> Issue Type: Improvement
> Components: C++ Framework
> Reporter: Bhavani Iyer
> Assignee: Bhavani Iyer
> Fix For: 2.3C
>
> Attachments: UIMACPP-1620.patch
>
>
> Add options to runAECpp:
> 1) instantiate multiple instances of the analysis engine and run these concurrently on
different threads.
> 2) option to do multiple runs of the same inputs.
> 3) randomize the next input to process
> 4) random delays between calls to process
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-1627:
--------------------------------
Fix Version/s: 2.3C
> Application link not working on gcc 4.2
> ---------------------------------------
>
> Key: UIMA-1627
> URL: https://issues.apache.org/jira/browse/UIMA-1627
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Eddie Epstein
> Assignee: Eddie Epstein
> Fix For: 2.3C
>
>
> Need to explicitly specify -lapr-1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eddie Epstein updated UIMA-1617:
--------------------------------
Fix Version/s: 2.3C
> Add support for quiesce and shut down
> --------------------------------------
>
> Key: UIMA-1617
> URL: https://issues.apache.org/jira/browse/UIMA-1617
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Bhavani Iyer
> Assignee: Bhavani Iyer
> Fix For: 2.3C
>
> Attachments: UIMACPP-1617.patch
>
>
> The C++ service wrapper needs to be modified to handle quiesce and shutdown requests
from the command line as well as from a Java controller.
> A 'q' entered at the command line should cause the wrapper to wait for the processing
instances to complete the current work before shutdown. A 's' entered at the command line
should result in an immediate shut down. Ctrl C is to be handled as a quiesce and shutdown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1628:
---------------------------------
Fix Version/s: 2.3C
> deployCppService does not return <elementType> on getMeta replies
> -----------------------------------------------------------------
>
> Key: UIMA-1628
> URL: https://issues.apache.org/jira/browse/UIMA-1628
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Eddie Epstein
> Fix For: 2.3C
>
>
> 3. I deployed the uimacpp AE service which has exactly the same typesystem as a uimaj
AE in the pipeline. However, the CASes are incompatible with the following reason:
> - There is a type 'Constituent' which has a 'children' feature. 'children' is of the
range type 'FSArray' with the element type 'Constituent'.
> - However, when getting the typesystem from the uimacpp service, the element type is
ignored. Both components cannot be plugged into one pipeline, because of an exception complaining
about incompatible typesystems.
> I will work around the last issue by altering the typesystem (removing the element type),
but this is not satisfactory.
> Kind regards
> Matthias
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1629:
---------------------------------
Fix Version/s: 2.3C
> UIMACPP <import> behavior not sufficiently documented
> -----------------------------------------------------
>
> Key: UIMA-1629
> URL: https://issues.apache.org/jira/browse/UIMA-1629
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Eddie Epstein
> Fix For: 2.3C
>
>
> 1. uimacpp does not support import by name <import name="..." />, which I think
is not mentioned in the documentation.
> 2. using <import location="..." /> employs a different path resolving strategy
from that of uimaj:
> - both support using absolute paths and relative paths (relative to the descriptor
in which the import occurs)
> - uimacpp can be given the environment variable UIMACPP_DATAPATH which is additionally
used to resolve relative paths
> - However, uimaj does not support resolving relative <import location="..." />
from it's datapath.
> Kind regards
> Matthias
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1623:
---------------------------------
Fix Version/s: 2.3AS
> Error handling incorrect if multiple delegates have the same window values
> --------------------------------------------------------------------------
>
> Key: UIMA-1623
> URL: https://issues.apache.org/jira/browse/UIMA-1623
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Burn Lewis
> Fix For: 2.3AS
>
>
> When delegates have the same processCas error configuration dd2spring gives them the
same Threshold object ... but that has R/W storage when a threshold window is specified, causing
premature error actions. Fix is to give each delegate a unique instance when necessary.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1685:
---------------------------------
Fix Version/s: 2.3S
> Sandbox licenses has uima-as licenses, but those are now moved out into a separate entity
> -----------------------------------------------------------------------------------------
>
> Key: UIMA-1685
> URL: https://issues.apache.org/jira/browse/UIMA-1685
> Project: UIMA
> Issue Type: Bug
> Components: Sandbox
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.3S
>
>
> The Sandbox license still includes the licenses for uima-as, which was moved out of the
sandbox. Remove these.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1653:
---------------------------------
Fix Version/s: 2.3C
> XMI Serialization of replies is not checking for FS references when serializing incoming
FSs
> --------------------------------------------------------------------------------------------
>
> Key: UIMA-1653
> URL: https://issues.apache.org/jira/browse/UIMA-1653
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
> Reporter: Bhavani Iyer
> Assignee: Bhavani Iyer
> Fix For: 2.3C
>
> Attachments: UIMACPP-1653.patch
>
>
> As discovered by Matthias Wendt when the incoming FS has a feature with multiple references
which is set by the C++ annotator, the FS reference is not serialized.
> Mathias provided the sample XMI below returned in the reply from a C++ service where
the 'variant' feature gets an id-ref value of "4", but there is no object having xmi:id="4".
> The feature 'variant' has MultipleReferenceAllowed set to true. The encompassing FS
is passed to C++ annotator which sets the 'variant' feature.
> ....(.........................n....K[..........$..T,...2....<?xml version
> ="1.0" encoding="UTF-8"?><xmi:XMI xmlns:examples="http:///org/apache/uima/e
> xamples.ecore" xmlns:cas="http:///uima/cas.ecore" xmlns:tcas="http:///uima/
> tcas.ecore" xmlns:xmi="http://www.omg.org/XMI" xmi:version="2.0"><cas:NULL
> xmi:id="0"/> <cas:Sofa xmi:id="1" sofaNum="1" sofaID="_InitialView" mimeTy
> pe="text" sofaString="Load or edit text here."/>. <tcas:DocumentAnnotation
> xmi:id="2" sofa="1" begin="0" end="23" language="en"/>. <examples:David xmi
> :id="3" sofa="1" begin="0" end="1" variants="4"/>.<cas:View sofa="1" member
> s="2 3"/></xmi:XMI>....9......CasReference...-37f4a0fc:124c9361c79:-7feb..C
> ommand.......IdleTime.......?...MessageFrom...DAVEDETECTORQ..MessageType...
> ....Payload.......ServerURI...tcp://localhost:61616..TimeInAnalytic........
> `..TimeInProcessCAS........`..TimeInService...........TimeToDeserializeCAS.
> .......P..TimeToSerializeCAS...................
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1577:
---------------------------------
Fix Version/s: 2.3S
> Do pear packaging with dependencies included for CFE
> ----------------------------------------------------
>
> Key: UIMA-1577
> URL: https://issues.apache.org/jira/browse/UIMA-1577
> Project: UIMA
> Issue Type: Bug
> Components: Sandbox-CFE
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.3S
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1621:
---------------------------------
Fix Version/s: 2.3
> CVD should work when classes loaded dynamically
> -----------------------------------------------
>
> Key: UIMA-1621
> URL: https://issues.apache.org/jira/browse/UIMA-1621
> Project: UIMA
> Issue Type: Bug
> Components: Tools
> Affects Versions: 2.3
> Reporter: Burn Lewis
> Assignee: Burn Lewis
> Priority: Minor
> Fix For: 2.3
>
>
> If CVD is loaded via the bootstrap loader it gets a NPE when configuring the logger.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1696:
---------------------------------
Fix Version/s: 2.3AS
> Fix log messages in UIMA AS aggregate
> -------------------------------------
>
> Key: UIMA-1696
> URL: https://issues.apache.org/jira/browse/UIMA-1696
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.3AS
> Reporter: Jerry Cwiklik
> Priority: Minor
> Fix For: 2.3AS
>
>
> Aggregate should swap arguments when logging certain messages. There are a few messages
where the key in a property file expects delegate key but the code places CAS id and where
the CAS id is expected the code places delegate key.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-1695:
---------------------------------
Fix Version/s: 2.3
> Eclipse tooling: CDE fully instantiates components of aggregates, resulting in OutOfMemory
issues
> -------------------------------------------------------------------------------------------------
>
> Key: UIMA-1695
> URL: https://issues.apache.org/jira/browse/UIMA-1695
> Project: UIMA
> Issue Type: Improvement
> Components: Eclipse plugins
> Affects Versions: 2.3
> Reporter: Thilo Goetz
> Priority: Minor
> Fix For: 2.3
>
>
> When I create an aggregate descriptor from several installed pears (e.g., WS tokenizer,
tagger & regex), the CDE creates an OOM situation on Eclipse 3.5 and Sun Java 6 on windows.
This seems to be due to the fact that the CDE fully instantiates delegate components to get
at their metadata. Is this really necessary? We keep all our metadata in xml specifically
so we don't have to do this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-1700.
--------------------------------
Resolution: Fixed
> copy LIC/NOT files to top level for UIMA-AS
> -------------------------------------------
>
> Key: UIMA-1700
> URL: https://issues.apache.org/jira/browse/UIMA-1700
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout, Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.3AS
>
>
> The License and Notice files for uima-as are under some directories - need to be easily
findable at the top level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
I am starting to update the release notes and build 07 candidates for base uima and uima-as, based on the fixes now closed in Jira. -Marshall
[ https://issues.apache.org/jira/browse/UIMA-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-1701.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3AS
> dd2spring script fails
> ----------------------
>
> Key: UIMA-1701
> URL: https://issues.apache.org/jira/browse/UIMA-1701
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Blocker
> Fix For: 2.3AS
>
>
> The script was not changed to use the new jarpath runner, so it just calls setUimaClassPath
, which is no longer modified by uima-as installation. So it doesn't get any of the new uima-as
jars. While here, check for any other scripts that need updating.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
dd2spring script fails
----------------------
Key: UIMA-1701
URL: https://issues.apache.org/jira/browse/UIMA-1701
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Marshall Schor
Assignee: Marshall Schor
Priority: Blocker
The script was not changed to use the new jarpath runner, so it just calls setUimaClassPath
, which is no longer modified by uima-as installation. So it doesn't get any of the new uima-as
jars. While here, check for any other scripts that need updating.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reopened UIMA-1700:
----------------------------------
the Disclaimer file should probably also be at the top level, and the README too, but renamed,
so as not to conflict with the base UIMA bin distribution file. This is because the readme
says to unzip & copy the uima-as bin distribution over the base distribution.
> copy LIC/NOT files to top level for UIMA-AS
> -------------------------------------------
>
> Key: UIMA-1700
> URL: https://issues.apache.org/jira/browse/UIMA-1700
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout, Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.3AS
>
>
> The License and Notice files for uima-as are under some directories - need to be easily
findable at the top level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz closed UIMA-1693.
-----------------------------
Resolution: Not A Problem
Ok, user error. Sorry for the noise. I don't usually set UIMA_HOME, and most things work
without it. I guess I shouldn't test stuff that I never use in real life ;-)
> Pear installer: logger config not found when running pear installer
> -------------------------------------------------------------------
>
> Key: UIMA-1693
> URL: https://issues.apache.org/jira/browse/UIMA-1693
> Project: UIMA
> Issue Type: Bug
> Components: Tools
> Affects Versions: 2.3
> Reporter: Thilo Goetz
> Priority: Minor
>
> I installed the 2.3-RC5 Eclipse tooling, imported the examples projects and tried to
run the pear installer via the preconfigured pear installer launch configuration. This results
in the exception below. The same does not happen when the pear installer is started via the
.bat file. Pear installation works regardless, so this is minor and should not hold up 2.3.
> java.io.FileNotFoundException: \config\Logger.properties (The system cannot find the
path specified.)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:112)
> at java.io.FileInputStream.<init>(FileInputStream.java:72)
> at java.util.logging.LogManager.readConfiguration(LogManager.java:459)
> at java.util.logging.LogManager$3.run(LogManager.java:221)
> at java.security.AccessController.doPrivileged(AccessController.java:202)
> at java.util.logging.LogManager.<clinit>(LogManager.java:207)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik closed UIMA-1292.
-------------------------------
Resolution: Fixed
Removed testTerminateOnInitializationFailureWithAggregateForcedShutdown() as it was causing
a hang. In this test, an aggregate tries to establish a connection to a non-existent broker.
before recent changes, the listener was not trying to recover a connection a broker and simply
terminated the service. Recent code changes force the listener to silently reconnect until
a broker is ready but since the broker is never started the test hangs. This test is no longer
valid.
> Uima AS Jms Listener Should Support Retry When Establishing Connection To a Broker
> ----------------------------------------------------------------------------------
>
> Key: UIMA-1292
> URL: https://issues.apache.org/jira/browse/UIMA-1292
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> UIMA AS service should support retry when a listener on the service input queue fails
due to a broker not being available. The listener should log a message stating the fact that
the broker is not available and it should enter a loop attempting to reconnect. When a broker
becomes available the listener should reconnect, log a message that the connection was made,
and proceed to complete initialization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili closed UIMA-1694.
---------------------------------
> Error 'scm url cannot be null' on uimaj POM
> -------------------------------------------
>
> Key: UIMA-1694
> URL: https://issues.apache.org/jira/browse/UIMA-1694
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.3S
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 2.3
>
>
> When launching 'mvn -Dmaven.repo.local=/tmp/uimaj-rc5 clean install' for testing the
new 2.3.0-rc5, an error 'scm url cannot be null' on uimaj POM comes out
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-1700.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3AS
> copy LIC/NOT files to top level for UIMA-AS
> -------------------------------------------
>
> Key: UIMA-1700
> URL: https://issues.apache.org/jira/browse/UIMA-1700
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout, Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.3AS
>
>
> The License and Notice files for uima-as are under some directories - need to be easily
findable at the top level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-1699.
----------------------------------
Resolution: Fixed
Assignee: Jerry Cwiklik (was: Marshall Schor)
Jerry - any issues with this change?
> UIMA-AS start broker appears to hang - but maybe a logging issue (RC6)
> ----------------------------------------------------------------------
>
> Key: UIMA-1699
> URL: https://issues.apache.org/jira/browse/UIMA-1699
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Marshall Schor
> Assignee: Jerry Cwiklik
> Priority: Blocker
> Fix For: 2.3AS
>
>
> Running the bringup tests with RC6 - the logging appears to be not working properly.
> bin/startBroker.sh appears to hang. But it is actually running ( both on Linux and Windows
) - as indicated by trying the sample in section 3.4 of the README for UIMA-AS.
> The "log" specified in the log4j configuration is created, but is empty.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
copy LIC/NOT files to top level for UIMA-AS
-------------------------------------------
Key: UIMA-1700
URL: https://issues.apache.org/jira/browse/UIMA-1700
Project: UIMA
Issue Type: Improvement
Components: Async Scaleout, Build, Packaging and Test
Reporter: Marshall Schor
Assignee: Marshall Schor
The License and Notice files for uima-as are under some directories - need to be easily findable
at the top level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reassigned UIMA-1699:
------------------------------------
Assignee: Marshall Schor
> UIMA-AS start broker appears to hang - but maybe a logging issue (RC6)
> ----------------------------------------------------------------------
>
> Key: UIMA-1699
> URL: https://issues.apache.org/jira/browse/UIMA-1699
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Blocker
> Fix For: 2.3AS
>
>
> Running the bringup tests with RC6 - the logging appears to be not working properly.
> bin/startBroker.sh appears to hang. But it is actually running ( both on Linux and Windows
) - as indicated by trying the sample in section 3.4 of the README for UIMA-AS.
> The "log" specified in the log4j configuration is created, but is empty.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
UIMA-AS start broker appears to hang - but maybe a logging issue (RC6)
----------------------------------------------------------------------
Key: UIMA-1699
URL: https://issues.apache.org/jira/browse/UIMA-1699
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Marshall Schor
Priority: Blocker
Fix For: 2.3AS
Running the bringup tests with RC6 - the logging appears to be not working properly.
bin/startBroker.sh appears to hang. But it is actually running ( both on Linux and Windows
) - as indicated by trying the sample in section 3.4 of the README for UIMA-AS.
The "log" specified in the log4j configuration is created, but is empty.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[ https://issues.apache.org/jira/browse/UIMA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry Cwiklik reopened UIMA-1292:
---------------------------------
Remove a testTerminateOnInitializationFailureWithDelegateBrokerMissing() test from extended
test suite that expects an exception when a Broker is not available. The code has recently
been changed to silently retry the connection indefinitely. Thus the test hangs.
> Uima AS Jms Listener Should Support Retry When Establishing Connection To a Broker
> ----------------------------------------------------------------------------------
>
> Key: UIMA-1292
> URL: https://issues.apache.org/jira/browse/UIMA-1292
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.3AS
>
>
> UIMA AS service should support retry when a listener on the service input queue fails
due to a broker not being available. The listener should log a message stating the fact that
the broker is not available and it should enter a loop attempting to reconnect. When a broker
becomes available the listener should reconnect, log a message that the connection was made,
and proceed to complete initialization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.