Hi,
this sounds like a missing content-length header line in combination with a
keep-alive header line in the response. In such a case the connection must be
kept open until all data is sent but the receiving instance (your apache
proxy) does not know when to stop the transmission and the timeout stops the
transmission.
Best Regards,
Ilja Pavkovic
Am Donnerstag, 18. Februar 2010 01:25:24 schrieb Adam Bender:
> Greetings,
>
> This is kind of an odd problem so I will do my best to explain it.
>
> First our environment:
>
> We are running a wicket 1.4 app inside Tomcat
> Tomcat is front-ended by Apache 2.2 using mod_proxy_http so we are talking
> to the Http 1.1 connector in Tomcat Our Http 1.1 connector has a
> connectionTimeout parameter of 20 seconds (I believe this is the default
> it is shipped with)
>
> We are using the Wicket DateTextField which includes the use of some yui
> css and javascript
>
>
> Now for the problem:
>
> Whenever we load a page with a DateTextField on it the loading takes a very
> long time. I have been able to trace the problem to the loading of all of
> the js/css elements that are used by the DateTextField. Each element takes
> exactly 20 seconds to load (again this is the timeout on Tomcat's Http 1.1
> connector) which means in total it can take over minute for the
> DateTextField to be usable.
>
> When I change the connectionTimeout parameter to something smaller like 2
> seconds it takes each js/css element exactly 2 seconds to load. This lead
> me to believe that the loading of these files is timing out. Tracking it
> down further it looks like the timeout is coming on the
> java.net.SocketInputStream when it performs a read.
>
> I have tried moving some of these files out of the jar they came with and
> it seems to reduce the loading time to tens of milliseconds so it seems
> like the problem has to do with the fact tomcat is being asked to serve a
> file out of a jar.
>
> Now I realize that this is not a bug in Wicket but I have exhausted Google
> in a search for someone else who has had this problem. Has anyone run into
> problems using the DateTextField component when running right off of an
> Http 1.1 connector.
>
> I should also mention that when we started with the AJP connector in tomcat
> and the problem doesnt appear, however we have had reliability issues with
> AJP and it occasionally drops packets so we have been asked to switch to
> the Http 1.1 connector.
>
> Thanks,
> Adam
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
--
binaere bauten gmbh · tempelhofer ufer 1a · 10961 berlin
+49 · 171 · 9342 465
Handelsregister: HRB 115854 - Amtsgericht Charlottenburg
Geschäftsführer: Dipl.-Inform. Ilja Pavkovic, Dipl.-Inform. Jost Becker
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
