Applet lifecycle and Java plug-in.
Sorry if this is a FAQ. But I (really) found no clue anywhere. I have a Swing applet. Tested on Linux/Debian/Mozilla/Blackdown 1.3.1 and Windows/2000/IE/Sun 1.3.1_01. The behavious is exactly the same: the init() method is called each time the browser displays the applet. I tested the applet at: http://java.sun.com/docs/books/tutorial/applet/overview/lifeCycle.html and it fails too (the "init..." string appears each time you access the page, instead of only once). The major problem is that there is no way to keep applet state during browsing. Each time you access the page, a brand new applet is launched. This is not the case, if you use internal JVMs of browsers (but then, of course, you have Java 1.1). Any help is welcome. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: jdk1.3.1 crash on Linux
Signal 11 may be a hardware fault - run a memory checker. For the record, here are some links from my bookmarks (apologies if the embedded HTML zaps anybody's client): Easy-to-use (user space) tool: http://www.qcc.sk.ca/~charlesc/software/memtester/";>Charles Cazabon's memtest Excellent developerWorks article: http://www-106.ibm.com/developerworks/linux/library/l-hw1/index.html?dwzone=linux?open&l=252,t=gr,p=lxhwstabgd1";>developerWorks Linux Linux hardware stability guide, Part 1 A CPU burner - to check the CPU under stress: http://users.bigpond.net.au/cpuburn/";>CPU Burn-in Homepage Other stuff: http://www.linuxdoc.org/HOWTO/Kernel-HOWTO-2.html";>The Linux Kernel HOWTO Quick Steps - Kernel Compile http://panic.et.tudelft.nl/~costar/memmxtest/";>MemMXtest - A Memory Testing Environment for MMX PCs http://www.teresaudio.com/memtest86/#commands";>Memtest86 - Memory Diagnostic Page http://www.simmtester.com/default.asp";>CSTInc, The Online Memory Tester and Testing Solution Company. http://librenix.com/?inode=1132";>Linux Linux hardware stability guide, part 2 [Librenix.com] http://www.netroedge.com/~lm78/";>Linux System Hardware Monitoring Regards, Thomas. At 21:41 13/11/2001 -0800, Hong ZHou wrote: >Hi, Dear ALL: > >I have two problems that need great helps. > >1. On my Redhat Linux computer, when I run blackdown-1.3.1-FCS java, I >got the JVM crashes time to time at about 30% frequences. The error >message says: > >*** >Unexpected Signal : 11 occurred at PC=0x40152522 >Function name=JVM_IHashCode >Library=/usr/local/j2sdk1.3.1/jre/lib/i386/client/libjvm.so > >Current Java thread: > at java.lang.System.identityHashCode(Native Method) > at > java.io.ObjectOutputStream$HandleTable.findWireOffset(ObjectOutputStream.java:2344) > at > java.io.ObjectOutputStream.serializeNullAndRepeat(ObjectOutputStream.java:1257) > at > java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281) > at > java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827) > at > java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480) > at java.util.Hashtable.writeObject(Hashtable.java:747) > at java.lang.reflect.Method.invoke(Native Method) > at > java.io.ObjectOutputStream.invokeObjectWriter(ObjectOutputStream.java:1864) > at > java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1210) > at > java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366) > at > java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1827) > at > java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480) > at > java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214) > at > java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366) > at com.anabas.recorderServer.ZipSaver.saveMessage(ZipSaver.java:174) > at > >com.anabas.recorderServer.Recorder$MeetingMessageListener.onMessage(Recorder.java:235) > at > >com.anabas.sonicmq.SonicMQMessageListenerAdapter.onMessage(SonicMQMessageListenerAdapter.java:32) > at com.anabas.sonicmq.Receiver.onMessage(GMS_SubscriberImpl.java:194) > at progress.message.jclient.Session.dc_(Unknown Source) > at progress.message.jclient.TopicSession.run(Unknown Source) > at progress.message.jclient.co.run(Unknown Source) > >Dynamic libraries: >08048000-0804c000 r-xp 08:01 >1006738/usr/local/j2sdk1.3.1/bin/i386/native_threads/java >0804c000-0804d000 rw-p 3000 08:01 >1006738/usr/local/j2sdk1.3.1/bin/i386/native_threads/java >4000-40016000 r-xp 08:01 389379 /lib/ld-2.1.92.so >40016000-40017000 rw-p 00015000 08:01 389379 /lib/ld-2.1.92.so >40018000-40019000 r--p 08:01 >908554 /usr/lib/locale/en_US/LC_IDENTIFICATION >40019000-4001a000 r--p 08:01 >908555 /usr/lib/locale/en_US/LC_MEASUREMENT >4001a000-4001b000 r--p 08:01 >908560 /usr/lib/locale/en_US/LC_TELEPHONE >4001b000-4001c000 r--p 08:01 >908551 /usr/lib/locale/en_US/LC_ADDRESS >4001c000-4002a000 r-xp 08:01 389418 /lib/libpthread-0.9.so >4002a000-40032000 rw-p d000 08:01 389418 /lib/libpthread-0.9.so >40032000-4003d000 r-xp 08:01 >243797 /usr/local/j2sdk1.3.1/jre/lib/i386/native_threads/libhpi.so >4003d000-4003e000 rw-p a000 08:01 >243797 /usr/local/j2sdk1.3.1/jre/lib/i386/native_threads/libhpi.so >4003e000-40301000 r-xp 08:01 >617269 /usr/local/j2sdk1.3.1/jre/lib/i386/client/libjvm.so >40301000-40318000 rw-p 002c2000 08:01 >617269 /usr/local/j2sdk1.3.1/jre/lib/i386/client/libjvm.so >4033-40332000 r-xp 08:01 389390 /lib/libdl-2.1.92.so >40332000-40333000 rw-p 1000 08:01 389390 /lib/libdl
Re: Delete Key
brEezE wrote: > Hi, > Just a simple question. > Why does a square box appeared whenever I press the Delete key? This happens > in TogetherJ 4 and 'sometimes' in Netbeans/FFJ. Or a lowercase-y-with-umlaut (char 255)? Is this a known issue? Is it a Java thing or an X thing? I see it occasionally with the Sun JVM as well, but can't seem to pin down a specific circumstance which will always cause it (I am noticing it in NetBeans). -- Glenn Holmer ([EMAIL PROTECTED]) "Mere force is useless against people who are neither cowards nor fools. We must match courage with courage and cunning with still greater cunning if we are to do anything at all." -Leslie Howard in "The Scarlet Pimpernel", 1935 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what are the differences among classic/libjvm.so, server/libjvm.so, and client/libjvm.so?
On Tue, Nov 13, 2001 at 10:50:23PM -0800, Hong ZHou wrote: > Hi, Dear ALL: > > In the linux JDK, there are 3 libjvm.so, what are the differences among them? > > (classic/libjvm.so, server/libjvm.so, and client/libjvm.so) The "classic" is an old JVM that uses green threads instead of kernel threads. The other two are implementations of Sun's HotSpot performance engine, optimized for use in server and client environments. The HotSpot versions use kernel threads, which means true support of multiprocessing. Nathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
strange thread dump
Hi, I run Blackdown JDK1.3.1 (build Blackdown-1.3.1-FCS) on linux (Linux 2.2.18 #6 SMP, 2 processors, GLIBC 2.1.3). I run a server application, using green threads and the classic VM. In rare situations I get very strange thread dump (using kill -QUIT): Full thread dump Classic VM (Blackdown-1.3.1-FCS, green threads): "250" (TID:0x2ccd8048, sys_thread_t:0x88aee80, state:R) prio=5 "249" (TID:0x2ccd8268, sys_thread_t:0x88ad8f0, state:R) prio=5 "248" (TID:0x2ccd82d8, sys_thread_t:0x88ac360, state:R) prio=5 "247" (TID:0x2ccd8500, sys_thread_t:0x88aadd0, state:R) prio=5 "246" (TID:0x2ccd8560, sys_thread_t:0x88a9840, state:R) prio=5 "245" (TID:0x2ccd8838, sys_thread_t:0x88a82b0, state:R) prio=5 "244" (TID:0x2ccd, sys_thread_t:0x88a6d20, state:R) prio=5 "243" (TID:0x2ccd8b08, sys_thread_t:0x88a5790, state:R) prio=5 "242" (TID:0x2ccd8dc8, sys_thread_t:0x88a4200, state:R) prio=5 and so on No stack traces available? When this happens, the VM seems to be frozen. Is this thread dump corrupted? Any help very appreciated! bye Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what are the differences among classic/libjvm.so, server/libjvm.so, and client/libjvm.so?
Nathan Meyers <[EMAIL PROTECTED]> writes: > On Tue, Nov 13, 2001 at 10:50:23PM -0800, Hong ZHou wrote: >> Hi, Dear ALL: >> >> In the linux JDK, there are 3 libjvm.so, what are the differences >> among them? >> >> (classic/libjvm.so, server/libjvm.so, and client/libjvm.so) > > The "classic" is an old JVM that uses green threads instead of > kernel threads. Yes, it's old but it's only restricted to "green" threads in Sun's version. Our classic VM supports both native and green threads. > The other two are implementations of Sun's HotSpot performance > engine, optimized for use in server and client environments. The > HotSpot versions use kernel threads, which means true support of > multiprocessing. Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux.html Run Java 2 SE v1.3.1 on your iPAQ: http://www.handhelds.org/pipermail/ipaq/2001-June/007221.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: jdk1.3.1 crash on Linux
Hong ZHou <[EMAIL PROTECTED]> writes: > I have two problems that need great helps. > > 1. On my Redhat Linux computer, when I run blackdown-1.3.1-FCS > java, I got the JVM crashes time to time at about 30% > frequences. The error message says: > > > Dynamic libraries: > 40333000-4044e000 r-xp 08:01 389386 /lib/libc-2.1.92.so Please upgrade your glibc. 2.1.92 is a broken beta version. The latest version for RH 7.0 seems to be 2.2.4-18: http://www.redhat.com/support/errata/RHBA-2001-121.html Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux.html Run Java 2 SE v1.3.1 on your iPAQ: http://www.handhelds.org/pipermail/ipaq/2001-June/007221.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what are the differences among classic/libjvm.so, server/libjvm.so, and client/libjvm.so?
"JK" == Juergen Kreileder <[EMAIL PROTECTED]> writes: JK> Yes, it's old but it's only restricted to "green" threads in Sun's JK> version. Our classic VM supports both native and green threads. I don't think this is correct for both JDK 1.2.2 and JDK 1.3.1. $ ls /opt/jdk1.2.2/jre/bin/i386/ green_threads/ native_threads/ realpath* $ ls /opt/jdk1.3.1_01/jre/bin/i386/ green_threads/ native_threads/ realpath* --- Vladimir Vladimir G. Ivanovichttp://leonora.org/~vladimir 2770 Cowper St. [EMAIL PROTECTED] Palo Alto, CA 94306-2447 +1 650 678 8014 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what are the differences among classic/libjvm.so, server/libjvm.so, and client/libjvm.so?
Vladimir G. Ivanovic <[EMAIL PROTECTED]> writes:
> "JK" == Juergen Kreileder <[EMAIL PROTECTED]> writes:
>
> JK> Yes, it's old but it's only restricted to "green" threads in
> JK> Sun's version. Our classic VM supports both native and green
> JK> threads.
>
> I don't think this is correct for both JDK 1.2.2 and JDK 1.3.1.
>
>$ ls /opt/jdk1.2.2/jre/bin/i386/
>green_threads/ native_threads/ realpath*
>$ ls /opt/jdk1.3.1_01/jre/bin/i386/
>green_threads/ native_threads/ realpath*
"Restricted" may be the wrong word. Technically you can run Sun's
version with the classic native threads VM. But AFAIK Sun hasn't
merged our native threads VM changes into their 1.2.2 (I'm not sure
about 1.3.x, Calvin?) and so it isn't really usable. In Sun's 1.3.1
.java_wrapper only allows to use green threads with the classic VM:
,
| if [ "${vmtype}" = "classic" ]; then
| ttype=green_threads
| LD_BIND_NOW=yes
| export LD_BIND_NOW
| _JVM_THREADS_TYPE=green_threads
| export _JVM_THREADS_TYPE
| fi
`
(Note that native_threads/libhpi.so is also used by the HotSpot VMs.)
Juergen
--
Juergen Kreileder, Blackdown Java-Linux Team
http://www.blackdown.org/java-linux.html
Run Java 2 SE v1.3.1 on your iPAQ:
http://www.handhelds.org/pipermail/ipaq/2001-June/007221.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what are the differences among classic/libjvm.so, server/libjvm.so, and client/libjvm.so?
So, the directory structure is misleading. Thanks for the clarification.
--- Vladimir
Vladimir G. Ivanovichttp://leonora.org/~vladimir
2770 Cowper St. [EMAIL PROTECTED]
Palo Alto, CA 94306-2447 +1 650 678 8014
"JK" == Juergen Kreileder <[EMAIL PROTECTED]> writes:
JK> Vladimir G. Ivanovic <[EMAIL PROTECTED]> writes:
>> "JK" == Juergen Kreileder <[EMAIL PROTECTED]> writes:
>>
JK> Yes, it's old but it's only restricted to "green" threads in
JK> Sun's version. Our classic VM supports both native and green
JK> threads.
>>
>> I don't think this is correct for both JDK 1.2.2 and JDK 1.3.1.
>>
>> $ ls /opt/jdk1.2.2/jre/bin/i386/
>> green_threads/ native_threads/ realpath*
>> $ ls /opt/jdk1.3.1_01/jre/bin/i386/
>> green_threads/ native_threads/ realpath*
JK> "Restricted" may be the wrong word. Technically you can run Sun's
JK> version with the classic native threads VM. But AFAIK Sun hasn't
JK> merged our native threads VM changes into their 1.2.2 (I'm not sure
JK> about 1.3.x, Calvin?) and so it isn't really usable. In Sun's 1.3.1
JK> .java_wrapper only allows to use green threads with the classic VM:
JK> ,
>> if [ "${vmtype}" = "classic" ]; then
>> ttype=green_threads
>> LD_BIND_NOW=yes
>> export LD_BIND_NOW
>> _JVM_THREADS_TYPE=green_threads
>> export _JVM_THREADS_TYPE
>> fi
JK> `
JK> (Note that native_threads/libhpi.so is also used by the HotSpot VMs.)
JK> Juergen
JK> --
JK> Juergen Kreileder, Blackdown Java-Linux Team
JK> http://www.blackdown.org/java-linux.html
JK> Run Java 2 SE v1.3.1 on your iPAQ:
JK> http://www.handhelds.org/pipermail/ipaq/2001-June/007221.html
JK> --
JK> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
JK> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
