[
https://issues.apache.org/jira/browse/CTAKES-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620126#comment-13620126
]
Pei Chen commented on CTAKES-151:
---------------------------------
One alternative workaround/suggestion from the umls lex folks is for us to
instantiate a new LvgCmdApi() which should be a new read only connection to
their hsqldb;
instead of sharing it as an UIMA resources (which we're not taking advantage
anyway).
----
We will look into it and will let you know if we decide to modify the source
code.
If so, it will be included in the next (2014) release.
As for now, you can use multiple API instances within a single JVM for thread
safe.
Please see
http://lexsrv3.nlm.nih.gov/LexSysGroup/Projects/lvg/current/web/faq.html
Thank you!
-------------------------------------
Chris J Lu, Ph.D.
Senior Systems Architect
MSC/NLM/NIH
(E): l...@nlm.nih.gov
-------------------------------------
> LVG is not thread safe for multiple instances inside of a single JVM.
> ---------------------------------------------------------------------
>
> Key: CTAKES-151
> URL: https://issues.apache.org/jira/browse/CTAKES-151
> Project: cTAKES
> Issue Type: Sub-task
> Components: ctakes-lvg
> Affects Versions: future enhancement, 3.0-incubating, 3.1-incubating
> Reporter: Kim Ebert
> Priority: Critical
> Attachments: lvg_static_fix.patch
>
>
> The LVG library is not thread safe. It uses global variables, so between
> multiple instances, the data will become corrupted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
