[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 ] Eddie Epstein updated UIMA-1049: Fix Version/s: 2.2C Must fix for first release > 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 > Fix For: 2.2C > > 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] 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] 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-1.patch The JNIEnv handle is not set correctly when calling Java log method. > 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.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] 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.
