Try pairing up (logging) the null id with the actual requested resource
URL to see if there is an http request rather than an https one.
Andy.
On 01/07/2015 14:44, Alex Soto wrote:
I will need to do something like this yes, I will see how to enable on
mod_jk and ajp :)
Thanks.
El dc., 1 jul. 2015 a les 14:33, Romain Manni-Bucau (<[email protected]>)
va escriure:
Hi Alex,
Did you activated debug on both servers to see what was incoming?
Maybe also ensure versions are up to date but compatible.
Romain
Le 1 juil. 2015 01:21, "Alex Soto" <[email protected]> a écrit :
Hello I have a problem that I am sure it is not related with TomEE but
because I don't know what is happening I would like to share with you to
see if any of you have any idea.
I am configuring the typical Apache as frontend and TomEE as backend
solution. Currently Apache is configured with SSL and with mod_jk it
connects to TomEE using AJP. This works perfectly. The problem is that
inside my code I need to get the ssl session id:
String ssl =
(String)servletRequest.getAttribute("javax.servlet.request.ssl_session_id");
I don't know why but sometimes this attribute is null and sometimes not.
It
may return a null at first then stay like 10 requests working and then
stop
working again during some requests.
It seems that everything should be configured correctly since sometimes
works. Have you ever found something similar or knows what it can be
happening? Do you think that maybe the problem is on client (browser)
side?
Thank you so much,
Alex.
--
Andy Gumbrecht
https://twitter.com/AndyGeeDe
http://www.tomitribe.com
