On Tue, Oct 17, 2017 at 3:44 AM, Keiichi Fujino wrote:
> Hi
>
> You have set factory="org.apache.tomcat.jdbc.pool.DataSourceFactory".
> In other words, you do not use (tomcat)DBCP, you are using Tomcat jdbc-pool.
That's what I meant sorry. Was comparing to commons-dbcp and went
dyslexic on the ac
On 17/10/17 15:32, Maor Shiffman wrote:
> No, we are using Apache web server in our production environment, but this
> issue also reproduces in our dev environment which doesn't use a web server.
> I have further isolated the issue to be in 8.0.45.
> Could this be related to the fix of
> https://
On 10/16/2017 1:27 PM, Net Dawg wrote:
Profuse apologies. We are unable reproduce this. However out tests were
failing for another reason.
8.5.23 returns 400 error with header "HTTP/1.1 400" where as version 8.0.47 returns the same as
"HTTP/1.1 400 Bad Request". When the tests check for th
On Tue, Oct 17, 2017 at 5:27 PM, Igal @ Lucee.org wrote:
> Maor,
>
> On 10/17/2017 6:32 AM, Mark Thomas wrote:
>
>> On 16/10/17 21:50, Maor Shiffman wrote:
>>
>>> Hi,
>>>
>>> We've recently upgraded our servers from 8.0.43 to 8.0.45 and URLs with
>>> consecutive double slashes that used to work s
Maor,
On 10/17/2017 6:32 AM, Mark Thomas wrote:
On 16/10/17 21:50, Maor Shiffman wrote:
Hi,
We've recently upgraded our servers from 8.0.43 to 8.0.45 and URLs with
consecutive double slashes that used to work such as
http://www.domain.com/auth//signin.html stopped working - getting a 404.
This
On 16/10/17 23:08, john.e.gr...@wellsfargo.com.INVALID wrote:
> All,
>
> Hopefully I can explain this clearly...
>
> The short question is that my client is sometimes not getting the 0-length
> chunk at the end of the response from Tomcat, so my connections don't get
> reused.
>
> My Tomcat se
On 16/10/17 21:50, Maor Shiffman wrote:
> Hi,
>
> We've recently upgraded our servers from 8.0.43 to 8.0.45 and URLs with
> consecutive double slashes that used to work such as
> http://www.domain.com/auth//signin.html stopped working - getting a 404.
> This happens on our production environment r
Hi
You have set factory="org.apache.tomcat.jdbc.pool.DataSourceFactory".
In other words, you do not use (tomcat)DBCP, you are using Tomcat jdbc-pool.
In DBCP, the default of rollbackOnReturn attribute is true.
However, in Tomcat jdbc-pool, the default of rollbackOnReturn( and
commitOnReturn
) att