[jira] Commented: (TOMAHAWK-877) DojoUtils component creation code breaks in ie

["Werner Punz (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TOMAHAWK-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469215 ] 

Werner Punz commented on TOMAHAWK-877:
--------------------------------------

ok it is not the dojo code, that I am sure now.

I already left a comment in the thread in the users list:
Ok, I am getting closer,
I upgraded the tomcat versions, the problem still persists.
Funny thing is, it is only on a Mac (running an intel Dual Core)
If I serve the file from linux on a single core notebook
in the same Tomcat configuration the problems are gone.

This looks like a timing issue, i am not sure if the mac
is at fault here, or the Dual core is triggering
something in the JVM, I got a similar report from
a user whom I am trying to fix some issues in the Fisheye for.
Anyway, dojo is not at fault here, the problem either is the jdk
or some resource loader code going haiwire.

The funny thing is, once I switched tomcats the client abort exception
stopped (maybe it was ignored due to different settings) but the result
of not working dojo controls persisted.


----
Additional comment, there was an error which i got in the Tomcat 5.5.17
which looked like that:


es.renderkit.html.util.DefaultAddResource serveResource
SCHWERWIEGEND: Error while serving resource:
dojo.DojoResourceLoader/dojo.js, message : null
ClientAbortException:  java.net.SocketException: Broken pipe
	at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366)
	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
	at
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)
	at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:278)
	at
org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:103)
	at
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.writeResource(MyFacesResourceLoader.java:244)
	at
org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader.serveResource(MyFacesResourceLoader.java:217)
	at
org.apache.myfaces.renderkit.html.util.DefaultAddResource.serveResource(DefaultAddResource.java:606)
	at
org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:128)
	at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
	at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
	at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
	at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
	at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
	at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
	at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
	at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
	at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
	at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
	at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
	at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
	at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
	at java.lang.Thread.run(Thread.java:613)
Caused by: java.net.SocketException: Broken pipe
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
	at
org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:746)
	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:348)
	at
org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:769)
	at
org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:117)
	at
org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:579)
	at org.apache.coyote.Response.doWrite(Response.java:559)
	at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:361)
	... 22 more


this one did not occur anymore in tomcat 5.5.20 (probably supressed error message or rerouting of the problem)
anyway the problem persisted.
We have had that before I am going to do some additional tests with a different app server (jetty to check if it resolves the problem)

Anyway something in the resource loader must go haywire, I assume it really is the broken pipe error, I had a similar issue once serving pdfs into the IE, the fix back then was, to add the content length which you wanted to send to the browser in the response!



> DojoUtils component creation code breaks in ie
> ----------------------------------------------
>
>                 Key: TOMAHAWK-877
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-877
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>         Environment: IE 6 and 7
>            Reporter: Werner Punz
>         Assigned To: Werner Punz
>
> Someone commited a code in the dojo utils which causes the component creation of the dojo components
> to break on all ie versions.
> I assume the code has been moved from in page code to body onload or something along those lines.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.