gmane.comp.apache.uima.devel

[jira] Created: (UIMA-1246) Error handling for CASes generated in an aggregate needs clarification.

Eddie Epstein (JIRA — 2008-12-03T17:39:44

Error handling for CASes generated in an aggregate needs clarification. ----------------------------------------------------------------------- Key: UIMA-1246 URL: https://issues.apache.org/jira/browse/UIMA-1246 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Eddie Epstein Burn raised the question of error handling for CM children within a multi-threaded UIMA AS aggregate. A summary of discussion with Burn, Adam, Jerry, Marshall and Eddie is below. A child CAS is a CAS that was generated by a CasMultiplier delegate within the same aggregate. The child's parent CAS will never be returned by an aggregate until all processing of it's children is completed. A child CAS may encounter an error condition while being processed by a delegate. If the delegate error handling results in a non-recoverable error, processing of the child's parent CAS will be stopped and the error report will be returned against that parent CAS. If the parent CAS is itself a child CAS, the error will be propagated to its parent CAS. Note: The parent CAS(es) may have other outstanding children in play (currently being processed). Our discussion touched on but did not fully analyze whether processing on these children should continue or be stopped. More discussion needed.

[jira] Created: (UIMA-1245) Processing order of parent CAS different on UIMA and UIMA AS

Eddie Epstein (JIRA — 2008-12-03T16:55:44

Processing order of parent CAS different on UIMA and UIMA AS ------------------------------------------------------------ Key: UIMA-1245 URL: https://issues.apache.org/jira/browse/UIMA-1245 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Eddie Epstein Arron Kaplan raised the question of when parent CASes are processed relative to their children. See http://markmail.org/message/5cop7iv2nshouhgs As of now, the processing order for a multi-threaded UIMA AS aggregate is different than that for a single-threaded UIMA aggregate. A discussion with Burn, Adam, Jerry, Marshall and myself concluded that the default processing order for UIMA AS should be changed to be the same as in UIMA, in order to have the same application behavior for both. This will be done by suspending flow of a parent CAS after it is returned from a CasMultiplier delegate until all its children CASes have finished processing. However, there also needs to be a UIMA AS deployment option for CasMultiplier delegates that allows the parent CAS to resume processing immediately after being returned from the CM. This option is needed to enable parallel processing.

Status page update

Thilo Goetz — 2008-12-03T10:20:17

I committed a new version of the uima.xml status file, adding Tong and Jerry as committers. Is there anything I need to do to get this published, or is it synced automatically? --Thilo

[jira] Created: (UIMA-1244) PDF for Tutorials and Users' Guides printing fails on page 32

Marshall Schor (JIRA — 2008-12-02T20:34:44

PDF for Tutorials and Users' Guides printing fails on page 32 ------------------------------------------------------------- Key: UIMA-1244 URL: https://issues.apache.org/jira/browse/UIMA-1244 Project: UIMA Issue Type: Bug Components: Documentation Affects Versions: 2.2.2 Reporter: Marshall Schor Assignee: Marshall Schor Priority: Minor Fix For: 2.3 The PDF for the Tutorials and Users' Guides fails to print with Acrobat Reader 8 and 9 (may print with earlier versions - not confirmed). Generating the PDF with the lastest release of Apache FOP (0.95) seems to avoid this issue. Move the doc generation to 0.95 and check the resulting docs print OK. See discussion: http://markmail.org/message/rv236b6gxxsxrhg6

[jira] Created: (UIMA-1243) testFindAbsoluteUrl(org.apache.uima.resource.metadata.impl.Import_implTest) fails on windows

Thilo Goetz (JIRA — 2008-12-02T17:04:44

testFindAbsoluteUrl(org.apache.uima.resource.metadata.impl.Import_implTest) fails on windows -------------------------------------------------------------------------------------------- Key: UIMA-1243 URL: https://issues.apache.org/jira/browse/UIMA-1243 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Affects Versions: 2.2.2 Environment: Windows, Sun Java 6. Didn't test other JVMs. Reporter: Thilo Goetz Priority: Minor URL comparison fails because device is in capitals (C:) in one instance, and in lowercase (c:) in the other. Not sure how to fix this. ------------------------------------------------------------------------------- Test set: org.apache.uima.resource.metadata.impl.Import_implTest ------------------------------------------------------------------------------- Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec <<< FAILURE! testFindAbsoluteUrl(org.apache.uima.resource.metadata.impl.Import_implTest) Time elapsed: 0.016 sec <<< FAILURE! junit.framework.AssertionFailedError: expected: but was: at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:71) at org.apache.uima.resource.metadata.impl.Import_implTest.testFindAbsoluteUrl(Import_implTest.java:124) at org.apache.uima.resource.metadata.impl.Import_implTest.testFindAbsoluteUrl(Import_implTest.java:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.GeneratedMethodAccessor313.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)

[jira] Created: (UIMA-1242) Array-valued features are written out incorrectly when serializing type system

Thilo Goetz (JIRA — 2008-12-02T13:40:44

Array-valued features are written out incorrectly when serializing type system ------------------------------------------------------------------------------ Key: UIMA-1242 URL: https://issues.apache.org/jira/browse/UIMA-1242 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.2.2 Reporter: Thilo Goetz Assignee: Thilo Goetz Fix For: 2.3 When serializing a type system that contains type with array-valued features, type declarations as below are generated: org.apache.uima.test.Test uima.tcas.Annotation sofa uima.cas.Sofa begin uima.cas.Integer end uima.cas.Integer array uima.tcas.Annotation[] uima.tcas.Annotation[] uima.cas.FSArray These are of course incorrect and can't be read back in.

[jira] Created: (UIMA-1241) UIMA AS Service Should Expose Cas Pool Size for Monitioring via JMX

Jerry Cwiklik (JIRA — 2008-12-01T16:27:44

UIMA AS Service Should Expose Cas Pool Size for Monitioring via JMX ------------------------------------------------------------------- Key: UIMA-1241 URL: https://issues.apache.org/jira/browse/UIMA-1241 Project: UIMA Issue Type: New Feature Components: Async Scaleout Reporter: Jerry Cwiklik The internal Cas Pool of the UIMA AS service needs to be exposed via JMX for monitoring. Currently, only the Cas Multiplier's Cas Pool is exposed. All Cas Pools are JMX enabled already. Modifiy JmxMonitor to query JMX Server for the Cas Pool size.

Can't print PDF version of UIMA Tutorial and Developer's Guide

Thilo Goetz — 2008-12-01T12:43:39

I can't print page 32 of the developer's guide. This is on Windows with both Acrobat 8 and 9. Has anybody else seen this? --Thilo

[jira] Created: (UIMA-1240) Deployment Descriptor Editor resets CAS Pool size for aggregates when you change number of instances of a delegate

Adam Lally (JIRA — 2008-11-26T22:36:46

Deployment Descriptor Editor resets CAS Pool size for aggregates when you change number of instances of a delegate ------------------------------------------------------------------------------------------------------------------ Key: UIMA-1240 URL: https://issues.apache.org/jira/browse/UIMA-1240 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Adam Lally Assignee: Tong Fin I have an async aggregate with multiple delegates. When I set the number of instances of one of the delegates (it happened to be a CAS Multiplier, but I'm not sure that matters), the DDE automatically reset the CAS Pool size of the entire aggregate to the same value! It took me quite a while to figure out that this was the reason my application started running more slowly.

[jira] Created: (UIMA-1239) Fix "Consumer Closed" Exception Thrown By ActiveMQ

Jerry Cwiklik (JIRA — 2008-11-26T19:00:45

Fix "Consumer Closed" Exception Thrown By ActiveMQ --------------------------------------------------- Key: UIMA-1239 URL: https://issues.apache.org/jira/browse/UIMA-1239 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik ActiveMQ seems to close a connection to a broker if the connection is not actively used. This results in different types of exceptions thrown by a listener on an input queue. Sometimes the exception is " Broken Pipe", in other times "Consumer Closed". This error prevents the service from receiving messages and leads to a hang as CASes sent by a client never come back

[jira] Created: (UIMA-1238) Fix NullPointerException When Sending Reply to Uima AS Client

Jerry Cwiklik (JIRA — 2008-11-25T17:57:44

Fix NullPointerException When Sending Reply to Uima AS Client ------------------------------------------------------------- Key: UIMA-1238 URL: https://issues.apache.org/jira/browse/UIMA-1238 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik There is a NPE when sending a reply back to a client from Uima AS aggregate. Caused by: java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:846) at org.apache.uima.aae.spi.transport.vm.UimaVmMessage.addStringProperty(UimaVmMessage.java:52) at org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.sendVMMessage(AggregateAnalysisEngineController_impl.java:1594) at org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.replyToClient(AggregateAnalysisEngineController_impl.java:1552) at org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.finalStep(AggregateAnalysisEngineController_impl.java:1358) ... 13 more It seems that the code is trying to set a property with a value of NULL which is not allowed

[jira] Created: (UIMA-1237) Fix "Cas Not Found In CasManager Cache" Error in the Parallel Step

Jerry Cwiklik (JIRA — 2008-11-25T16:57:44

Fix "Cas Not Found In CasManager Cache" Error in the Parallel Step ------------------------------------------------------------------ Key: UIMA-1237 URL: https://issues.apache.org/jira/browse/UIMA-1237 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik There is an exception when processing a secondary reply from a delegate in a parallel step. The exception indicates that the CAS id received in a reply message from one of the delegates in the parallel step does not exist in the cache. The exception happens in the testcase that tests disable of one of the delegates in the parallel step.

[jira] Created: (UIMA-1236) Fix a hang in the testProcessParallelFlowWithDelegateDisable testcase

Jerry Cwiklik (JIRA — 2008-11-25T16:15:44

Fix a hang in the testProcessParallelFlowWithDelegateDisable testcase ---------------------------------------------------------------------- Key: UIMA-1236 URL: https://issues.apache.org/jira/browse/UIMA-1236 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik This testcase occasionally hangs after the delegate is disabled and its reply queue listener killed.

UIMACPP release webpage info

Eddie Epstein — 2008-11-23T19:59:54

In preparation for the release, please take a look at http://incubator.apache.org/uima/doc-uimacpp-huh.html Thanks, Eddie

[jira] Created: (UIMA-1235) Changes for the first UIMACPP release.

Eddie Epstein (JIRA — 2008-11-23T17:27:44

Changes for the first UIMACPP release. -------------------------------------- Key: UIMA-1235 URL: https://issues.apache.org/jira/browse/UIMA-1235 Project: UIMA Issue Type: New Feature Components: Website Reporter: Eddie Epstein Assignee: Eddie Epstein Download links, getting started guide, etc.

[jira] Created: (UIMA-1234) Cleanup Testcases to Handle ServiceShutdownException Quietly

Jerry Cwiklik (JIRA — 2008-11-21T21:45:44

Cleanup Testcases to Handle ServiceShutdownException Quietly ------------------------------------------------------------ Key: UIMA-1234 URL: https://issues.apache.org/jira/browse/UIMA-1234 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik UIMA AS testcases dump ServiceShutdownException to stdout. Modify testcase code to ignore this exception. Service sends a ShutdownException to its client when it terminates.

[jira] Created: (UIMA-1233) Log Outgoing Message Sizes Destined for Remote Queue

Jerry Cwiklik (JIRA — 2008-11-21T20:21:44

Log Outgoing Message Sizes Destined for Remote Queue ---------------------------------------------------- Key: UIMA-1233 URL: https://issues.apache.org/jira/browse/UIMA-1233 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik Log the size of CAS before sending it to a remote queue.

[jira] Created: (UIMA-1232) Fix Synchronization Problem in the UIMA AS code

Jerry Cwiklik (JIRA — 2008-11-21T20:15:44

Fix Synchronization Problem in the UIMA AS code ----------------------------------------------- Key: UIMA-1232 URL: https://issues.apache.org/jira/browse/UIMA-1232 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik UIMA AS Aggregate code synchronizes code that sends a reply (CAS) back to a client. Part of sending the CAS back to the remote client is serialization of the CAS. This takes time. While the CAS is being serialized, other threads are blocked causing a bottleneck. Move the code that sends a reply outside of the synchronized block.

[jira] Created: (UIMA-1231) UIMA AS Doesnt Expose to JMX Sizes of Java Queues Used For Internal Messaging

Jerry Cwiklik (JIRA — 2008-11-21T20:11:44

UIMA AS Doesnt Expose to JMX Sizes of Java Queues Used For Internal Messaging ----------------------------------------------------------------------------- Key: UIMA-1231 URL: https://issues.apache.org/jira/browse/UIMA-1231 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik Uima AS uses java queues for internal messaging. The depths of these queues are not visible in jmx. Add JMX support to both input and output queues. Modify JMX Monitor to show the depth of the java queues.

[jira] Created: (UIMA-1230) When parsing an aggregate descriptor, should parse a shared type system file only once

Adam Lally (JIRA — 2008-11-20T19:42:44

When parsing an aggregate descriptor, should parse a shared type system file only once -------------------------------------------------------------------------------------- Key: UIMA-1230 URL: https://issues.apache.org/jira/browse/UIMA-1230 Project: UIMA Issue Type: Improvement Components: Core Java Framework Affects Versions: 2.2.2 Reporter: Adam Lally Assignee: Adam Lally Priority: Minor Fix For: 2.3 Frequently an aggregate will contain several primitives that all import a single shared type system descriptor. Currently, the shared type system descriptor will be separately parsed for each of the primitives, and each primitive descriptor will contain a separate copy of the TypeSystemDescription object. When there are a large number of primitives and a large number of types in the shared type system, this parsing takes a long time and the resulting TypeSystemDescription objects consume a lot of memory. Instead, we could keep a cache of imports that have already been parsed, and we can reuse the same TypeSystemDescription object within each of the primitive descriptors rather than having a separate copy.

Vote : Donate TIkaAnnotator to Sandbox

Julien Nioche — 2008-11-20T14:16:51

Hi guys, Not sure if I am supposed to initiate the vote myself as I am not a committer. Are you in favour of adding the Tika Annotator to the sandbox? Best, Julien