I'd take a look at this: http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout
Or you add parameters to your ProxyPass directive http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass On Feb 19, 3:17 pm, Fran <[email protected]> wrote: > After some tests I can to confirm that the delay between Comet events > are constant. > > Seems that Apache apply a timeout when conects to tomcat by Proxypass > > Anyone know it? > > On 19 feb, 02:04, Fran <[email protected]> wrote: > > > > > anyone know the problem? please > > > On 18 feb, 00:41, Fran <[email protected]> wrote: > > > > I use Comet that its Long polling. > > > I think that the problem is a timeout that is applied by tomcat when > > > apache conect the proxy to the tomcat. > > > > If I execute the aplication directly in tomcat. Its works fine. > > > If I execute the aplication in apache and a proxypass to servlet, the > > > aplication has a timeout between comet events that I dont understand. > > > > You can test it: > > > > Aplication in tomcat > > > directly:http://california.lirondo.com:8081/msn/Messenger.html > > > ---> It works very good (is needed to use diferents navegators for > > > conect diferent users) > > > Aplication in apache:http://california.lirondo.com/msn/Messenger.html > > > --> If you are patient, you can test that works fine but is soooo slow > > > > Help please, thanks! > > > > On 17 feb, 23:46, Chris Lercher <[email protected]> wrote: > > > > > Hi, > > > > > I don't have an Apache+Tomcat setup, so I can only guess what may be > > > > happening: There are two basic ways to do Comet. > > > > > - Streaming (for one request, the server sends a few bytes, then later > > > > some more etc.) > > > > - Long polling (for one request, the server sends zero bytes > > > > initially, and just waits until it can send anything. When the client > > > > receives that response, it creates a new request.) > > > > > Streaming is known not to work reliably, especially with proxies > > > > (unfortunately). Long polling also only works reliably, if you don't > > > > wait too long with your response. > > > > > Even if you manage to set up your apache in a way that it works, you > > > > probably can't control how additional proxies etc (and also the > > > > browser) between your server and the client behave. > > > > > Maybe this helps a little bit. > > > > Chris > > > > > On Feb 17, 8:56 pm, Fran <[email protected]> wrote: > > > > > > anyone can help me please? > > > > > > On 17 feb, 00:53, Fran <[email protected]> wrote: > > > > > > > help me please > > > > > > > On 16 feb, 19:54, Fran <[email protected]> wrote: > > > > > > > > I am using now Proxypass for apache. The config is: > > > > > > > > <VirtualHost *:80> > > > > > > > ServerName california.####.com > > > > > > > ServerAdmin webmas...@localhost > > > > > > > DocumentRoot /var/www/#### > > > > > > > ProxyRequests On > > > > > > > <Proxy *> > > > > > > > Order deny,allow > > > > > > > Allow from all > > > > > > > </Proxy> > > > > > > > ProxyPass > > > > > > > /app/com.apphttp://california.####.com:8081/app/com.app > > > > > > > ProxyPassReverse > > > > > > > /app/com.apphttp://california.####.com:8081/app/com.app > > > > > > > > DirectoryIndex index.php > > > > > > > AccessFileName .htaccess > > > > > > > </VirtualHost> > > > > > > > > The aplication is a Comet chat. > > > > > > > With this configuration, the aplication executed from apache > > > > > > > works but > > > > > > > some message lost. > > > > > > > The error log shows: > > > > > > > > [error] [client ########] proxy: error reading status line from > > > > > > > remote > > > > > > > server california.####.com, > > > > > > > referer:http://california.####.com/app/com.app/2179BCD97ED1043BAEE2BAA974B2E7... > > > > > > > [error] [client ########] ] proxy: Error reading from remote > > > > > > > server > > > > > > > returned by /app/com.app/messenger, > > > > > > > referer:http://california.####.com/app/com.app/2179BCD97ED1043BAEE2BAA974B2E7... > > > > > > > > I read in some forum that is needed the lines in Location > > > > > > > directive of > > > > > > > apache: > > > > > > > > SetEnv force-proxy-request-1.0 1 > > > > > > > SetEnv proxy-nokeepalive 1 > > > > > > > > If I put this, the aplications is beeing more and more slowly. > > > > > > > > Someone can tell me a solutions please :( > > > > > > > > On 15 feb, 22:47, Fran <[email protected]> wrote: > > > > > > > > > Hello, > > > > > > > > > I need your help about GWT integration in apache and tomcat. > > > > > > > > > I have a GWT aplication that has server side. This server side > > > > > > > > is > > > > > > > > listening in 8081 port at tomcat. > > > > > > > > I need that the client side be in apache that is listening in > > > > > > > > port 80, > > > > > > > > so I need call server side at port 8081 of tomcat. > > > > > > > > How can I do? > > > > > > > > > If I run the aplication int tomcat, its works fine. But If I > > > > > > > > run the > > > > > > > > aplication in apache, the server side dont work. > > > > > > > > > Help me please > > > > > > > > Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
