I think that Chuck is right : it has nothing to do with Tomcat, it's more a problem of communication between your webapp and the Google API.
2013/4/12 Caldarale, Charles R <chuck.caldar...@unisys.com> > > From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com] > > Subject: java.net.SocketTimeoutException: Read timed out > > > The stack trace below is the exception that occurred today. Does this > look > > like a tomcat or google calendar issue? > > It has nothing to do with Tomcat; it's your webapp that opened the > connection to Google - Tomcat is completely unaware of it. Whether it's a > Google limitation or a bug in your webapp can't be determined from just the > stack trace. Best if you could get a network traffic capture for the > incident and see if the request to Google is malformed, which might well > result in the Google server ignoring it. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail and > its attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- CHAKER Antoine Philippe Chekry Ingénieur Informaticien / Software Engineer Cote d'Ivoire / Ivory Coast Afrique de l'Ouest / West Africa * *