> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Monday, June 20, 2016 11:32 AM
> To: Tomcat Users List
> Subject: Re: session-timeout and maxInactiveInterval
>
> On 20/06/2016 16:00, mw...@loftware.com wrote:
> > We are running 7.0.69 and Java 1.8.0_91.
> >
>
We are running 7.0.69 and Java 1.8.0_91.
We ran into an incident at a customer where the customer had set
session-timeout to 0 - which according to the servlet 3.0 spec, the session
should never time out. However, the customer was basically seeing the session
timeout immediately. When we chan
> -Original Message-
> From: Daniel Mikusa [mailto:dmik...@pivotal.io]
> Sent: Friday, February 06, 2015 8:06 AM
> To: Tomcat Users List
> Subject: Re: Issue when using tomcat JDBC Connection Pool with a shared
> resource
>
> On Fri, Feb 6, 2015 at 6:27 AM, Jean-Louis Mateo louis.ma...@
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Tuesday, January 13, 2015 1:05 PM
> To: Tomcat Users List
> Subject: Re: Occasional long wait for a JDBC connection
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Darren,
>
> On 1/13/15 11:49 AM, Darren Davis wrote
> From: Daniel Mikusa [mailto:dmik...@gopivotal.com]
> Sent: Monday, August 05, 2013 7:56 AM
> To: Tomcat Users List
> Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
>
> On Aug 4, 2013, at 2:14 PM, mw...@loftware.com wrote:
>
> >> From: Mark Eggers [mailto:its_toas...@yahoo.com
> From: Mark Eggers [mailto:its_toas...@yahoo.com]
> Sent: Friday, August 02, 2013 5:28 PM
> To: Tomcat Users List
> Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
>
> On 8/2/2013 1:30 PM, mw...@loftware.com wrote:
> >> From: Michael-O [mailto:1983-01...@gmx.net] Sent: Friday, A
> From: Michael-O [mailto:1983-01...@gmx.net]
> Sent: Friday, August 02, 2013 3:28 PM
> To: Tomcat Users List
> Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
>
> Am 2013-08-02 21:24, schrieb mw...@loftware.com:
> > I expect that by putting the SQL Server JDBC4 driver jar
> > (s
I expect that by putting the SQL Server JDBC4 driver jar (sqljdbc4.jar) into
${CATALINA_HOME}/lib, that the driver would be automatically available upon
server start. As expected, this works in 6.0.33, but fails in 6.0.35. It
seems that the fix to Bug 51640 is the cause of this, and in fact, s
