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. I will add a note in the jira report, someone else has to take over that, I have to say this is beyound the domain where I am good at :-( Werner Werner Punz schrieb: > Ok I am ccing this into the devs list, some other people have to > look into the issue as well! > > > I think I found the cause of all evil regarding the non initializing > components: > > 2007 21:46:29 org.apache.myfaces.shared_tomahawk.config.MyfacesConfig > getStringInitParameter > INFO: No context init parameter > 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value > /faces/myFacesExtensionResource > 31.01.2007 21:46:29 > org.apache.myfaces.shared_tomahawk.config.MyfacesConfig getCurrentInstance > INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation > 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig > getBooleanInitParameter > INFO: No context init parameter > 'org.apache.myfaces.READONLY_AS_DISABLED_FOR_SELECTS' found, using > default value true > 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig > getStringInitParameter > INFO: No context init parameter > 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH' found, using default value > /faces/myFacesExtensionResource > 31.01.2007 21:46:30 org.apache.myfaces.shared_impl.config.MyfacesConfig > getCurrentInstance > INFO: Starting up Tomahawk on the MyFaces-JSF-Implementation > 31.01.2007 21:46:40 > org.apache.myfaces.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 > > > But the funny thing is, this does not happen always, something must be > going badly wrong in the resource loader, which is code I have > absolutely no clue about (sorry have not touched it so far) > > My personal assumption is, that the ie to my knowledge chokes on > resources if you do not serve the filelength upfront, under certain > conditions. I have no clue why I am getting this and others > like cagatay under similar conditions do not get it, and why I only > get it at certain controls! > > Can anyone who hase more insight into the resource loader look into the > problem? > > > I can remember something along those lines already once was in there > and has been fixed, but now it is here again (oh joy) > > Werner > > > Werner Punz schrieb: >> Catalin Kormos schrieb: >>> Hi, >>> >>> Any of you experiencing problems using Dojo based components on IE, like >>> modalDialog or inputSuggestAjax? i keep getting this kind of messages, >>> and only on IE: >>> >>> Jan 29, 2007 9:48:13 PM >>> org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader serveResource >>> SEVERE: Unable to find resource src/widget.js for component >>> dojo.DojoResourceLoader. Check that this file is available in the >>> classpath in sub-directory /resource of the package-directory. >>> >>> It works perfectly fine on Firefox, and it did worked on IE too, a few >>> days ago. I'm using the latest 1.1.5 snapshots that i built from the SVN >>> with facelets. >>> >> Ok I filed a bugreport on this one, I will start to investigate into it >> tonight. >> >> > >
