[jira] Created: (UIMA-1666) CasPoolSize should equal numberOfInstances when deploying a primitive component
CasPoolSize should equal numberOfInstances when deploying a primitive component --- Key: UIMA-1666 URL: https://issues.apache.org/jira/browse/UIMA-1666 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1625) AnalysisEngmeManagementImpl getAnalysisTime() and getCasesProcessedPerSecond() should include remote service call time.
[ https://issues.apache.org/jira/browse/UIMA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer closed UIMA-1625. -- Fixed. AnalysisEngmeManagementImpl getAnalysisTime() and getCasesProcessedPerSecond() should include remote service call time. --- Key: UIMA-1625 URL: https://issues.apache.org/jira/browse/UIMA-1625 Project: UIMA Issue Type: Bug Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1625-uimaj-core.patch Service call time is recorded but not included in analysis time and in computing CASes per second. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1625) AnalysisEngmeManagementImpl getAnalysisTime() and getCasesProcessedPerSecond() should include remote service call time.
AnalysisEngmeManagementImpl getAnalysisTime() and getCasesProcessedPerSecond() should include remote service call time. --- Key: UIMA-1625 URL: https://issues.apache.org/jira/browse/UIMA-1625 Project: UIMA Issue Type: Bug Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Service call time is recorded but not included in analysis time and in computing CASes per second. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1625) AnalysisEngmeManagementImpl getAnalysisTime() and getCasesProcessedPerSecond() should include remote service call time.
[ https://issues.apache.org/jira/browse/UIMA-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1625: --- Attachment: UIMA-1625-uimaj-core.patch getAnalysisTime() return sum of analysisTime and serviceCallTime. This way applications can call one API to get the time in AE and do not need to know whether AE is local or remote. getCASesPerSecond() returns getAnalysisTime() / numProcessed. numProcessed now accumulated for services. AnalysisEngmeManagementImpl getAnalysisTime() and getCasesProcessedPerSecond() should include remote service call time. --- Key: UIMA-1625 URL: https://issues.apache.org/jira/browse/UIMA-1625 Project: UIMA Issue Type: Bug Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1625-uimaj-core.patch Service call time is recorded but not included in analysis time and in computing CASes per second. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1620) Add options to enable testing of annotator in a multithreaded setup.
Add options 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 Reporter: Bhavani Iyer Add options to: 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.
[jira] Updated: (UIMA-1620) Add options runAECpp to enable testing of annotator in a multithreaded setup.
[ https://issues.apache.org/jira/browse/UIMA-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1620: --- Component/s: C++ Framework Description: 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 was: Add options to: 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 Assignee: Bhavani Iyer Summary: Add options runAECpp to enable testing of annotator in a multithreaded setup. (was: Add options to enable testing of annotator in a multithreaded setup.) 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 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.
[jira] Updated: (UIMA-1620) Add options runAECpp to enable testing of annotator in a multithreaded setup.
[ https://issues.apache.org/jira/browse/UIMA-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1620: --- Attachment: UIMACPP-1620.patch The following optional command line arguments enable these functions: -n numInstances number of annotator instances each running in a separate thread -r numRuns number of iterations over the same input. -rand randomize the selection on next input to process. -rdelay max random delay in millis between 0 and this max between calls to process. 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 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.
[jira] Created: (UIMA-1616) Add ability to quiesce C++ service before shutdown
Add ability to quiesce C++ service before shutdown -- Key: UIMA-1616 URL: https://issues.apache.org/jira/browse/UIMA-1616 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Need the ability to ask a C++ services to complete the current work before shutting down. Undeploying a service should not result in loss of work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1617) Add support for quiesce and shut down
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 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.
[jira] Assigned: (UIMA-1617) Add support for quiesce and shut down
[ https://issues.apache.org/jira/browse/UIMA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1617: -- Assignee: Bhavani Iyer 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 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.
[jira] Assigned: (UIMA-1616) Add ability to quiesce C++ service before shutdown
[ https://issues.apache.org/jira/browse/UIMA-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1616: -- Assignee: Bhavani Iyer Add ability to quiesce C++ service before shutdown -- Key: UIMA-1616 URL: https://issues.apache.org/jira/browse/UIMA-1616 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Assignee: Bhavani Iyer Need the ability to ask a C++ services to complete the current work before shutting down. Undeploying a service should not result in loss of work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1616) Add ability to quiesce C++ service before shutdown
[ https://issues.apache.org/jira/browse/UIMA-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1616: --- Attachment: UIMA-1616.patch Modified quiesceAndStop() method to send a QUIESCEANDSTOP request to the C++ service. This requires the patch in UIMA-1617 which modifies the C++ service wrapper to process this request type. The C++ service wrapper will call the JMS Connection stop() method to stop dispatch of new messages and allow the processing threads to complete current work before shutting down the service. A QUIESCEANDSTOP request is initiated when a 'q' is entered at the command prompt or service is shutdown with CTRL C. The controller waits for an quiesce done response from the service. This patch also modifies the UimacppServiceController shutdown() api which is used to stop the service immediately to wait for acknowledgment from the service that shutdown was initiated. Add ability to quiesce C++ service before shutdown -- Key: UIMA-1616 URL: https://issues.apache.org/jira/browse/UIMA-1616 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1616.patch Need the ability to ask a C++ services to complete the current work before shutting down. Undeploying a service should not result in loss of work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1617) Add support for quiesce and shut down
[ https://issues.apache.org/jira/browse/UIMA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1617: --- Attachment: UIMACPP-1617.patch Modified the C++ service wrapper to handle QUIESCEANDSTOP request The wrapper will call stop() on the Connection to stop dispatch of message. It will allow processing threads to complete current work, send a DONE message to the Java controller and terminate the C++ process. The UIMA-1616 patch is required for compatibility with the Java UimacppServiceController. 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 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.
[jira] Created: (UIMA-1611) UimacppServiceControlled need to implement isStopped()
UimacppServiceControlled need to implement isStopped() -- Key: UIMA-1611 URL: https://issues.apache.org/jira/browse/UIMA-1611 Project: UIMA Issue Type: Bug Reporter: Bhavani Iyer Required in order for UIMA_Service to undeploy and shutdown when handling a stop or quiesce and stop command. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1608) JMX statistics are not being updated
JMX statistics are not being updated Key: UIMA-1608 URL: https://issues.apache.org/jira/browse/UIMA-1608 Project: UIMA Issue Type: Bug Reporter: Bhavani Iyer Process CAS requests are not updating the statistics correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1608) JMX statistics are not being updated
[ https://issues.apache.org/jira/browse/UIMA-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1608: -- Assignee: Bhavani Iyer JMX statistics are not being updated Key: UIMA-1608 URL: https://issues.apache.org/jira/browse/UIMA-1608 Project: UIMA Issue Type: Bug Reporter: Bhavani Iyer Assignee: Bhavani Iyer Process CAS requests are not updating the statistics correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1608) JMX statistics are not being updated
[ https://issues.apache.org/jira/browse/UIMA-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1608: --- Attachment: UIMACPP-1608.patch JMX statistics are not being updated Key: UIMA-1608 URL: https://issues.apache.org/jira/browse/UIMA-1608 Project: UIMA Issue Type: Bug Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMACPP-1608.patch Process CAS requests are not updating the statistics correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1584) Document Delta CAS XMI format
Document Delta CAS XMI format - Key: UIMA-1584 URL: https://issues.apache.org/jira/browse/UIMA-1584 Project: UIMA Issue Type: Bug Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Update xmi reference. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1584) Document Delta CAS XMI format
[ https://issues.apache.org/jira/browse/UIMA-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1584: --- Attachment: UIMA-1584.patch Added a section on Delta CAS XMI format. Document Delta CAS XMI format - Key: UIMA-1584 URL: https://issues.apache.org/jira/browse/UIMA-1584 Project: UIMA Issue Type: Bug Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1584.patch Update xmi reference. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1269) NPE when using a C++ service deployed via JNI
[ https://issues.apache.org/jira/browse/UIMA-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1269: --- Attachment: UIMA-1269-uimaj-as-activemq.patch UIMA-1269-uimaj-as-core.patch Prerequisite for this patch is the patch for issue UIMA-1569. CPP serivices do not support delta CAS format and receive and return the complete CAS. The Marker created prior to receiving a complete CAS in the reply is therefore invalid for future delta CAS serialization. Added a test that Marker is valid prior to delta serialization and do a complete serialization if it is invalid. In addition, a new Marker is created to be used in subsequent delta CAS serialzation. The modification applied to both XMI and Binary delta CAS formats. NPE when using a C++ service deployed via JNI - Key: UIMA-1269 URL: https://issues.apache.org/jira/browse/UIMA-1269 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Burn Lewis Assignee: Bhavani Iyer Attachments: UIMA-1269-uimaj-as-activemq.patch, UIMA-1269-uimaj-as-core.patch C++ services don't support delta CAS so the JNI wrapper clears the Marker before uploading the C++ CAS but then the service crashes when trying to return a delta CAS to its caller. May also have a problem in an aggregate if one of its services does not support delta CAS ... need to invalidate the input Marker and make the aggregate return a full CAS. Should also create a fresh Marker for following delegates so they can return delta CASes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1569) Marker should be make invalid when CAS is reset.
Marker should be make invalid when CAS is reset. Key: UIMA-1569 URL: https://issues.apache.org/jira/browse/UIMA-1569 Project: UIMA Issue Type: Bug Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer When the CAS is reset any Marker created prior to the reset are invalid and should not be used for a later delta CAS serialization. The reset() should make the Marker invalid and calls to delta serialization should test whether the Marker is valid. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1569) Marker should be make invalid when CAS is reset.
[ https://issues.apache.org/jira/browse/UIMA-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1569: --- Attachment: UIMA-1569.patch The CAS will maintain a handle to all Marker objects it created and make them invalid when the CAS is reset. Using an invalid Marker to serialize a delta CAS will result in an exception being thrown. Marker should be make invalid when CAS is reset. Key: UIMA-1569 URL: https://issues.apache.org/jira/browse/UIMA-1569 Project: UIMA Issue Type: Bug Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1569.patch When the CAS is reset any Marker created prior to the reset are invalid and should not be used for a later delta CAS serialization. The reset() should make the Marker invalid and calls to delta serialization should test whether the Marker is valid. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-799) C++ service reconnect to JMS provider
[ https://issues.apache.org/jira/browse/UIMA-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-799: - Assignee: Bhavani Iyer 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 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.
[jira] Updated: (UIMA-799) C++ service reconnect to JMS provider
[ https://issues.apache.org/jira/browse/UIMA-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-799: -- Attachment: UIMACPP-799.patch The modifications to the service wrapper to support reconnect include: 1. Replace registering a MessageListener to receive message with the synchrounous receive() api. 2. Added reporting of Reconnecting and ReconnectionSuccess status. 3. Added support for fast GetMeta. 4. Cleanup of code to support other JMS providers. 5. Cleaup to the JMX statistics 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 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.
[jira] Assigned: (UIMA-1490) C++ service fails to properly terminate when UimacppServiceController is stopped.
[ https://issues.apache.org/jira/browse/UIMA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1490: -- Assignee: Bhavani Iyer C++ service fails to properly terminate when UimacppServiceController is stopped. - Key: UIMA-1490 URL: https://issues.apache.org/jira/browse/UIMA-1490 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer The C++ service is still running after UimacppServiceController has terminated. The problem appears to be that the AnalysisEngine instances are not explicitly destroyed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1490) C++ service fails to properly terminate when UimacppServiceController is stopped.
C++ service fails to properly terminate when UimacppServiceController is stopped. - Key: UIMA-1490 URL: https://issues.apache.org/jira/browse/UIMA-1490 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer The C++ service is still running after UimacppServiceController has terminated. The problem appears to be that the AnalysisEngine instances are not explicitly destroyed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1490) C++ service fails to properly terminate when UimacppServiceController is stopped.
[ https://issues.apache.org/jira/browse/UIMA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1490: --- Attachment: UIMACPP-1490.patch Added call to destroy AnalysisEngine instances before terminating. C++ service fails to properly terminate when UimacppServiceController is stopped. - Key: UIMA-1490 URL: https://issues.apache.org/jira/browse/UIMA-1490 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMACPP-1490.patch The C++ service is still running after UimacppServiceController has terminated. The problem appears to be that the AnalysisEngine instances are not explicitly destroyed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1459) Fix UIMA AS bugs reported by Findbugs
[ https://issues.apache.org/jira/browse/UIMA-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1459: --- Attachment: UIMA-1459.patch Fixed UimacppServiceController and related MBean classes. Fix UIMA AS bugs reported by Findbugs - Key: UIMA-1459 URL: https://issues.apache.org/jira/browse/UIMA-1459 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik Assignee: Bhavani Iyer Fix For: 2.3AS Attachments: UIMA-1459.patch There are many bugs found by Findbugs in the UIMA As code. Some are minor like a deadstore in a var that is never used. Others are more severe like dereferencing a var that is not checked for NULL. Clean up the code to eliminate reported bugs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1278) Add ability to report JMS reconnection status
Add ability to report JMS reconnection status - Key: UIMA-1278 URL: https://issues.apache.org/jira/browse/UIMA-1278 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Bhavani Iyer The ControllerCallbackListener needs to be extended to provide APIs to report JMS reconnection status. At present this status is reported by C++ services via the UimacppServiceController bean, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1278) Add ability to report JMS reconnection status
[ https://issues.apache.org/jira/browse/UIMA-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1278: -- Assignee: Bhavani Iyer Add ability to report JMS reconnection status - Key: UIMA-1278 URL: https://issues.apache.org/jira/browse/UIMA-1278 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Bhavani Iyer Assignee: Bhavani Iyer The ControllerCallbackListener needs to be extended to provide APIs to report JMS reconnection status. At present this status is reported by C++ services via the UimacppServiceController bean, -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1256) UIMA-AS XMI serialization loses items appended to an FSList
[ https://issues.apache.org/jira/browse/UIMA-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1256: -- Assignee: Bhavani Iyer UIMA-AS XMI serialization loses items appended to an FSList --- Key: UIMA-1256 URL: https://issues.apache.org/jira/browse/UIMA-1256 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Adam Lally Assignee: Bhavani Iyer I have an FSList that contains 2 FeatureStructures. I send it to a remote annotator that creates approximately 40 new FeatureStructures and appends them to the end of the FSList. It also adds these new FSs to the indexes. When I use xmi serialization, the CAS comes back without the new FSs having been added to the FSList, although I do see them in the indexes. When I use binary serialization, all works fine. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1256) UIMA-AS XMI serialization loses items appended to an FSList
[ https://issues.apache.org/jira/browse/UIMA-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1256: --- Attachment: UIMA-1256.patch The list FS nodes were not properly mapped to the feature structure that the list FS was a feature of during deserialization and hence when the list FS was modfied the encompassing FS was not serialized during delta XMI serialization. UIMA-AS XMI serialization loses items appended to an FSList --- Key: UIMA-1256 URL: https://issues.apache.org/jira/browse/UIMA-1256 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.2.2 Reporter: Adam Lally Assignee: Bhavani Iyer Attachments: UIMA-1256.patch I have an FSList that contains 2 FeatureStructures. I send it to a remote annotator that creates approximately 40 new FeatureStructures and appends them to the end of the FSList. It also adds these new FSs to the indexes. When I use xmi serialization, the CAS comes back without the new FSs having been added to the FSList, although I do see them in the indexes. When I use binary serialization, all works fine. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1207) Support for Delta CAS format in binary (blob) serialization
[ https://issues.apache.org/jira/browse/UIMA-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1207: --- Attachment: UIMA-1207.patch Please refer to org.apache.uima.cas.impl.CASSerializer.java for a description of the binary delta CAS format. Support for Delta CAS format in binary (blob) serialization --- Key: UIMA-1207 URL: https://issues.apache.org/jira/browse/UIMA-1207 Project: UIMA Issue Type: New Feature Components: Core Java Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1207.patch In order to reduce the serialization overhead, UIMA-AS provides the option of using binary serialization Providing the ability to allow a service to serialize only the changes made to the CAS will further reduce this overhead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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-2a.patch This patch replaces UIMA-1129-2.patch. It contains : - support for Delta CAS serialization of modified non-shared multivalued feature which requires serialization of the encompassing FS. - fixed bug in delta cas serialization when the CAS has not been modified in any way. - added a test cas for the above 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-2a.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] Created: (UIMA-1168) Use Delta CAS serialization to reduce overhead of remote service calls
Use Delta CAS serialization to reduce overhead of remote service calls -- Key: UIMA-1168 URL: https://issues.apache.org/jira/browse/UIMA-1168 Project: UIMA Issue Type: New Feature Components: Async Scaleout Reporter: Bhavani Iyer Assignee: Bhavani Iyer Make use of Delta CAS XMI format when serializing the CAS when calling a remote service per the requirements discussed here: [http://cwiki.apache.org/UIMA/reducing-overhead-for-remote-service-calls.html] Older servicea and client that are not aware of Delta CAS should be supported. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1168) Use Delta CAS serialization to reduce overhead of remote service calls
[ https://issues.apache.org/jira/browse/UIMA-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1168: --- Attachment: UIMA-1168-uimaj-as-core.patch UIMA-1168-uimaj-as-activemq.patch Contains implementation for using Delta CAS serialization when calling a remote service Use Delta CAS serialization to reduce overhead of remote service calls -- Key: UIMA-1168 URL: https://issues.apache.org/jira/browse/UIMA-1168 Project: UIMA Issue Type: New Feature Components: Async Scaleout Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1168-uimaj-as-activemq.patch, UIMA-1168-uimaj-as-core.patch Make use of Delta CAS XMI format when serializing the CAS when calling a remote service per the requirements discussed here: [http://cwiki.apache.org/UIMA/reducing-overhead-for-remote-service-calls.html] Older servicea and client that are not aware of Delta CAS should be supported. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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-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-1.patch This patch replaces the previous patch. It includes modifications made to address issues with the previous patch: - modifiedPreexisitngFS is initialized only when trackingMark is set. - renamed currentMark variable to trackingMark. - fixed javadoc comments. 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.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] Commented: (UIMA-1129) XMI serialization support for delta CAS
[ https://issues.apache.org/jira/browse/UIMA-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12625520#action_12625520 ] Bhavani Iyer commented on UIMA-1129: [ Show » ] My comments below: Thilo Goetz - 25/Aug/08 01:55 AM Some things I noticed looking at the patch: bq.* I thought this option would be enabled by a performance tuning option. I don't see that in the patch, maybe I missed it. The primary use for this is to enable a serivce to return a delta CAS. The service may reply with a complete CAS or with delta CAS depending on what format the client will accept. So enabling delta CAS is per request and not a global setting. bq.* There should be a boolean member variable deltaCasEnabled or something like that. This should be used in the code for checking this condition, so it's clear what's going on (and easier to change in case the implementation changes). The idea here was that the same design initially used to support delta CAS would be used to support journalling as well. When journalling, there will be multiple markers created to track activity per component. bq. It's also faster. Could you please clarify. Are you saying checking a boolean is faster than checking if an object reference is null ? bq.* this.svd.modifiedPreexistingFSs should only be initialised if deltaCasEnabled. We want to keep the CAS reset overhead as small as possible. Good point. Will do. bq.* There should be no public createMarker() API, see above. As explained above, required when a service needs to send a delta cas in the reply to a particular request. bq.* What's the point of having a marker interface if the XmiCasSerializer uses the MarkerImpl? Either make the interface so specific that the XmiCasSerializer can use it, or dispense with the interface altogether. I would vote for not having public interfaces for this. In the CAS you insert a new public API, then say don't use it. Why? Just keep this implementation internal. There is an example of creating and using the Marker object in the testcase. Applications will use the public interface . In the framework code I used the impl for efficiency . 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.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-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.patch Initial implementation of Delta CAS XMI serialization. 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.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] Created: (UIMA-1129) XMI serialization support for delta CAS
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 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-1096) Incorrect metaData returned when deployed as a separate process
[ https://issues.apache.org/jira/browse/UIMA-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1096: --- Attachment: UIMA-1096.patch Fixed the inconsistencies described. One clarification - the default value for mutiple references allowed is false. Incorrect metaData returned when deployed as a separate process --- Key: UIMA-1096 URL: https://issues.apache.org/jira/browse/UIMA-1096 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Burn Lewis Attachments: UIMA-1096.patch Comparing the getMeta reply from a service deployed as a separate C++ process with that from one deployed via JNI I see the following: 1) A typePriority index key is changed: fsIndexKey typePriority/ /fsIndexKey becomes: fsIndexKey featureName /featureName comparatorstandard/comparator /fsIndexKey 2) Invalid xml chars are not escaped, e.g. description NAMED gt; NOMINAL gt; PRONOMINAL./description becomes description NAMED NOMINAL PRONOMINAL./description 3) The default of multipleReferencesAllowedtrue/multipleReferencesAllowed is inserted in many featureDescriptions 4) These may be bugs in the JNI output: both typePriorities and operationalProperties are only in the JNI reply. 5) First 2 lines are missing the encoding xmlns attributes: ?xml version=1.0 encoding=UTF-8? analysisEngineMetaData xmlns=http://uima.apache.org/resourceSpecifier; -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1096) Incorrect metaData returned when deployed as a separate process
[ https://issues.apache.org/jira/browse/UIMA-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1096: -- Assignee: Bhavani Iyer Incorrect metaData returned when deployed as a separate process --- Key: UIMA-1096 URL: https://issues.apache.org/jira/browse/UIMA-1096 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Burn Lewis Assignee: Bhavani Iyer Attachments: UIMA-1096.patch Comparing the getMeta reply from a service deployed as a separate C++ process with that from one deployed via JNI I see the following: 1) A typePriority index key is changed: fsIndexKey typePriority/ /fsIndexKey becomes: fsIndexKey featureName /featureName comparatorstandard/comparator /fsIndexKey 2) Invalid xml chars are not escaped, e.g. description NAMED gt; NOMINAL gt; PRONOMINAL./description becomes description NAMED NOMINAL PRONOMINAL./description 3) The default of multipleReferencesAllowedtrue/multipleReferencesAllowed is inserted in many featureDescriptions 4) These may be bugs in the JNI output: both typePriorities and operationalProperties are only in the JNI reply. 5) First 2 lines are missing the encoding xmlns attributes: ?xml version=1.0 encoding=UTF-8? analysisEngineMetaData xmlns=http://uima.apache.org/resourceSpecifier; -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1072) Remove call to Java logger at service initialization start
Remove call to Java logger at service initialization start --- Key: UIMA-1072 URL: https://issues.apache.org/jira/browse/UIMA-1072 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer There could be a race condition and the Java logger is called before the UimacppServiceController is ready to handle these. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1072) Remove call to Java logger at service initialization start
[ https://issues.apache.org/jira/browse/UIMA-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1072: --- Attachment: UIMA-1072.patch Remove call to Java logger at service initialization start --- Key: UIMA-1072 URL: https://issues.apache.org/jira/browse/UIMA-1072 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1072.patch There could be a race condition and the Java logger is called before the UimacppServiceController is ready to handle these. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1066) Incorrect property name TimeInProcessCAS in reply message
[ https://issues.apache.org/jira/browse/UIMA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1066: --- Attachment: UIMA-1066.patch Incorrect property name TimeInProcessCAS in reply message - Key: UIMA-1066 URL: https://issues.apache.org/jira/browse/UIMA-1066 Project: UIMA Issue Type: Bug Reporter: Bhavani Iyer Attachments: UIMA-1066.patch TimeInProcessCAS has incorrect case. Look up is case sensitive. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1049) Uimacpp logging facility is not thread safe
[ https://issues.apache.org/jira/browse/UIMA-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1049: --- Attachment: UIMA-1049-2.patch Please ignore previous patch. Uimacpp logging facility is not thread safe --- Key: UIMA-1049 URL: https://issues.apache.org/jira/browse/UIMA-1049 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1049-1.patch, UIMA-1049-2.patch, UIMA-1049.patch Multiple instances of a C++ annotator may be run when the C++ annotator is run within a CPM with multiple parallel pipelines or when the C++ annotator is deployed as a UIMA AS service configured to start multiple instances. In both cases, when the JNI interface to logging is used, the call to the logging facility results in the exception, Exception in thread pool-1-thread-2 and the log message is not written. The problem does not appear when the C++ service is run in the natively using the ActiveMQ C++ serivce wrapper since the wrapper implements its own synchronization for logging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1049) Uimacpp logging facility is not thread safe
[ https://issues.apache.org/jira/browse/UIMA-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1049: -- Assignee: Bhavani Iyer Uimacpp logging facility is not thread safe --- Key: UIMA-1049 URL: https://issues.apache.org/jira/browse/UIMA-1049 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Multiple instances of a C++ annotator may be run when the C++ annotator is run within a CPM with multiple parallel pipelines or when the C++ annotator is deployed as a UIMA AS service configured to start multiple instances. In both cases, when the JNI interface to logging is used, the call to the logging facility results in the exception, Exception in thread pool-1-thread-2 and the log message is not written. The problem does not appear when the C++ service is run in the natively using the ActiveMQ C++ serivce wrapper since the wrapper implements its own synchronization for logging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1049) Uimacpp logging facility is not thread safe
Uimacpp logging facility is not thread safe --- Key: UIMA-1049 URL: https://issues.apache.org/jira/browse/UIMA-1049 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Multiple instances of a C++ annotator may be run when the C++ annotator is run within a CPM with multiple parallel pipelines or when the C++ annotator is deployed as a UIMA AS service configured to start multiple instances. In both cases, when the JNI interface to logging is used, the call to the logging facility results in the exception, Exception in thread pool-1-thread-2 and the log message is not written. The problem does not appear when the C++ service is run in the natively using the ActiveMQ C++ serivce wrapper since the wrapper implements its own synchronization for logging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1049) Uimacpp logging facility is not thread safe
[ https://issues.apache.org/jira/browse/UIMA-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1049: --- Attachment: UIMA-1049.patch Added synchronization locks around calls to the registered loggers. Updated the JNI logging to properly set the JNI environment for the current thread. Uimacpp logging facility is not thread safe --- Key: UIMA-1049 URL: https://issues.apache.org/jira/browse/UIMA-1049 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-1049.patch Multiple instances of a C++ annotator may be run when the C++ annotator is run within a CPM with multiple parallel pipelines or when the C++ annotator is deployed as a UIMA AS service configured to start multiple instances. In both cases, when the JNI interface to logging is used, the call to the logging facility results in the exception, Exception in thread pool-1-thread-2 and the log message is not written. The problem does not appear when the C++ service is run in the natively using the ActiveMQ C++ serivce wrapper since the wrapper implements its own synchronization for logging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1039) Fix use of non thread safe calls service wrapper Update property names in reply message to be compatible with Java.
Fix use of non thread safe calls service wrapper Update property names in reply message to be compatible with Java. -- Key: UIMA-1039 URL: https://issues.apache.org/jira/browse/UIMA-1039 Project: UIMA Issue Type: Bug Reporter: Bhavani Iyer Call to uimacpp logger is not thread safe. Rename property TimeInAnalytic to TimeInProcessCas in reply message Add support for time to send reply messaage to the JMX statistics maintained by the wrapper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1039) Fix use of non thread safe calls service wrapper Update property names in reply message to be compatible with Java.
[ https://issues.apache.org/jira/browse/UIMA-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-1039: -- Assignee: Bhavani Iyer Fix use of non thread safe calls service wrapper Update property names in reply message to be compatible with Java. -- Key: UIMA-1039 URL: https://issues.apache.org/jira/browse/UIMA-1039 Project: UIMA Issue Type: Bug Reporter: Bhavani Iyer Assignee: Bhavani Iyer Call to uimacpp logger is not thread safe. Rename property TimeInAnalytic to TimeInProcessCas in reply message Add support for time to send reply messaage to the JMX statistics maintained by the wrapper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1039) Fix use of non thread safe calls service wrapper Update property names in reply message to be compatible with Java.
[ https://issues.apache.org/jira/browse/UIMA-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-1039: --- Attachment: UMA-1039-1.patch Removed references to SendTime . Fix use of non thread safe calls service wrapper Update property names in reply message to be compatible with Java. -- Key: UIMA-1039 URL: https://issues.apache.org/jira/browse/UIMA-1039 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Fix For: 2.2C Attachments: UMA-1039-1.patch, UMA-1039.patch Call to uimacpp logger is not thread safe. Rename property TimeInAnalytic to TimeInProcessCas in reply message Add support for time to send reply messaage to the JMX statistics maintained by the wrapper. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-968) Service wrapper needs to send initialization success/failure message to Java controller
[ https://issues.apache.org/jira/browse/UIMA-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-968: -- Attachment: UIMA-968-2.patch Previous patch has a bug in reporting exceptions when the service wrapper is run in native mode, that is, not from Java. Service wrapper needs to send initialization success/failure message to Java controller --- Key: UIMA-968 URL: https://issues.apache.org/jira/browse/UIMA-968 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-968-1.patch, UIMA-968-2.patch, UIMA-968.patch In order for the Java controller to provide synchronous interface to C++ service initialization, the wrapper must send a success or failure message on completion of initialization. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-790) Move uimacpp-as service wrapper to uimacpp
[ https://issues.apache.org/jira/browse/UIMA-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586881#action_12586881 ] Bhavani Iyer commented on UIMA-790: --- The overview and setup page needs to be updated with respect to the native C++ service wrapper. Move uimacpp-as service wrapper to uimacpp -- Key: UIMA-790 URL: https://issues.apache.org/jira/browse/UIMA-790 Project: UIMA Issue Type: Task Components: C++ Framework Affects Versions: 2.2.2 Reporter: Eddie Epstein Assignee: Eddie Epstein Attachments: UIMA-790-2.patch, UIMA-790-3.patch, UIMA-790.patch, UMA-790-1.patch The uimacpp-as service wrapper should be maintained in the uimacpp project. It is unusable and cannot be built without uimacpp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-923) update the run examples scripts to use XMI format of CAS.
[ https://issues.apache.org/jira/browse/UIMA-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-923: -- Attachment: UIMA-923-1.patch updated to use XMI format of the input CAS. update the run examples scripts to use XMI format of CAS. - Key: UIMA-923 URL: https://issues.apache.org/jira/browse/UIMA-923 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Fix For: 2.2.2 Attachments: UIMA-923-1.patch, UIMA-923.patch Replace XCAS CAS inputs with XMI CAS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-968) Service wrapper needs to send initialization success/failure message to Java controller
Service wrapper needs to send initialization success/failure message to Java controller --- Key: UIMA-968 URL: https://issues.apache.org/jira/browse/UIMA-968 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer In order for the Java controller to provide synchronous interface to C++ service initialization, the wrapper must send a success or failure message on completion of initialization. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-967) UimacppServiceController service startup is not synchronous
UimacppServiceController service startup is not synchronous Key: UIMA-967 URL: https://issues.apache.org/jira/browse/UIMA-967 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer The service startup code does not wait for properly confirm that service startup success or failure. It needs to be reeceive a initialization success/failure message from C++ process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-967) UimacppServiceController service startup is not synchronous
[ https://issues.apache.org/jira/browse/UIMA-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-967: - Assignee: Bhavani Iyer UimacppServiceController service startup is not synchronous Key: UIMA-967 URL: https://issues.apache.org/jira/browse/UIMA-967 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Assignee: Bhavani Iyer The service startup code does not wait for properly confirm that service startup success or failure. It needs to be reeceive a initialization success/failure message from C++ process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-967) UimacppServiceController service startup is not synchronous
[ https://issues.apache.org/jira/browse/UIMA-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-967: -- Attachment: UIMA-967.patch This will only work with the C++ service wrapper with a fix for UIMA-968. The controller will now wait to receive the C++ service initaliziation status message through socket connection. UimacppServiceController service startup is not synchronous Key: UIMA-967 URL: https://issues.apache.org/jira/browse/UIMA-967 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-967.patch The service startup code does not wait for properly confirm that service startup success or failure. It needs to be reeceive a initialization success/failure message from C++ process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-968) Service wrapper needs to send initialization success/failure message to Java controller
[ https://issues.apache.org/jira/browse/UIMA-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-968: -- Attachment: UIMA-968.patch The service wrapper reports initialization status via socket connection to the Java Uimacpp service controller. This requires Java UIMA AS which includes the fix for JIRA issue UIMA-967. Service wrapper needs to send initialization success/failure message to Java controller --- Key: UIMA-968 URL: https://issues.apache.org/jira/browse/UIMA-968 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-968.patch In order for the Java controller to provide synchronous interface to C++ service initialization, the wrapper must send a success or failure message on completion of initialization. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-968) Service wrapper needs to send initialization success/failure message to Java controller
[ https://issues.apache.org/jira/browse/UIMA-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-968: -- Attachment: UIMA-968-1.patch Previous patch was invalid. Service wrapper needs to send initialization success/failure message to Java controller --- Key: UIMA-968 URL: https://issues.apache.org/jira/browse/UIMA-968 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Assignee: Bhavani Iyer Attachments: UIMA-968-1.patch, UIMA-968.patch In order for the Java controller to provide synchronous interface to C++ service initialization, the wrapper must send a success or failure message on completion of initialization. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-886) Support fro fast GETMETA
[ https://issues.apache.org/jira/browse/UIMA-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer reassigned UIMA-886: - Assignee: Bhavani Iyer 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 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.
[jira] Updated: (UIMA-886) Support fro fast GETMETA
[ https://issues.apache.org/jira/browse/UIMA-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-886: -- Attachment: UIMA-886.patch The service wrapper creates one MessageConsumer to handle getMeta requests exclusively. One or more MessagConsumers handle ProcessCas and CPC request based on the numberOfInstance parameter. These MessageConsumer register a message selector that sets a filter on the request sent to the consumers. 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 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.
[jira] Updated: (UIMA-948) cleanup warnings generated by deployCppService build
[ https://issues.apache.org/jira/browse/UIMA-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-948: -- Attachment: UIMA-948.patch cleanup warnings generated by deployCppService build - Key: UIMA-948 URL: https://issues.apache.org/jira/browse/UIMA-948 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Attachments: UIMA-948.patch cleanup warnings generated by deployCppService build -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-948) cleanup warnings generated by deployCppService build
cleanup warnings generated by deployCppService build - Key: UIMA-948 URL: https://issues.apache.org/jira/browse/UIMA-948 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer cleanup warnings generated by deployCppService build -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-790) Move uimacpp-as service wrapper to uimacpp
[ https://issues.apache.org/jira/browse/UIMA-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-790: -- Attachment: UIMA-790-2.patch Added debug build of Active MQ CPP client library. Move uimacpp-as service wrapper to uimacpp -- Key: UIMA-790 URL: https://issues.apache.org/jira/browse/UIMA-790 Project: UIMA Issue Type: Task Components: C++ Framework Affects Versions: 2.2.2 Reporter: Eddie Epstein Assignee: Eddie Epstein Attachments: UIMA-790-2.patch, UIMA-790.patch, UMA-790-1.patch The uimacpp-as service wrapper should be maintained in the uimacpp project. It is unusable and cannot be built without uimacpp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-923) update the run examples scripts to use XMI format of CAS.
update the run examples scripts to use XMI format of CAS. - Key: UIMA-923 URL: https://issues.apache.org/jira/browse/UIMA-923 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Replace XCAS CAS inputs with XMI CAS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-790) Move uimacpp-as service wrapper to uimacpp
[ https://issues.apache.org/jira/browse/UIMA-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-790: -- Attachment: UIMA-790-3.patch Updated the Linux build to include the ActiveMQ based service wrapper Move uimacpp-as service wrapper to uimacpp -- Key: UIMA-790 URL: https://issues.apache.org/jira/browse/UIMA-790 Project: UIMA Issue Type: Task Components: C++ Framework Affects Versions: 2.2.2 Reporter: Eddie Epstein Assignee: Eddie Epstein Attachments: UIMA-790-2.patch, UIMA-790-3.patch, UIMA-790.patch, UMA-790-1.patch The uimacpp-as service wrapper should be maintained in the uimacpp project. It is unusable and cannot be built without uimacpp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-923) update the run examples scripts to use XMI format of CAS.
[ https://issues.apache.org/jira/browse/UIMA-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-923: -- Attachment: UIMA-923.patch update the run examples scripts to use XMI format of CAS. - Key: UIMA-923 URL: https://issues.apache.org/jira/browse/UIMA-923 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Attachments: UIMA-923.patch Replace XCAS CAS inputs with XMI CAS. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-913) cleanup and simplify C++ service wrapper implementation
cleanup and simplify C++ service wrapper implementation --- Key: UIMA-913 URL: https://issues.apache.org/jira/browse/UIMA-913 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Some cleanup and simplificaiton of code that handles service initialization and manages ActivMQ JMS connection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-913) cleanup and simplify C++ service wrapper implementation
[ https://issues.apache.org/jira/browse/UIMA-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-913: -- Attachment: UIMA-913.patch cleanup and simplify C++ service wrapper implementation --- Key: UIMA-913 URL: https://issues.apache.org/jira/browse/UIMA-913 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Attachments: UIMA-913.patch Some cleanup and simplificaiton of code that handles service initialization and manages ActivMQ JMS connection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-790) Move uimacpp-as service wrapper to uimacpp
[ https://issues.apache.org/jira/browse/UIMA-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-790: -- Attachment: UMA-790-1.patch Added service wrapper and activemq library to buildsdk script. Move uimacpp-as service wrapper to uimacpp -- Key: UIMA-790 URL: https://issues.apache.org/jira/browse/UIMA-790 Project: UIMA Issue Type: Task Components: C++ Framework Affects Versions: 2.2.2 Reporter: Eddie Epstein Assignee: Eddie Epstein Attachments: UIMA-790.patch, UMA-790-1.patch The uimacpp-as service wrapper should be maintained in the uimacpp project. It is unusable and cannot be built without uimacpp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-881) runAECpp should output XMI
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 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.
[jira] Updated: (UIMA-790) Move uimacpp-as service wrapper to uimacpp
[ https://issues.apache.org/jira/browse/UIMA-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-790: -- Attachment: UIMA-790.patch The VC project that builds the servcie wrapper has been updated and the project added to the uimacpp solution. Move uimacpp-as service wrapper to uimacpp -- Key: UIMA-790 URL: https://issues.apache.org/jira/browse/UIMA-790 Project: UIMA Issue Type: Task Components: C++ Framework Affects Versions: 2.2.2 Reporter: Eddie Epstein Assignee: Eddie Epstein Attachments: UIMA-790.patch The uimacpp-as service wrapper should be maintained in the uimacpp project. It is unusable and cannot be built without uimacpp. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-881) runAECpp should output XMI
[ https://issues.apache.org/jira/browse/UIMA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-881: -- Attachment: UIMA-881.patch runAECpp outputs XMI. 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 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.
[jira] Updated: (UIMA-798) Operational properties are not being handled
[ https://issues.apache.org/jira/browse/UIMA-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-798: -- Attachment: UIMA-798.patch Added Operational properties to AnalysisEngineMetaData and added support for handling this XML element when parsing the AE descriptor. Operational properties are not being handled Key: UIMA-798 URL: https://issues.apache.org/jira/browse/UIMA-798 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer Attachments: UIMA-798.patch The C++ framework need to support operational properties element in descriptors. This is required for C++ service and application support for CAS multiplier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-886) Support fro fast GETMETA
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 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.
[jira] Created: (UIMA-797) JMX timing statistics reported by services
JMX timing statistics reported by services -- Key: UIMA-797 URL: https://issues.apache.org/jira/browse/UIMA-797 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer 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.
[jira] Created: (UIMA-798) Operational properties are not being handled
Operational properties are not being handled Key: UIMA-798 URL: https://issues.apache.org/jira/browse/UIMA-798 Project: UIMA Issue Type: Bug Components: C++ Framework Reporter: Bhavani Iyer The C++ framework need to support operational properties element in descriptors. This is required for C++ service and application support for CAS multiplier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-748) Multiple notfications sent to registered listeners.
[ https://issues.apache.org/jira/browse/UIMA-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-748: -- Attachment: UIMA-748-1.patch Previous patch did not match up. Multiple notfications sent to registered listeners. --- Key: UIMA-748 URL: https://issues.apache.org/jira/browse/UIMA-748 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Attachments: UIMA-748-1.patch, UIMA-748.patch Multiple notfications sent to registered listeners. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-748) Multiple notfications sent to registered listeners.
Multiple notfications sent to registered listeners. --- Key: UIMA-748 URL: https://issues.apache.org/jira/browse/UIMA-748 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Multiple notfications sent to registered listeners. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-748) Multiple notfications sent to registered listeners.
[ https://issues.apache.org/jira/browse/UIMA-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-748: -- Attachment: UIMA-748.patch Fixed notification. Multiple notfications sent to registered listeners. --- Key: UIMA-748 URL: https://issues.apache.org/jira/browse/UIMA-748 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Attachments: UIMA-748.patch Multiple notfications sent to registered listeners. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-676) Performance problem with XMI serialization implementation of string data normalization
[ https://issues.apache.org/jira/browse/UIMA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-676: -- Attachment: UIMA-676.patch Modified to improve performance of scanning and escaping xml special characters in string Performance problem with XMI serialization implementation of string data normalization --- Key: UIMA-676 URL: https://issues.apache.org/jira/browse/UIMA-676 Project: UIMA Issue Type: Bug Components: C++ Framework Affects Versions: 2.2.1 Reporter: Bhavani Iyer Attachments: UIMA-676.patch The XMI serialzation used UnicodeString.findAndReplace(...) to escape XML special characters which is not efficient and should use the utilities available in Xerces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-676) Performance problem with XMI serialization implementation of string data normalization
Performance problem with XMI serialization implementation of string data normalization --- Key: UIMA-676 URL: https://issues.apache.org/jira/browse/UIMA-676 Project: UIMA Issue Type: Bug Components: C++ Framework Affects Versions: 2.2.1 Reporter: Bhavani Iyer The XMI serialzation used UnicodeString.findAndReplace(...) to escape XML special characters which is not efficient and should use the utilities available in Xerces. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-567) Support for application specified logging facility
Support for application specified logging facility -- Key: UIMA-567 URL: https://issues.apache.org/jira/browse/UIMA-567 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Bhavani Iyer .Applications embedding the UIMA C++ runtine need to be able to route log messages generated by the C++ framework and by UIMA C++ componenets to logging facilities used by the application. Currently, the UIMA C++ SDK only supports logging to a file and routing log messages to Java if called from a Java application. To support this requirement to support custom loggers, the SDK will be extended as follows: 1) define a Logger interface to be implemented by users to wrap the application specific logger. 2) provide APIs in the ResourceManager class to register/unregister Loggers. The ResourceManager will maintain reference to all the registered loggers. 3) modify the LogFacility class to route the log messages to all registered loggers. 4) reimplement the current logging to file and java logger to conform to this design. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-371) XMI serialization to UIMA C++
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-371: -- Attachment: UIMA-371-1.patch Fix for memory leak in XmiSerializationSharedData. The destructor was not deleting vector of OOTS array elements. XMI serialization to UIMA C++ - Key: UIMA-371 URL: https://issues.apache.org/jira/browse/UIMA-371 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Eddie Epstein Assignee: Eddie Epstein Fix For: 2.2C Attachments: UIMA-371-1.patch, UIMA-371.patch, uimacpp-xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.zip, xmi_bytearray.patch In order to comply to the UIMA standard for CAS data, Bhavani Iyer has been working on XMI serialization support for UIMA C++. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-371) XMI serialization to UIMA C++
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-371: -- Attachment: UIMA-371.patch The patch fixes the handling of FSList type features to be compatible with the Java XMI output and to support multiple references allowed attribute. XMI serialization to UIMA C++ - Key: UIMA-371 URL: https://issues.apache.org/jira/browse/UIMA-371 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Eddie Epstein Assignee: Eddie Epstein Fix For: 2.2C Attachments: UIMA-371.patch, uimacpp-xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.zip, xmi_bytearray.patch In order to comply to the UIMA standard for CAS data, Bhavani Iyer has been working on XMI serialization support for UIMA C++. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-423) Detect and fix memory leaks
[ https://issues.apache.org/jira/browse/UIMA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-423: -- Attachment: UIMA-423-2.patch fix memory leak in XMLParser Detect and fix memory leaks --- Key: UIMA-423 URL: https://issues.apache.org/jira/browse/UIMA-423 Project: UIMA Issue Type: Bug Components: C++ Framework Affects Versions: 2.1, 2.2 Reporter: Bhavani Iyer Assignee: Eddie Epstein Attachments: UIMA-423-1.patch, UIMA-423-2.patch, UIMA-423.patch Fournd memory leaks in XMI serialization, exception handling, CAS. Memory leak detection in debug mode is currently disabled in the base code because of issues with malloc.h in Visual Studio 7. This appears to be fixed in VS 8. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-423) Detect and fix memory leaks
[ https://issues.apache.org/jira/browse/UIMA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-423: -- Attachment: UIMA-423-1.patch This patch contains fixes for: 1) AnnotatorContext::release(vectorstring*) was not freeing elements in the vector. 2) Some XMLParser methods were not not deleting XMLErrorHandler under error conditions. 3) Modified runAECpp to check that the input file / direcotory exists before instantiating an engine and cas. runAECppD will report a memory leak if run in debug mode with an invalid descriptor since the AnalysisEngine::createAnalysisEngine method releases auto ptrs before initialization is completed. 4) Cleaned up memory leaks in test cases - test_cas and test_engine still report leaks when run in debug mode. Detect and fix memory leaks --- Key: UIMA-423 URL: https://issues.apache.org/jira/browse/UIMA-423 Project: UIMA Issue Type: Bug Components: C++ Framework Affects Versions: 2.1, 2.2 Reporter: Bhavani Iyer Assignee: Eddie Epstein Attachments: UIMA-423-1.patch, UIMA-423.patch Fournd memory leaks in XMI serialization, exception handling, CAS. Memory leak detection in debug mode is currently disabled in the base code because of issues with malloc.h in Visual Studio 7. This appears to be fixed in VS 8. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-423) Detect and fix memory leaks
[ https://issues.apache.org/jira/browse/UIMA-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-423: -- Attachment: UIMA-423.patch This patch contains the following: 1) Memory leak detection enabled under MS VC++ 8 debug build. 2) Fixed leaks in: i. XMI serialization ii. CAS object destructor, createView() iii SofaStream iv. CodePage2UnicodeConverter and Unicode2CodePageConverter v. uima:::Exception::asString() vi. test programs -- test_sofa, test_primitivetypes, test_xcasdeserializatio and test_xmideserialization. Detect and fix memory leaks --- Key: UIMA-423 URL: https://issues.apache.org/jira/browse/UIMA-423 Project: UIMA Issue Type: Bug Components: C++ Framework Affects Versions: 2.1, 2.2 Reporter: Bhavani Iyer Assignee: Eddie Epstein Attachments: UIMA-423.patch Fournd memory leaks in XMI serialization, exception handling, CAS. Memory leak detection in debug mode is currently disabled in the base code because of issues with malloc.h in Visual Studio 7. This appears to be fixed in VS 8. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-423) Detect and fix memory leaks
Detect and fix memory leaks --- Key: UIMA-423 URL: https://issues.apache.org/jira/browse/UIMA-423 Project: UIMA Issue Type: Bug Components: C++ Framework Affects Versions: 2.1, 2.2 Reporter: Bhavani Iyer Fournd memory leaks in XMI serialization, exception handling, CAS. Memory leak detection in debug mode is currently disabled in the base code because of issues with malloc.h in Visual Studio 7. This appears to be fixed in VS 8. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-371) XMI serialization to UIMA C++
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-371: -- Attachment: xmi_bytearray.patch Had not checked the Grant license to ASF for inclusion in ASF works flag XMI serialization to UIMA C++ - Key: UIMA-371 URL: https://issues.apache.org/jira/browse/UIMA-371 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Eddie Epstein Assigned To: Eddie Epstein Fix For: 2.2 Attachments: uimacpp-xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.zip, xmi_bytearray.patch, xmi_bytearray.patch In order to comply to the UIMA standard for CAS data, Bhavani Iyer has been working on XMI serialization support for UIMA C++. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-371) XMI serialization to UIMA C++
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-371: -- Attachment: xmi_bytearray.patch Fixed xmi serialization of byte array to handle signed values. Added some checks to test for valid FeatureSructure object. XMI serialization to UIMA C++ - Key: UIMA-371 URL: https://issues.apache.org/jira/browse/UIMA-371 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Eddie Epstein Assigned To: Eddie Epstein Fix For: 2.2 Attachments: uimacpp-xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.zip, xmi_bytearray.patch In order to comply to the UIMA standard for CAS data, Bhavani Iyer has been working on XMI serialization support for UIMA C++. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-371) XMI serialization to UIMA C++
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-371: -- Attachment: uimacpp-xmi.patch Previous patch was not ignoring line ends XMI serialization to UIMA C++ - Key: UIMA-371 URL: https://issues.apache.org/jira/browse/UIMA-371 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Eddie Epstein Assigned To: Eddie Epstein Fix For: 2.2 Attachments: uimacpp-xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.zip In order to comply to the UIMA standard for CAS data, Bhavani Iyer has been working on XMI serialization support for UIMA C++. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-371) XMI serialization to UIMA C++
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-371: -- Attachment: uimacpp_xmi.zip uimacpp_xmi.patch The attached contains the implementation of C++ support for XMI serialization. the XMI code is a port of the XMI serialization code from the Apache Java distribution, combined with techniques used in XCAS serialization code from Apache C++ distribution. The patch contains fixes to the bugs listed below found while implementing the XMI serialization: a) removed assert statements which were preventing proper reporting of exceptions when loading an annotator dll which is not found in the path and on call to getIndex with an invalid index name. b) fixes to XMLParser methods to synch up with the schema. This is required for XMI test cases. c) Type name of ANNOTATION_BASE missing the namespace prefix. Fix required for XMI serialization to work properly. XMI serialization to UIMA C++ - Key: UIMA-371 URL: https://issues.apache.org/jira/browse/UIMA-371 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Eddie Epstein Assigned To: Eddie Epstein Fix For: 2.2 Attachments: uimacpp_xmi.patch, uimacpp_xmi.zip In order to comply to the UIMA standard for CAS data, Bhavani Iyer has been working on XMI serialization support for UIMA C++. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
