You are viewing a plain text version of this content. The canonical link for it is here.

Posted to pylucene-dev@lucene.apache.org by "Martin (JIRA)" <ji...@apache.org> on 2013/11/04 13:58:21 UTC

[jira] [Updated] (PYLUCENE-28) JCC reuses JVM instances in impl, if compile() is called twice.

     [ https://issues.apache.org/jira/browse/PYLUCENE-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin updated PYLUCENE-28:
---------------------------

    Attachment: jvm_instance_check.patch

> JCC reuses JVM instances in impl, if compile() is called twice.
> ---------------------------------------------------------------
>
>                 Key: PYLUCENE-28
>                 URL: https://issues.apache.org/jira/browse/PYLUCENE-28
>             Project: PyLucene
>          Issue Type: Improvement
>         Environment: jcc-svn-head (2.18-pre)
>            Reporter: Martin
>            Priority: Blocker
>              Labels: patch
>         Attachments: jvm_instance_check.patch
>
>
> If you import jcc.cpp to call compile yourself (a wrapped setup.py script to generate a wrapper on the fly, which seems to be a common use case), the current version complains about the JVM already being initialized before.
> The patch first checks for a running instance and creates one, if none is being found.
> For myself, this is a blocker, since it raises otherwise.
> Best, 
> Martin



--
This message was sent by Atlassian JIRA
(v6.1#6144)