[Pljava-dev] zlib conflict on Debian AMD64 ???

Hi Joost,
Sun fixed the cause of the zlib conflict at patch level 5 so I doubt
that's what you're seeing. Is it possible that you compiled the
pljava.so binary for 32-bit and the JVM is a 64-bit or vice versa?

GCJ (version 4.0 and up) should work fine but so should any compatible JVM.

Regards,
Thomas Hallgren

Joost Kraaijeveld wrote:
> Hi,
>
> I suspect I have the zlib conflict, using the SUN 1.5.0 patch level7 JDK
> on a Debian Etch AMD64 ,although I cannot see if the error is in
> java.util.zip.Inflater.init:
>
> DEBUG: Using integer_datetimes
> DEBUG: Added JVM option string "-Djava.class.path=/usr/lib/postgresql/8.1/lib/pljava.jar"
> DEBUG: Added JVM option string "-Dsqlj.defaultconnection=jdbc:default:connection"
> DEBUG: Added JVM option string "vfprintf"
> DEBUG: Added JVM option string "-Xrs"
> DEBUG: Creating JavaVM
> DEBUG: JavaVM created
> DEBUG: Getting Backend class pljava.jar
> WARNING: java.lang.InternalError
> DEBUG: Destroying JavaVM...
> DEBUG: JavaVM destroyed
> ERROR: Unable to load class org/postgresql/pljava/internal/Backend using CLASSPATH '-Djava.class.path=/usr/lib/postgresql/8.1/lib/pljava.jar'
>
> Is there a way to make sure that it is in java.util.zip.Inflater.init,
> without resorting to debuggers?
>
> If I am indeed bitten by the zlib bug, is there a way to make PL/Java
> work on a Debian Etch AMD64? Should using GJC instead of using the Sun
> JVM *just for PostgreSQL* work? (I cannot replace the Sun JVM as I need
> to run JBoss).
>
> TIA
>
>