You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by cw...@apache.org on 2018/03/14 15:08:38 UTC
svn commit: r1826727 - /uima/uima-ducc/trunk/RELEASE_NOTES.html
Author: cwiklik
Date: Wed Mar 14 15:08:38 2018
New Revision: 1826727
URL: http://svn.apache.org/viewvc?rev=1826727&view=rev
Log:
UIMA-5728 add comment about uima-as limitation described in JIRA UIMA-5747
Modified:
uima/uima-ducc/trunk/RELEASE_NOTES.html
Modified: uima/uima-ducc/trunk/RELEASE_NOTES.html
URL: http://svn.apache.org/viewvc/uima/uima-ducc/trunk/RELEASE_NOTES.html?rev=1826727&r1=1826726&r2=1826727&view=diff
==============================================================================
--- uima/uima-ducc/trunk/RELEASE_NOTES.html (original)
+++ uima/uima-ducc/trunk/RELEASE_NOTES.html Wed Mar 14 15:08:38 2018
@@ -77,16 +77,20 @@ On some systems cgroups swap accounting
confirm, please check memory.stat file in <cgroups base dir>/ducc/ folder. If swap accounting is
enabled there should be "swap" property defined. If it's missing, you need to add a kernel parameter
swapaccount=1. Details of how to do this can be found <a href="http://unix.stackexchange.com/questions/147158/how-to-enable-swap-accounting-for-memory-cgroup-in-archlinux">here</a>.
-
+<p>
Due to a bug in uima sdk, the uima AnalysisEngineProcessException cannot be serialized as a Java object. If your
analysis engine throws an exception in process(), the ducc framework will stringify it and wrap it in
java RuntimeException. If you have a custom error handler plugged in into a job driver you will not be
able to test for AnalysisEngineProcessException in a stack trace with a code like this:
if ( error instanceof AnalysisEngineProcessException ) ...
-
+</p>
+<p>
To use OS-based login with the WebServer while running DUCC with IBM java, the minimum JDK version is
Java 8 SR4 FP5 (8.0.4.5).
-
+</p>
+<p>
+Due to a bug in uima-as v.2.10.2 (see <a href="https://issues.apache.org/jira/browse/UIMA-5747">https://issues.apache.org/jira/browse/UIMA-5747</a>), job processes which use uima-as Jms Service Descriptor may fail with javax.jms.InvalidClientIDException. The fix for this is to use uima-as 2.9.0.
+</p>
</body>
</html>