Subject | Re: [firebird-support] Re: FB 1.5 hang under load with events, same with 1.0 work fine |
---|---|
Author | Helen Borrie |
Post date | 2004-04-27T01:08:47Z |
At 12:15 AM 27/04/2004 +0000, you wrote:
channel. Perhaps sometimes you get the situation where two "matching"
ports (between client and server) are not available.
You can configure a single port through which event traffic will always
flow. See RemoteAuxPort in firebird.conf. Then open that port and disallow
any other traffic from using it. On the client, I think all that's needed
is for any personal firewall to permit traffic from the server's IP address.
I don't know why you wouldn't see the same problem with Fb 1.03, though
(where in fact you can't configure the RemoteAuxPort). So maybe your
network admin has closed too many boltholes....
/heLen
> > we are testing one of our apps over FB 1.5 (latest)Could it be a firewall problem? For events, Fb grabs a random port-to-port
> > this app use extensively events, with Firebird 1.0 all
> > works fine, under FB 1.5 after some time of good
> > work the server run at 100% CPU use and the clients
> > hangs waiting the server. Is this a know issue?
> > Thx for support.
> >
> > (Latest FB 1.5 on Windows 2000 Server sp3).
>
>Not useful, but I can confirm I have this happen about once every
>week or so, running FB 1.5 on Win 2000 SP3. Never saw it with FB
>1.03. I also use events. Yours is the third message about this today,
>so it must be real.
>
>Is there anyway we can isolate the cause?
channel. Perhaps sometimes you get the situation where two "matching"
ports (between client and server) are not available.
You can configure a single port through which event traffic will always
flow. See RemoteAuxPort in firebird.conf. Then open that port and disallow
any other traffic from using it. On the client, I think all that's needed
is for any personal firewall to permit traffic from the server's IP address.
I don't know why you wouldn't see the same problem with Fb 1.03, though
(where in fact you can't configure the RemoteAuxPort). So maybe your
network admin has closed too many boltholes....
/heLen