Invocation API and JNI in JDK1.2
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 methods are in the same "executable" program as the rest of the code - and worked in JDK1.1.7. In JDK1.2 it can't find the methods. After I moved the native methods in a .so file and I used System.loadLibrary() everything worked fine. Still, I don't remember anything in the specs requiring that - is it a bug or a feature? ( everything worked fine after that, I'm using JDK1.2 now ) Regards Costin ( application = apache-apr, I wrote a small mod_java module, and I try to make it work with 1.2) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Serialver on JDK1.2
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 Method) at java.lang.ClassLoader.loadLibrary0(Compiled Code) at java.lang.ClassLoader.loadLibrary(Compiled Code) at java.lang.Runtime.loadLibrary0(Compiled Code) at java.lang.System.loadLibrary(Compiled Code) at sun.security.action.LoadLibraryAction.run(Compiled Code) at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Compiled Code) at java.awt.Toolkit.(Toolkit.java:903) at java.awt.Component.(Component.java:258) I assumed is something wrong with my libraries, but everything else is working fine, including appletviewer and Swing/AWT applications. Does anyone have run serialver? Costin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hang in GC with invocation (1.2)
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 just attach to the virtual machine when I need to do Java processing ( and when gc() hung, all other threads are also hunged) Please help - I have no ideea where to start with this. Regards, Costin ( the program is apache-apr, the multithreading version of Apache - but I don't think it's a problem with their code, since 1.1.7 works too well, I had it running all night with 20 clients calling servlets ) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Garbage collection problem in JDK1.2
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 machine when I need to do Java processing - when gc() is called all other threads are also hunged. Please help - I have no ideea where to start with this. Regards, Costin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
