You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Thilo Goetz (JIRA)" <ui...@incubator.apache.org> on 2008/06/10 11:35:45 UTC
[jira] Created: (UIMA-1069) Model file is not loaded correctly if
tagger is deployed more than once in same AE
Model file is not loaded correctly if tagger is deployed more than once in same AE
----------------------------------------------------------------------------------
Key: UIMA-1069
URL: https://issues.apache.org/jira/browse/UIMA-1069
Project: UIMA
Issue Type: Bug
Components: Sandbox-Tagger
Affects Versions: 2.2.2S
Reporter: Thilo Goetz
Assignee: Thilo Goetz
Priority: Minor
Fix For: 2.3S
The model resource in the tagger is implemented such that it just returns the InputStream for the model file. If the tagger is deployed more than once into the same AE, this leads to an IOException as both instances try to load their model from the same input stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1069) Model file is not loaded correctly if
tagger is deployed more than once in same AE
Posted by "Thilo Goetz (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thilo Goetz closed UIMA-1069.
-----------------------------
Resolution: Fixed
> Model file is not loaded correctly if tagger is deployed more than once in same AE
> ----------------------------------------------------------------------------------
>
> Key: UIMA-1069
> URL: https://issues.apache.org/jira/browse/UIMA-1069
> Project: UIMA
> Issue Type: Bug
> Components: Sandbox-Tagger
> Affects Versions: 2.2.2S
> Reporter: Thilo Goetz
> Assignee: Thilo Goetz
> Priority: Minor
> Fix For: 2.3S
>
>
> The model resource in the tagger is implemented such that it just returns the InputStream for the model file. If the tagger is deployed more than once into the same AE, this leads to an IOException as both instances try to load their model from the same input stream.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.