Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of at.silk@everis.com designates
 212.0.112.166 as permitted sender)
From: "at.silk" <at.silk@everis.com>
To: Tomcat Users List <users@tomcat.apache.org>
Subject: RE: Exception in CoyoteAdapter class
Thread-Topic: Exception in CoyoteAdapter class
Thread-Index: Ac7wEChny3iQuTXiSVOEsNyE+o6zDf//9vWA//31fQA=
Date: Wed, 4 Dec 2013 17:17:27 +0000
Message-ID: 
 <53C5AEB522377049B76D20E197C49AFEA9797B@INFPROMBX11.usersad.everis.int>
References: 
 <53C5AEB522377049B76D20E197C49AFEA97028@INFPROMBX11.usersad.everis.int>
 <529DB501.7020901@apache.org>
In-Reply-To: <529DB501.7020901@apache.org>
Accept-Language: es-ES, es-ES, en-US
Content-Language: es-ES
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Mark,

This is the application behaviour, and it only happens when the session has=
 expired. I cannot say why this method is still called if there is no sessi=
on at that time.

We just can assure that the exception is triggered by this piece of code, s=
ince handling the exception inside this method leads to a correct execution=
.

AT.

-----Mensaje original-----
De: Mark Thomas [mailto:markt@apache.org]=20
Enviado el: martes, 03 de diciembre de 2013 11:40
Para: Tomcat Users List
Asunto: Re: Exception in CoyoteAdapter class

On 03/12/2013 10:25, at.silk wrote:
> Hi,
>=20
> I contact you to talk about an exception we receive in a Tomcat class. Fe=
w days ago we get an error in an application integrated with Tomcat. We hav=
e tried to get information about it but we don't find any solution, so we w=
ould like to know if you are aware about this issue.=20
>=20
> First we describe our scenario:
> 1. User logs in the portal and remain static for more than 30 minutes (30=
 minutes is session expiration time).
> 2. Afterwards, he refreshes the webpage and session has been expired.
> 3. During the page reloading, an error occurs while executing the "parseS=
essionSslId" method because the "SSLSupport.SESSION_ID_KEY" is empty.
> 4. A blank page is displayed because the error is not caught.

How is that possible? If there is no SSL session the client should not be a=
ble to send a request to Tomcat since that would mean that the HTTPS connec=
tion had not been established. Since this code is only triggered when parsi=
ng a request from the client this error should never be observed.

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org