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 (athena.apache.org: domain of hilavalensia@gmail.com
 designates 209.85.214.45 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=sf8/mnX59CD0sksTu7XWtlfHndFn/qnn8EFRlNbyaUqesNzPJNWCHbm4OuG5DokB6H
         nelfd3JDnqBWkA4A9WL5QgeyBaXYvzND4p6Vc25UMv3qF3NR71Fa0Y39ZTecibowoXEM
         zj7uMTa1U3FCKuLIgejC9BOWQ3pouJSgBCKPg=
MIME-Version: 1.0
In-Reply-To: <4DD2C4AE.5090709@verizon.net>
References: <BANLkTik60s_nP_C4JFbk60TRG-XJsGrQww@mail.gmail.com>
 <4DD28179.8030203@ice-sa.com>
 <BANLkTin7nhpT0snaqGZNdj=t9nARVEo42w@mail.gmail.com>
 <BANLkTimVGb_hDUD4y--kbAYnOdzjOCTtLA@mail.gmail.com>
 <4DD2C4AE.5090709@verizon.net>
From: =?UTF-8?B?15TXmdec15Q=?= <hilavalensia@gmail.com>
Date: Tue, 17 May 2011 22:06:41 +0300
Message-ID: <BANLkTimWV8ng6mRcK6ORajAFp34TkMgi6w@mail.gmail.com>
Subject: Re: Application crash after Migrate to different ESX
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=0016e6dbe825af12c604a37d7a21

--0016e6dbe825af12c604a37d7a21
Content-Type: text/plain; charset=ISO-8859-1

>
> how can I abruptly break all connections between application and DB?
>> the only way I know is take the server out of the Load balancer so no new
>> users can get to the server + the LB kicks the users that are already
>> connected.
>>
>
> Pulling the network cable at the db server would do it.
>
> It's a production environment. I can't do it.
>
>
>>
>>> I suspect that
>>> a) at webapp end you will have a lot of unusable connections in the
>>> pool. If you did not forget to configure validation, they will be
>>> replaced by valid connections by the next time when you try to get
>>> them from the pool.
>>>
>>>
>> I haven't configure validation cause in our production environment it has
>> proven to be harmful (freezes application)
>>
>>
>>> b) at the DB end you will have a number of aborted transactions. How
>>> it handles them depends on your DB.
>>>
>>>
>> How can I see the aborted transactions?
>> how can I check the configuration that handles it?
>>
>
> That's something the db admin will have to tell you.
>
>
> Each time I come to them with specific questions about connections and how
> it handles them (stuff that is more application and less infrastructure),
> they don't know what to say, since they are DBA infra and not applicative.
> if this is the only way to check the issue, I will ask the applicative DBA's
> (they are external, so we don't approach them with every issue unless they
> are our last resort)
>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--0016e6dbe825af12c604a37d7a21--