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)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=x8sf4DLoc7vqo9KB0TCmf5zjzgsA+StfXavPABp+kxuQwvwVeL+vrGzDpzEw+2y0OMNvbbVGcZL66B3Pcg3sLS0HXpkJ91Y4YnY6oQcMQgDXSpxb6lBUN1nEBo08fK8K74Vn9cnD4ytd6iiL0Jf0XUNENJTLgW6XpquMSLw3PUw=;
Message-ID: <233331.30664.qm@web113502.mail.gq1.yahoo.com>
Date: Mon, 15 Nov 2010 23:34:02 -0800 (PST)
From: Amol Puglia <amolcpuglia@yahoo.com>
Subject: Re: Tomcat Going down Frequently
To: Tomcat Users List <users@tomcat.apache.org>
In-Reply-To: <4CE1610B.9060704@pidster.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1824924220-1289892842=:30664"

--0-1824924220-1289892842=:30664
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Pid,

Thanks for the updates.It would be great if you could let us know whether t=
he issue is in application server or application.

Also we are using apache to load balance tomcat instances using following m=
odules.

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so

Is there anything we have to tune configuration on apache,tomcat or applica=
tion,please suggest.


--- On Mon, 11/15/10, Pid <pid@pidster.com> wrote:

From: Pid <pid@pidster.com>
Subject: Re: Tomcat Going down Frequently
To: "Tomcat Users List" <users@tomcat.apache.org>
Date: Monday, November 15, 2010, 10:04 PM

On 15/11/2010 11:03, Amol Puglia wrote:
>=A0 =A0 =A0 =A0=A0=A0at org.apache.catalina.session.StandardSessionFacade.=
getAttributeNames(StandardSessionFacade.java:120)
>=A0 =A0 =A0 =A0=A0=A0at com.ericsson.mars.jspbean.LoginBean.logout(LoginBe=
an.java:2366)
>=A0 =A0 =A0 =A0=A0=A0at com.ericsson.mars.jspbean.LoginBean.valueUnbound(L=
oginBean.java:2450)

The problem is in your HttpSessionBindingListener LoginBean, it appears
to be operating on the session object after the session has been
invalidated.

I don't know whether this could take Tomcat down, unless you've
included* a System.exit call in a catch - which seems to be popular
again all of a sudden.


p

* which is A Really Bad Idea.
=0A=0A=0A      
--0-1824924220-1289892842=:30664--