[gme-users] Need help in registering Java component in GME
peter.volgyesi at vanderbilt.edu
Fri Jun 18 11:40:41 CDT 2010
This is the problem. GME is a 32 bit application, it cannot host a 64
bit JVM dll. Install a 32 bit JVM (it can be installed side-by-sde
with the existing 64 bit JVM).
On Fri, Jun 18, 2010 at 11:17 AM, Raghu Vamsi Chavali
<rchavali at purdue.edu> wrote:
> Hi Peter,
> My OS is 64 bit and JVM is also 64bit.
> Version info:
> java version "1.6.0_17"
> Java<TM> SE Runtime Environment <build 1.6.0_17-b04>
> Java HotSpot<TM> 64-Bit Server VM <build 14.3-b01, mixed mode>
> On 6/18/2010 11:37 AM, Peter Volgyesi wrote:
>> Is this a 64bit OS ? If yes, do you have a 32 bit or 64 bit JVM installed ?
>> Peter Volgyesi
>> Research Scientist
>> Vanderbilt University, ISIS
>> Office: +1 (615) 322-1018
>> Cell: +1 (615) 294-6520
>> On Fri, Jun 18, 2010 at 10:08 AM, Raghu Vamsi Chavali
>> <rchavali at purdue.edu> wrote:
>>> Hi all,
>>> I am currently facing an issue with Java Interpreters. I was going through
>>> the list of issues on JIRA and found a similar one. But the solution
>>> suggested there does not help me. My problem is as follows.
>>> As per the userguide, I have registered the TestBONComponent and am trying
>>> to test the same on GME. It results in " Error loading java. Cannot find
>>> jvm.dll" error being thrown. My java installation seems to be fine as other
>>> applications depending on it run just fine.
>>> I browsed through the previous issues list on this site and came across the
>>> following issue: (http://repo.isis.vanderbilt.edu/JIRA/browse/GME-120)
>>> After registering TestBONComponent, and enabling in GME, clicking Java icon
>>> results in "Error Loading java. Cannot query jvm.dll path from registry". I
>>> have tried setting the JavaClassPath to both gme.jar and jvm.dll locations,
>>> but no combination seems to work. I also added jvm.dll to Windows Path, but
>>> still get this error.
>>> The reply to the above issue was the following:
>>> I don't think there's a JIRA issue, but the source has already been fixed.
>>> The problem was the original code for loading the jvm.dll hardcoded in 1.4
>>> instead of querying the system for the current version. And it didn't become
>>> apparent until people that did not have any 1.4.x version installed tried to
>>> run a Java Component. People who had both 1.4 and 1.5 installed were unable
>>> to reproduce the bug.
>>> Please suggest what else could be wrong with my installation.
>>> Raghu Vamsi Chavali
>>> Purdue University
>>> gme-users mailing list
>>> gme-users at list.isis.vanderbilt.edu
>> gme-users mailing list
>> gme-users at list.isis.vanderbilt.edu
> gme-users mailing list
> gme-users at list.isis.vanderbilt.edu
More information about the gme-users