On Fri, Apr 12, 2013 at 8:02 PM, Howard W. Smith, Jr. <
smithh032...@gmail.com> wrote:
>
> On Fri, Apr 12, 2013 at 7:25 PM, Caldarale, Charles R <
> chuck.caldar...@unisys.com> wrote:
>
>> > From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com]
>> > Subject: java.net.SocketTimeoutException: R
On Fri, Apr 12, 2013 at 7:25 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > 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
On Fri, Apr 12, 2013 at 7:45 PM, antoine philippe chaker <
philippe.cha...@gmail.com> wrote:
> 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.
>
>
Agreed. :)
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
> > From: Howard W. Smith, Jr. [mailto:smithh032...@gmail.com]
> > Subject: java.net.SocketTimeoutException: Read timed out
> 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 o
