Re: Encrypted jdbc

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harrie, On 4/11/16 4:10 AM, Harrie Robins wrote: >> From MariaDB manual: > > have_openssl > > Description: Before MariaDB 10.0.1, have_openssl was an alias for > have_ssl. Since MariaDB 10.0.1, comparing have_openssl with > have_ssl will indicate

Re: Tomcat8 with Java8 session mix up issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, On 4/11/16 8:56 AM, David kerber wrote: > On 4/11/2016 8:54 AM, Olaf Kock wrote: >> >> >> Am 11.04.2016 um 14:51 schrieb Nilesh Dabholkar: >>> Hi, >>> >>> Has anyone come across issues related mixing up user session >>> on Tomcat 8.0.26?

async servlet, tomcat 8.0.33, behind apache

I am trying to use async servlet, tomcat version 8.0.33, sits behind apache, without async servlet never had any issues, now I am trying out async servlet, see issues with async servlet, connection to and from this servlet is taking very long time, all pages connect to this servlet to receive

Re: JSESSIONID changed without notice

Am Montag, den 11.04.2016, 10:22 + schrieb Arno Schäfer: > Hi Felix, > > thank you very much for that hint. > > > When a session gets 'authenticated' its id will change to prevent > > session fixation attacks. If you are interested in the events telling > > you the change you have two

RE: Tomcat8 with Java8 session mix up issue

I'm on Tomcat 8.0.26 You're right, my first instinct was to check the application itself. However, it is an intermittent issue and does not happen regularly or cannot be recreated at will. So, I'm wondering if anyone else has encountered a similar problem. Regards, Nilesh -Original

Re: Tomcat8 with Java8 session mix up issue

On 4/11/2016 9:07 AM, Nilesh Dabholkar wrote: So, are we saying that it has more to do with the application itself rather than Tomcat? Yes, that's far more likely. If Tomcat itself had a bug like that, every user would be screaming. Are you on the latest version of TC (8.0.33, I think)?

RE: Tomcat8 with Java8 session mix up issue

So, are we saying that it has more to do with the application itself rather than Tomcat? We're also using Spring MVC framework which handles session management. Regards, Nilesh -Original Message- From: David kerber [mailto:dcker...@verizon.net] Sent: 11 April 2016 13:57 To: Tomcat

Re: Tomcat8 with Java8 session mix up issue

On 4/11/2016 8:54 AM, Olaf Kock wrote: Am 11.04.2016 um 14:51 schrieb Nilesh Dabholkar: Hi, Has anyone come across issues related mixing up user session on Tomcat 8.0.26? We've been seeing intermittent issues whereby user session are getting mixed up after upgrading to Tomcat8 and Java8.

Re: Tomcat8 with Java8 session mix up issue

Am 11.04.2016 um 14:51 schrieb Nilesh Dabholkar: > Hi, > > Has anyone come across issues related mixing up user session on Tomcat 8.0.26? > > We've been seeing intermittent issues whereby user session are getting mixed > up after upgrading to Tomcat8 and Java8. Whenever I've seen content for

Tomcat8 with Java8 session mix up issue

Hi, Has anyone come across issues related mixing up user session on Tomcat 8.0.26? We've been seeing intermittent issues whereby user session are getting mixed up after upgrading to Tomcat8 and Java8. I could find similar issues logged on Tomcat 6 but not on any of the later versions. Any

Re: JSESSIONID changed without notice

Hi Felix, thank you very much for that hint. > When a session gets 'authenticated' its id will change to prevent > session fixation attacks. If you are interested in the events telling > you the change you have two possibilities: ok, that explain, what I see :-) > 1. Use servlet api 3.1 and

Re: Tomcat Windows Services issue

On 10.04.2016 22:14, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Saurav, On 4/7/16 11:24 AM, Saurav Maulick wrote: On Thu, Apr 7, 2016 at 6:11 AM, André Warnier (tomcat) wrote: On 07.04.2016 00:14, Saurav Maulick wrote: Hi All, I am using

RE: Encrypted jdbc

Hi! >From MariaDB manual: have_openssl Description: Before MariaDB 10.0.1, have_openssl was an alias for have_ssl. Since MariaDB 10.0.1, comparing have_openssl with have_ssl will indicate whether YaSSL or openssl was used. If YaSSL, have_ssl will be ON, but have_openssl will be OFF.