-
Re: ValueError: An error occurred while creating Java VMRoman Chyla 2012-05-04, 03:32
Yes, there is only one JDK on my system (fresh installation), and both
runs show it
python:
print j.System.getProperty("java.version")
1.6.0_24
java gives:
NOTE: Linux 3.2.0-2-amd64 amd64/Sun Microsystems Inc. 1.6.0_24
(64-bit)/cpus=2,threads=1,free=47600792,total=61276160
cat /usr/local/lib/python2.7/dist-packages/JCC-2.8-py2.7-linux-x86_64.egg/jcc/config.py
INCLUDES=['/usr/lib/jvm/java-6-openjdk-amd64//include',
'/usr/lib/jvm/java-6-openjdk-amd64//include/linux']
CFLAGS=['-fno-strict-aliasing', '-Wno-write-strings']
DEBUG_CFLAGS=['-O0', '-g', '-DDEBUG']
LFLAGS=['-L/usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64',
'-ljava', '-L/usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64/server',
'-ljvm', '-Wl,-rpath=/usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64/server']
IMPLIB_LFLAGS=[]
SHARED=True
VERSION="2.8"
roman
On Thu, May 3, 2012 at 8:58 PM, Andi Vajda <[EMAIL PROTECTED]> wrote:
>
> On Thu, 3 May 2012, Roman Chyla wrote:
>
>> We use JCC to run Java inside Python as well Python inside Java. I
>> have now discovered one interesting situation.
>>
>> I have a Hudson server that builds and tests our code. Hudson will
>> create its own python virtualenv (based on Python 2.7) and using it
>> builds JCC and Pylucene. Then Hudson also builds our own code (we
>> import pylucene and wrap solr with jcc). And it works great, all sorts
>> of unittests pass.
>>
>>
>> So I thought 'let me take JCC and Pylucene built by Hudson and install
>> it into my Python' (note: it is the same machine, so it should be
>> based on the same Python interpreter)
>
>
> But are the Java VMs the same ?
>
> Andi..
>
>
>>
>> While it works if I run the python code (that imports java),
>> Interestingly enough, it fails when I run the java (that imports
>> Python)
>>
>>
>> org.apache.jcc.PythonException: An error occurred while creating Java VM
>> Traceback (most recent call last):
>> File
>> "/dvt/workspace/montysolr/src/python/montysolr/tests/basic/bridge.py",
>> line 2, in <module>
>> from montysolr.initvm import montysolr_java as sj
>> File "/dvt/workspace/montysolr/src/python/montysolr/initvm.py", line
>> 48, in <module>
>> montysolr_java.initVM(os.pathsep.join([lucene.CLASSPATH,
>> solr_java.CLASSPATH, montysolr_java.CLASSPATH, _classpath]))
>> ValueError: An error occurred while creating Java VM
>>
>> at org.apache.jcc.PythonVM.instantiate(Native Method)
>> at invenio.montysolr.jni.PythonVMBridge.start(MontySolrVM.java:287)
>> at invenio.montysolr.jni.PythonVMBridge.start(MontySolrVM.java:277)
>> at
>> invenio.montysolr.jni.MontySolrVM.getBridge(MontySolrVM.java:161)
>>
>>
>> So, first I thought that I should blame the python virtualenv and that
>> I cannot re-use those eggs (ie. I have to build JCC and Pylucene
>> default Python). But in fact if I keep the JCC built by Hudson and
>> just replace the Pylucene, then it starts to work again. I can even
>> first compile our own project and include the 'broken' pylucene in it
>> (unittest fail). Then I replace just the pylucene and everything works
>> again.
>>
>> It is somewhat puzzling. I'd expect that if I use Hudson eggs that
>> they will either both work or both fail.
>>
>> So I thought this might be an early warning sign, something that needs
>> your attention. I am not sure how to proceed to analyze the problem.
>>
>> Thanks,
>>
>> roman
>>
>>
>>
>>
>> -----
>>
>> ldd for the libraries:
>>
>> rchyla@diana /dvt/workspace/pylucene_3_1_0 $ ldd
>>
>> /usr/local/lib/python2.7/dist-packages/JCC-2.8-py2.7-linux-x86_64.egg/jcc/_jcc.so
>> linux-vdso.so.1 => (0x00007fff7f378000)
>> libjava.so =>
>> /usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64/libjava.so
>> (0x00007f97a987f000)
>> libjvm.so =>
>> /usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64/server/libjvm.so
>> (0x00007f97a8cb7000)
>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>> (0x00007f97a8996000)
>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f97a8714000)
runs show it
python:
print j.System.getProperty("java.version")
1.6.0_24
java gives:
NOTE: Linux 3.2.0-2-amd64 amd64/Sun Microsystems Inc. 1.6.0_24
(64-bit)/cpus=2,threads=1,free=47600792,total=61276160
cat /usr/local/lib/python2.7/dist-packages/JCC-2.8-py2.7-linux-x86_64.egg/jcc/config.py
INCLUDES=['/usr/lib/jvm/java-6-openjdk-amd64//include',
'/usr/lib/jvm/java-6-openjdk-amd64//include/linux']
CFLAGS=['-fno-strict-aliasing', '-Wno-write-strings']
DEBUG_CFLAGS=['-O0', '-g', '-DDEBUG']
LFLAGS=['-L/usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64',
'-ljava', '-L/usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64/server',
'-ljvm', '-Wl,-rpath=/usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64/server']
IMPLIB_LFLAGS=[]
SHARED=True
VERSION="2.8"
roman
On Thu, May 3, 2012 at 8:58 PM, Andi Vajda <[EMAIL PROTECTED]> wrote:
>
> On Thu, 3 May 2012, Roman Chyla wrote:
>
>> We use JCC to run Java inside Python as well Python inside Java. I
>> have now discovered one interesting situation.
>>
>> I have a Hudson server that builds and tests our code. Hudson will
>> create its own python virtualenv (based on Python 2.7) and using it
>> builds JCC and Pylucene. Then Hudson also builds our own code (we
>> import pylucene and wrap solr with jcc). And it works great, all sorts
>> of unittests pass.
>>
>>
>> So I thought 'let me take JCC and Pylucene built by Hudson and install
>> it into my Python' (note: it is the same machine, so it should be
>> based on the same Python interpreter)
>
>
> But are the Java VMs the same ?
>
> Andi..
>
>
>>
>> While it works if I run the python code (that imports java),
>> Interestingly enough, it fails when I run the java (that imports
>> Python)
>>
>>
>> org.apache.jcc.PythonException: An error occurred while creating Java VM
>> Traceback (most recent call last):
>> File
>> "/dvt/workspace/montysolr/src/python/montysolr/tests/basic/bridge.py",
>> line 2, in <module>
>> from montysolr.initvm import montysolr_java as sj
>> File "/dvt/workspace/montysolr/src/python/montysolr/initvm.py", line
>> 48, in <module>
>> montysolr_java.initVM(os.pathsep.join([lucene.CLASSPATH,
>> solr_java.CLASSPATH, montysolr_java.CLASSPATH, _classpath]))
>> ValueError: An error occurred while creating Java VM
>>
>> at org.apache.jcc.PythonVM.instantiate(Native Method)
>> at invenio.montysolr.jni.PythonVMBridge.start(MontySolrVM.java:287)
>> at invenio.montysolr.jni.PythonVMBridge.start(MontySolrVM.java:277)
>> at
>> invenio.montysolr.jni.MontySolrVM.getBridge(MontySolrVM.java:161)
>>
>>
>> So, first I thought that I should blame the python virtualenv and that
>> I cannot re-use those eggs (ie. I have to build JCC and Pylucene
>> default Python). But in fact if I keep the JCC built by Hudson and
>> just replace the Pylucene, then it starts to work again. I can even
>> first compile our own project and include the 'broken' pylucene in it
>> (unittest fail). Then I replace just the pylucene and everything works
>> again.
>>
>> It is somewhat puzzling. I'd expect that if I use Hudson eggs that
>> they will either both work or both fail.
>>
>> So I thought this might be an early warning sign, something that needs
>> your attention. I am not sure how to proceed to analyze the problem.
>>
>> Thanks,
>>
>> roman
>>
>>
>>
>>
>> -----
>>
>> ldd for the libraries:
>>
>> rchyla@diana /dvt/workspace/pylucene_3_1_0 $ ldd
>>
>> /usr/local/lib/python2.7/dist-packages/JCC-2.8-py2.7-linux-x86_64.egg/jcc/_jcc.so
>> linux-vdso.so.1 => (0x00007fff7f378000)
>> libjava.so =>
>> /usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64/libjava.so
>> (0x00007f97a987f000)
>> libjvm.so =>
>> /usr/lib/jvm/java-6-openjdk-amd64//jre/lib/amd64/server/libjvm.so
>> (0x00007f97a8cb7000)
>> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
>> (0x00007f97a8996000)
>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f97a8714000)
