>
> 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-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
