[kepler-dev] [Bug 4985] problem with workflows using Rexpression on Windows XP

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Fri May 7 14:06:38 PDT 2010


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4985

jianwu <jianwu at sdsc.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jianwu at sdsc.edu

--- Comment #1 from jianwu <jianwu at sdsc.edu> 2010-05-07 14:06:37 PDT ---
I found two workflows can not be executed on Windows 7 64 bit:
Kepler-2.0.0-Demos\demos\R\r-2.0.0\demos\R\localFile_to_dataFrame_R and
sampling_occurrenceData_ R.

First of all, many workflows still use property("KEPLER") which should be
changed to property("DEMODIR").

For workflow "sampling_occurrenceData_ R", it tried to use
property("KEPLER")+"/lib/testdata/garp/DataPoints.txt". I finally found the
file at Kepler-2.0.0-Demos\demos\R\data\garp directory. So it probably should
be property("DEMODIR")+"/data/garp/DataPoints.txt"

After I manually pointed to the correct dir, these two workflows work for me.

I also tried workflows in Kepler-2.0.0-Demos\demos\R\r-2.0.0\demos\JRI
directory, the whole Kepler just quit with the following message in the
console. It makes sense that the dll doesn't work for 64 bit machine. But just
quitting Kepler is too unfriendly.


     [null] Cannot find JRI native library!
     [null] Please make sure that the JRI native library is in a directory
liste
d in java.library.path.
     [null]
     [null] java.lang.UnsatisfiedLinkError: C:\Program
Files\Kepler-2.0-RC2\r-2.
0.0\lib\jri.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
     [null]     at java.lang.ClassLoader$NativeLibrary.load(Native Method)
     [null]     at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1753)
     [null]     at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1678)
     [null]     at java.lang.Runtime.loadLibrary0(Runtime.java:822)
     [null]     at java.lang.System.loadLibrary(System.java:993)
     [null]     at org.rosuda.JRI.Rengine.<clinit>(Rengine.java:19)
     [null]     at
org.ecoinformatics.seek.R.RExpression2._initializeRengine(REx
pression2.java:569)
     [null]     at
org.ecoinformatics.seek.R.RExpression2._fireUsingJRI(RExpress
ion2.java:547)
     [null]     at
org.ecoinformatics.seek.R.RExpression2.fire(RExpression2.java
:289)
     [null]     at ptolemy.actor.AtomicActor.iterate(AtomicActor.java:469)
     [null]     at
ptolemy.actor.sched.StaticSchedulingDirector.fire(StaticSched
ulingDirector.java:188)
     [null]     at ptolemy.actor.CompositeActor.fire(CompositeActor.java:458)
     [null]     at ptolemy.actor.Manager.iterate(Manager.java:749)
     [null]     at ptolemy.actor.Manager.execute(Manager.java:351)
     [null]     at ptolemy.actor.Manager.run(Manager.java:1162)
     [null]     at ptolemy.actor.Manager$3.run(Manager.java:1215)
Exception in thread "main" Java returned: 1
        at org.kepler.build.modules.ModulesTask.execute(ModulesTask.java:105)
        at org.kepler.build.runner.Kepler.main(Kepler.java:78)
Caused by: Java returned: 1
        at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108)
        at org.kepler.build.Run.runSuite(Run.java:298)
        at org.kepler.build.Run.run(Run.java:202)
        at org.kepler.build.modules.ModulesTask.execute(ModulesTask.java:101)
        ... 1 more
--- Nested Exception ---
Java returned: 1
        at org.apache.tools.ant.taskdefs.Java.execute(Java.java:108)
        at org.kepler.build.Run.runSuite(Run.java:298)
        at org.kepler.build.Run.run(Run.java:202)
        at org.kepler.build.modules.ModulesTask.execute(ModulesTask.java:101)
        at org.kepler.build.runner.Kepler.main(Kepler.java:78)




P.S.: Do the workflows in Kepler-2.0.0-Demos\demos\R\r-2.0.0\demos\JRI\problems
directory really have execution "problems"? This directory name is confusing.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the Kepler-dev mailing list