Joaquín Rodriguez-Guerra Urcelay wrote: > Thanks Mark. Since the connection is never established with eos.apache.org, > we can not know the urls that liferay is requesting, right? So, if tomcat is > not the responsible for those connections, I guess there isn't any way to > configure tomcat to avoid them, right? Thanks for your help.
So run your app on a box that does have access to www.apache.org and see what happens. You could also take a thread dump whilst it is hanging to see what code is trying to make the connection(s). That should point you at the right part of the source code. Mark > > -----Mensaje original----- > De: Mark Thomas [mailto:ma...@apache.org] > Enviado el: miércoles, 12 de agosto de 2009 13:45 > Para: Tomcat Users List > Asunto: Re: tomcat connects to eso.apache.org > > Joaquín Rodriguez-Guerra Urcelay wrote: >> Hello all, I am using tomcat with liferay, and when uploading applications >> it is taking too much time. After using a sniffer to see the outgoing >> connections we found out that liferay was trying to access >> file-01.liferay.com to obtain files, but the firewall was not allowing the >> connections, whice was mking a delay. We configured liferay to block these >> connections, and uploading time decrement to the half (from 7 min to 3.5). >> But now, we are seeing that when uploading applications, there are still >> connections to eos.apache.org, probably by tomcat, blocked by the firewall, >> which are producing this delay. Do you know how can we block these >> connections that tomcat is doing to avoid the delay?? Thank you! > > That isn't Tomcat. It is your app or a library your app is using. My > money would be on an XML schema. Since you are sniffing traffic, what > URLs are being requested? > > Mark > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > ______________________ > Este mensaje, y en su caso, cualquier fichero anexo al mismo, > puede contener informacion clasificada por su emisor como confidencial > en el marco de su Sistema de Gestion de Seguridad de la > Informacion siendo para uso exclusivo del destinatario, quedando > prohibida su divulgacion copia o distribucion a terceros sin la > autorizacion expresa del remitente. Si Vd. ha recibido este mensaje > erroneamente, se ruega lo notifique al remitente y proceda a su borrado. > Gracias por su colaboracion. > ______________________ > This message including any attachments may contain confidential > information, according to our Information Security Management System, > and intended solely for a specific individual to whom they are addressed. > Any unauthorised copy, disclosure or distribution of this message > is strictly forbidden. If you have received this transmission in error, > please notify the sender immediately and delete it. > ______________________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
