[jira] Updated: (UIMA-1129) XMI serialization support for delta CAS
[ https://issues.apache.org/jira/browse/UIMA-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1129: --- Attachment: UIMA-1129-2.patch This patch adds support for Delta CAS serialization of modified non-shared multivalued feature. This requires serialization of the encompassing FS. XMI serialization support for delta CAS - Key: UIMA-1129 URL: https://issues.apache.org/jira/browse/UIMA-1129 Project: UIMA Issue Type: New Feature Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1129-1.patch, UIMA-1129-2.patch, UIMA-1129.patch Extend XMI serialization to enable serializing only the changes to the CAS. The requirement for delta CAS support in order to to reduce serialization overhead associated with remote services is described in the wiki page found here: http://cwiki.apache.org/UIMA/reducing-overhead-for-remote-service-calls.html. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1149) [UIMA-AS] fix potential thread safety issue with flow controller code
[ https://issues.apache.org/jira/browse/UIMA-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik updated UIMA-1149: Attachment: uimaj-as-core-UIMA-1149-patch.txt Synchronized access to the FlowControllerContainer and the FlowContainer to prevent concurrency issues while running the Aggregate with multiple listener threads. [UIMA-AS] fix potential thread safety issue with flow controller code - Key: UIMA-1149 URL: https://issues.apache.org/jira/browse/UIMA-1149 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2AS Reporter: Marshall Schor Priority: Minor Attachments: uimaj-as-core-UIMA-1149-patch.txt The general contract regarding threading for user-written UIMA components is that components do not have to be written to be thread-safe, or, more precisely, the framework guarantees it will not call an instance of a user-written component class on multiple threads at the same time. See http://incubator.apache.org/uima/downloads/releaseDocs/2.2.2-incubating/docs/html/tutorials_and_users_guides/tutorials_and_users_guides.html#ugr.tug.aae.contract_for_annotator_methods This is intended to make writing UIMA components by our user community easier, and to eliminate many hard-to-diagnose issues that could occur otherwise. The FlowController main object class, the one that is specified in the custom flow control specification for an aggregate, in UIMA-AS, can be (we think, but to be investigated :-) ) be called on multiple threads at the same time, in the current implementation. This Jira is to fix this, by synchronizing on the flow controller object so that users don't have to write thread safe implementations of this class. Also, the docs in the above referenced manual should be updated to include the flow controller object in the set of objects where the framework guarantees that instances of this object will not be called on multiple threads at the same time. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1165) Fix a race condition in the UIMA-AS aggregate that results in a hang
Fix a race condition in the UIMA-AS aggregate that results in a hang Key: UIMA-1165 URL: https://issues.apache.org/jira/browse/UIMA-1165 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik When running a complex Cas Multiplier Aggregate AS service with a scaled out listener threads, a race condition occurs that leads to a hang. Specifically, one thread obtains a number of child CASes produced from an input CAS, than this thread is preempted and another thread releases one of the child CASes. The parent CAS may not be released from the InProcessCache leading to CAS pool exhaustion since many CASes are stuck in the InProcessCache waiting to be released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1147) Merge uima-as-post1st branch with the uima-as SVN trunk
[ https://issues.apache.org/jira/browse/UIMA-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1147. --- Resolution: Fixed Merge uima-as-post1st branch with the uima-as SVN trunk --- Key: UIMA-1147 URL: https://issues.apache.org/jira/browse/UIMA-1147 Project: UIMA Issue Type: Task Components: Async Scaleout Reporter: Jerry Cwiklik Assignee: Jerry Cwiklik Attachments: uimaj-as-activemq-UIMA-1147-patch.txt, uimaj-as-core-UIMA-1147-patch-02.txt, uimaj-as-core-UIMA-1147-patch.txt, uimaj-as-jms-UIMA-1147-patch.txt Merge the uima-as branch with the SVN uima-as trunk -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1165) Fix a race condition in the UIMA-AS aggregate that results in a hang
[ https://issues.apache.org/jira/browse/UIMA-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik updated UIMA-1165: Attachment: uimaj-as-jms-UIMA-1165-patch.txt uimaj-as-core-UIMA-1165-patch.txt uimaj-as-activemq-UIMA-1165-patch.txt Synchronized critical sections in the UIMA AS Aggregate to fix a race condition that lead to a hang. Modified class boolean global vars to be volatile to make sure the changes are immediately visible to all the threads. Made several changes to remove inefficient synchronization using InProcessCache object which effectively locked that entire object. Removed dead code. Fix a race condition in the UIMA-AS aggregate that results in a hang Key: UIMA-1165 URL: https://issues.apache.org/jira/browse/UIMA-1165 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik Attachments: uimaj-as-activemq-UIMA-1165-patch.txt, uimaj-as-core-UIMA-1165-patch.txt, uimaj-as-jms-UIMA-1165-patch.txt When running a complex Cas Multiplier Aggregate AS service with a scaled out listener threads, a race condition occurs that leads to a hang. Specifically, one thread obtains a number of child CASes produced from an input CAS, than this thread is preempted and another thread releases one of the child CASes. The parent CAS may not be released from the InProcessCache leading to CAS pool exhaustion since many CASes are stuck in the InProcessCache waiting to be released. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1130) Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue
[ https://issues.apache.org/jira/browse/UIMA-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1130. --- Resolution: Fixed Deployment Descriptor should allow setting the number of concurrent listeners for a reply queue --- Key: UIMA-1130 URL: https://issues.apache.org/jira/browse/UIMA-1130 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Adam Lally Assignee: Marshall Schor Attachments: DDE_PATCH_JIRA_1130_A.txt, DDE_PATCH_JIRA_1130_B.txt The Spring XML allows setting a concurrentConsumers property for a reply queue (either an aggregate's collocated reply queue or a remote reply queue): property name=concurrentConsumers value=1/ The deployment descriptor should allow setting this property. In some deployments where remote delegates are scaled out many times, the bottleneck can become the aggregate deserializing CASes from the reply queue. If the aggregate is running on a multicore machine it helps to increase the number of threads that can process the reply queue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1166) Getmeta replies from some remote delegates are ignored, causing a timeout
Getmeta replies from some remote delegates are ignored, causing a timeout - Key: UIMA-1166 URL: https://issues.apache.org/jira/browse/UIMA-1166 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Burn Lewis The reply is falsely discarded: 9/4/08 3:15:05 PM - 22: org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.mergeTypeSystem: INFO: Controller: IODBurnTest Received Metadata From an Invalid (Possibly Disabled) Delegate: TopicLabellerAnnotatorQueue The recent change to support duplicate queue names on different brokers checks the broker name returned in the reply against the broker the request was sent to. But the service returns the name it uses for the broker, e.g. tcp://localhost:61616, and not the external name of the broker. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
