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: 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 >> >> > I tweaked the google calendar exception-handling code, a bit, and downloaded Wireshark. The next time it happens, I should be ready to debug/troubleshoot. I should have mentioned last time, that to workaround/resolve the issue, I stop tomee/tomcat, restart, and I run the utility within the webapp which can do 'manual' updates/pushes to google calendar. that 'always' works... so, based on that, i am under the assumption that the webapp is not to be blamed for the exceptions that I'm experiencing...over time, but I'm (still) considering all what you said and recommended though. May not be to the best interest of Atmosphere committer, but I reverted back to Atmosphere 1.0.12 (even though Atmosphere 1.0.13 snapshot seems to have some good/valid fixes, that don't seem so applicable to me and my use case), as I found that/1.0.12 as a stable release, and I experienced no issues. If I experience this issue again, it is time to revert to tomcat 7.0.37 and/or 7.0.35, after diving into Wireshark, while the issue is occurring. Hmmm, i think i remember someone posting an issue with their 'tomcat5' after windows did an automatic update on their machine (I assume, as it did on mine that same morning), but I forgot what was the person's issue and if issue was resolved. I know...I'd have to search the archives or recent history, since it was earlier this week. :) just trying to think out loud of all the 'changes' that occurred. it is clearly not a data issue (since a restart of tomcat and running my 'manual google calendar update' utility updates google calendar, successfully, with the same data that was attempted to be pushed via @Schedule and MDB), and i am not convinced (yet) that my app is to blame, but my app consists of any/all dependencies that I'm using...including tomee/tomcat. :) one of the tomee committer has advised me to use @Asynchronous instead of JMS/ActiveMQ. considering that, but i really don't feel the JMS/ActiveMQ is 'broke'... so, if it ain't broke, don't fix it.
