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: local policy)
Message-ID: <4E286CD3.4010209@web.de>
Date: Thu, 21 Jul 2011 20:15:47 +0200
From: smarto <smarto65@web.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Destroyed sessions without timeout or logout
References: <4E2703D4.7020909@web.de> <4E271D0C.3070408@kippdata.de>
In-Reply-To: <4E271D0C.3070408@kippdata.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Sender: smarto65@web.de

Thanks Rainer,

yea, the stracktrace is helpful ;) .... it was my first thought, to call 
the stacktrace.
But i withdraw it, because my guess was, that the
events and there stacktrace are "decoupled". I didn't even try it ... 
bad mistake

Best regards,

Martin


> On 20.07.2011 18:35, smarto wrote:
>> Hi,
>>
>> my SessionListener logs the creation and destruction of sessions.
> Then add logging the code stack and you will get an idea, where the
> invalidate originated. Something like
>
> log.info("Session destryoes"); changes to
> log.info("Session destroyed", new Throwable("Stack));
>
> Regards,
>
> Rainer
>


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