Re: [Jtreeview-devel] Signed applets anyone?
Brought to you by:
alokito
From: vkj <ve...@gm...> - 2008-01-24 05:06:44
|
Hi Alok, Thanks again for your attention! > I have not tried signing the applet. Does the unsigned version crash > the browser, or just the signed one? Which browser with which JVM? Only the signed version crashes the browser. Unsigned version works perfectly. I have tested this on the following combinations: 1. IE6 on WinXP, JDK 1.5 2. Firefox 2.0.5 on opensuse linux, JDK 1.5 as well as 1.6 3. Mozilla on solaris, JDK 1.5. 4. Seamonkey on opensuse linux, JDK 1.5. Applet launches fine and behaves perfectly until I close it. At that point it closes the browser from which it was launched. Xterm from which I launch browser shows the following message after browser closes: <start> INTERNAL ERROR on Browser End: Plugin instance index out of bounds -17409 System error?:: Success <end> Numeric value in the end of first statement varies across occurrences. It is not the process ID of either the browser process of java_vm process. Occasionally I also get a slightly different error: <start> INTERNAL ERROR on Browser End: Pipe closed during read? State may be corrupt System error?:: Resource temporarily unavailable <end> Few more details: --- I am creating a new dialog box which causes a browser window to open. This not possible in unsigned applets because of applet sandbox security model. Hence I am creating a signed applet. I first noticed the error I mentioned in this modified JTreeView. Then I went back and signed the original applet and that too had the same behavior. To be sure, I created a "Hello World" applet and signed it. This does not crash the browser. I have googled for this error message but nothing relevant is available. Sun has fixed a bug related to this error message ("http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4935740"). That was in Oct 2003: I am sure it must have gone into JDK distributions (at least in 1.6), though I must admit that the information on that bug report is teasingly similar to the error message I get. At this point I am clueless and any pointers will be deeply appreciated. The next step for me would be to try to attach a debugger to the running jvm. I was hoping to learn from others' experience if possible. Vineet |