For some scripting project (mostly DB-access via JDBC,calling Oracle
SQL+PL/SQL)
on AIX 5.3 I am trying to decide between Jython 2.5 and JRuby 1.4.
My personal preference would probably be JRuby, but I have a little
worry
that JRuby is not fully supported on AIX, because the native
libraries (ffi,jni…) for AIX are missing.
My tests so far (calling SQL queries and stored procedures) have been
just fine,
but maybe I am missing something. Does anybody know of some issues with
JRuby
on AIX?
My tests so far (calling SQL queries and stored procedures) have been
just fine,
but maybe I am missing something. Does anybody know of some issues with
JRuby
on AIX?
Ther’s no outstanding issues for AIX that I know of, and we do
actually ship a jffi library (which is our only major native
dependency) for ppc-AIX. So I think you’ll probably be fine.
If you’re using AIX on something other than PPC, you could always
build the binary and contribute it back
Ther’s no outstanding issues for AIX that I know of, and we do
actually ship a jffi library (which is our only major native
dependency) for ppc-AIX. So I think you’ll probably be fine.
If you’re using AIX on something other than PPC, you could always
build the binary and contribute it back
Hi,
thanks for the response. So far, my experiences have been just fine, the
only
minor problem that I had, was that I had to remove the Options
“$JAVA_JNA”,"$JFFI_OPTS" from the java call at the end of the jruby
wrapper
shell script in order to load the oracle jdbc-Driver, otherwise an
“unsuitable Driver” Error occured.
thanks for the response. So far, my experiences have been just fine, the
only
minor problem that I had, was that I had to remove the Options
“$JAVA_JNA”,“$JFFI_OPTS” from the java call at the end of the jruby
wrapper
shell script in order to load the oracle jdbc-Driver, otherwise an
“unsuitable Driver” Error occured.
Interesting. Can you post the full error, and possibly file a bug for
it? Ideally our JNA/JFFI stuff shouldn’t be interfering with a JDBC
driver, but I’d like to see the problem anyway. My guess is that the
driver you’re using has native code and our paths screw up loading
that code.
ppc-32,…)
using the Oracle thin driver classes12.jar that comes with Oracle
10.2.0.4.0.
When I remove the -Xbootclasspath, the connect is fine.
That makes a bit more sense. The bootclasspath line is purely to
improve startup by allowing jruby’s own classes to skip verification
(since ideally we’ll have verified them a thousand times during
testing, and most come right out of javac itself). Removing it doesn’t
hurt anything, but it’s also not surprising that having it there
monkeys with the loading of JDBC drivers. No worries, either way…
Interesting. Can you post the full error, and possibly file a bug for
it? Ideally our JNA/JFFI stuff shouldn’t be interfering with a JDBC
driver, but I’d like to see the problem anyway. My guess is that the
driver you’re using has native code and our paths screw up loading
that code.
Charlie
Correcting myself, it was the -Xbootclasspath/a:"$JRUBY_CP" Option that
made
the difference. In my environment, JRUBY_CP points at
jruby-1.4.0/lib/jruby.jar and jruby-1.4.0/lib/bsf.jar. I am getting :
java/sql/DriverManager.java:582:in getConnection': java.sql.SQLException: No suitable driver (NativeException) from java/sql/DriverManager.java:186:ingetConnection’
This is on AIX 5.3, IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX
ppc-32,…)
using the Oracle thin driver classes12.jar that comes with Oracle
10.2.0.4.0.
When I remove the -Xbootclasspath, the connect is fine.
-klaus
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
