I am using the invocation API to start JDK1.2 inside an application
, and everything works fine until System.gc() is called ( or I create
few large arrays and gc() is trigered). The same code works
without problems with JDK117.
The program is using it's own threads, I just attach to the virtual
Ok, I guess the subject is enough :-)
I am using the invocation API to start JDK1.2, and everything
works fine until System.gc() is called ( or I create few large arrays and
I suppose gc() is trigered). The same code works without problems with
JDK117.
The program is using it's own threads, I jus
Hi,
I have a small problem with JDK1.2:
$serialver
Exception in thread "main" java.lang.UnsatisfiedLinkError:
/home/costin/local/jdk1.2/jre/lib/i386/libawt.so:
/home/costin/local/jdk1.2/jre/lib/i386/libawt.so: undefined symbol: XmQmotif
at java.lang.ClassLoader$NativeLibrary.load(Native M
Hi,
JDK1.2 works great on my RedHat, everything is great (except fonts).
My question:
I use the invocation API to start a JVM from a C application.
With JDK1.1.7/native threads it works great, and worked
with JDK1.2 without any problems.
>From the started VM I call some native methods. The meth