Hi i'm new with Tomcat...i'm starting it in 64-bit mode on
Solaris....but i need to use a 32-bit library....i want to know if the
difference between 32-64 bits in jvm are really important......

tks !!!!!!!!

zamba wrote:
> Hi i'm new with Tomcat...i'm starting it in 64-bit mode on
> Solaris....but i need to use a 32-bit library....i want to know if the
> difference between 32-64 bits in jvm are really important......

I run a 64-bit Tomcat with JARs intended for 32-bit JVMs all the time.  Java 
doesn't care; the differences are subsumed in the JVMs.  Bytecode is bytecode.

-- 
Lew
The word "I" is capitalized.

On 21 mar, 01:56, Lew <l...@lewscanon.com> wrote:
> zambawrote:
> > Hi i'm new with Tomcat...i'm starting it in 64-bit mode on
> > Solaris....but i need to use a 32-bit library....i want to know if the
> > difference between 32-64 bits in jvm are really important......
>
> I run a 64-bit Tomcat with JARs intended for 32-bit JVMs all the time. =A0=
Java
> doesn't care; the differences are subsumed in the JVMs. =A0Bytecode is byt=
ecode.
>
> --
> Lew
> The word "I" is capitalized.

Lew, i have the problem that java sends me a null pointer exception
when try to intantiate a binary class wich is intended for 32 bits
running under TOMCAT wich was started with -d64 option....

zamba wrote:
> Lew, i [sic] have the problem that java sends me a null pointer exception
> when try to intantiate a binary class wich is intended for 32 bits
> running under TOMCAT wich was started with -d64 option....

And it runs correctly when you don't use that switch?

The thing is, classes aren't intended for 32-bit nor 64-bit JVMs, just for 
JVMs.  Your problem must lie elsewhere.

Bytecode is bytecode.

-- 
Lew
The word "I" in English is always capitalized.

zamba wrote:
> Hi i'm new with Tomcat...i'm starting it in 64-bit mode on
> Solaris....but i need to use a 32-bit library....i want to know if the
> difference between 32-64 bits in jvm are really important......

If it is pure Java, then 32 or 64 or 57 bit does not matter.

If the Java code calls native code via JNI then there may
be an issue.

Arne