I did not see a response. However, I did add a wait_timeout setting to the my.ini file. The timeout defaults to 8 hours, so I set it to 16 (in milliseconds). That seemed to provide an acceptable work around, at least for now.
-----Original Message----- From: Kendrick C. Wilson [mailto:[email protected]] Sent: Tuesday, February 21, 2012 2:38 PM To: [email protected] Subject: RE: James 3.0 Beta 4 version Any word on the JDBC connection timeout error? Kendrick C. Wilson > Date: Mon, 20 Feb 2012 10:45:23 +0100 > From: [email protected] > To: [email protected] > Subject: Re: James 3.0 Beta 4 version > > Hi, > If everything goes well, around 5th March. > Thx, > ERic > > > On 20/02/12 09:28, Jentu Jain wrote: > > Hi, > > > > When would James 3.0 beta4 version be released? > > > > Regards > > > > ------------------------------------ > > Jentu Jain | Datacert, Inc. > > > > /Why are major companies rapidly migrating to Passport? Find Out Here > > <http://www.datacert.com/>/ > > > > Description: cid:[email protected] > > <http://www.datacert.com/feed.xml>Description: > > cid:[email protected] <http://twitter.com/datacert> > > > > -- > eric | http://about.echarles.net | @echarles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
