You could write an api program that would hit all threads on all
queues, only problem with this approach is that it will block ALL
operations on the server for all the queues you are hitting. This
would also have to be timed with the state expiration policy on the
firewall, which for most firewall
Just a few WAGs... I am not sure if these would cause DB IO for each
thread or not:
Maybe you could force the server to re-read is db? ( arsignal -g )
Maybe you could change an ARS object's helptext and try force the
server to shake the threads
You could also write a small api program t
ubject: Re: ARS 7/Oracle and Firewalls/Network devices
The best solution would be if ARServer had a configuration option, a
thread keep-alive if you will, that would do this. This would avoid
the busy system errors that sessions will get if all threads are busy.
Axton Grams
On 9/20/07, J.T. Shym
>
> -Original Message-
> From: Axton [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 19, 2007 10:25 PM
> Subject: Re: ARS 7/Oracle and Firewalls/Network devices
>
> The escalation is (was) single threaded; in order to send traffic over
> every db connection, you
ons open.
It does amaze me, though, that BMC can call ARS an "enterprise" product when
it behaves so badly with stateful firewalls.
J.T. Shyman
Column Technologies
Cell: 404-242-5407
-Original Message-
From: Axton [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 19, 2007 1
The escalation is (was) single threaded; in order to send traffic over
every db connection, you have to exercise every thread. Since the
escalation engine is single threaded, it will only occupy that one
thread. If you notice in the arerror.log that all filter errors
reported show 390693 as the r
Why not an afterhour escalation... instead..
Say every 10 minutes.. to do table queries or a report or two..
from 1800 - 0712 or something...
On 9/19/07, Axton <[EMAIL PROTECTED]> wrote:
>
> "Actually, now that I re-read your post I don't think putting a
> specific rule will side-step state check
"Actually, now that I re-read your post I don't think putting a
specific rule will side-step state checking."
Depends on your firewall and the rule. Typically, states are created
using only SYN packets, if state can be created on other packet types,
you are still using stateful packet inspection,
Axton,
Appreciate your input!
I should have mentioned that we've been up and down that highway and
haven't seen a blasted thing. (apologies to Glen Frey)
What you are saying is exactly what I thought and we've disabled the
idle timeout on the firewall. I know this ma
Your firewall is probably using state tracking to track which machines
are allowed to talk with one another and the timeouts associated with
state tracking are configured to time out after x seconds of
inactivity. Since many of the connections between the db and the
arserver are idle at night, the
Hello all,
Does anyone on this list have any experience with AR 7 on RHEL 4 and
Oracle 10g where the AR server and Oracle server are off two different
interfaces on a firewall?
The reason I ask: We are currently working in an environment where
the AR Server is in one VLAN, the Oracle
11 matches
Mail list logo
