On 10/18/2012 05:18 PM, Camille Bégnis wrote:
>
> one of our users is experimenting (apparently) random applet death.
> The only hint we managed to collect -activating java logging on disk- is
> the attached trace.

For me an InterruptedException in Object.wait is not a big deal. 
Therefore you'd better make sure that this is really this 
InterruptedException which stops the applet.

Excerpts from the stack trace:
---
java.lang.InterruptedException
        at java.lang.Object.wait(Native Method)
        at sun.plugin2.message.Queue.waitForMessage(Unknown Source)
        at sun.plugin2.message.Pipe.receive(Unknown Source)
        at 
sun.plugin2.main.client.MessagePassingExecutionContext.doCookieOp(Unknown 
Source)
        at 
sun.plugin2.main.client.MessagePassingExecutionContext.getCookie(Unknown 
Source)
        at 
sun.plugin2.main.client.PluginCookieSelector.getCookieFromBrowser(Unknown 
Source)
        at com.sun.deploy.net.cookie.DeployCookieSelector.getCookieInfo(Unknown 
Source)
        at com.sun.deploy.net.cookie.DeployCookieSelector.get(Unknown Source)
        at sun.net.www.protocol.http.HttpURLConnection.setCookieHeader(Unknown 
Source)
        at sun.net.www.protocol.http.HttpURLConnection.writeRequests(Unknown 
Source)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown 
Source)
        at com.xmlmind.util.URLUtil.openStreamNoCache(URLUtil.java:1370)
        at 
com.xmlmind.xmledit.imagetoolkit.JavaImageToolkit$1.createImage(JavaImageToolkit.java:179)
        at 
com.xmlmind.xmledit.form.ImageViewportVP.createImage(ImageViewportVP.java:516)
        at 
com.xmlmind.xmledit.form.ImageViewportVP.createImageContent(ImageViewportVP.java:308)
        at 
com.xmlmind.xmledit.styledgadget.AbstractImageViewport.layoutContent(AbstractImageViewport.java:262)
---

Another strange this about this stack trace is that 
AbstractImageViewport.layoutContent (in both v5.3 and v5.4) catches all 
Throwables which could be raised by ImageViewportVP.createImageContent. 
Therefore I don't understand how you could see this stack trace.



>
> Any idea where this could come from?

Not really.

If you don't have this problem with a different Java runtime (e.g. try 
an older Java 1.7 or latest Java 1.6), then it's a bug in the Java 
runtime of this specific user. (Remember that an applet always runs on 
the machine of the end user, not on your servers.)

Otherwise the usual suspects are the network proxy or firewall of this 
user or its anti-virus software. An anti-virus software may act on 
opened sockets and forcibly close network connections (we have actually 
seen that.)

The Java bug database may also give you ideas about what happens. See 
for example:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7177454


 
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to