Gateway (EProxy) timeouts/lockups
Is anyone experiencing frequent Gateway EProxy timeouts or lockups ?
We have several gateways around the world all coming into a single
Portal/Profile server.The corporate WAN in most instances provides
acceptable bandwidth to the Portal server, but there will at times be heavy
congestion.
The problem we see as identified by iwtGateway logs is numerous EProxy
errors that perhaps indicate a network timeout...
ERROR: EProxyConnection cannot set TcpNoDelay on Socket[address of remote
IP,port=xxxx,localport=443]
java.net.SocketException: Invalid Argument
This error is not fatal, and the gateway will continue on eventually.
But - if this error occurs 3 times within 3 minutes, Eproxy will hang and
the Gateway will refuse all further connections until restarted. The Eproxy
Java process itself doesn't crash, as 'ps' shows it is still running. The
gateway watchdog process also does not catch this condition.
The fatal error message that results is:
ERROR: EProxyConnection cannot accept new connection on
ServerSocket[addr=0.0.0.0/0.0.0.0/port=0,localport=443]
java.net.SocketException: Software caused connection ABORT
We have also exhausted all the suggested tweaks iPlanet tech support has
provided. The best we have come up with is to add our own watchdog to
monitor iwtGateway logs for this error and to restart the gateway
automatically.Not foolproof, but a big help.
I was just wondering if anyone else experienced this problem and perhaps
found an adjustment to fix it for either SP2 or SP3?
Thanks,
Gary
[1689 byte] By [
708803] at [2007-11-25 4:31:17]
What are the other error messages you see when subsequent connections are
refused
Karthik !
Gary Beshara wrote:
> Is anyone experiencing frequent Gateway EProxy timeouts or lockups ?
>
> We have several gateways around the world all coming into a single
> Portal/Profile server.The corporate WAN in most instances provides
> acceptable bandwidth to the Portal server, but there will at times be heavy
> congestion.
>
> The problem we see as identified by iwtGateway logs is numerous EProxy
> errors that perhaps indicate a network timeout...
>
> ERROR: EProxyConnection cannot set TcpNoDelay on Socket[address of remote
> IP,port=xxxx,localport=443]
> java.net.SocketException: Invalid Argument
>
> This error is not fatal, and the gateway will continue on eventually.
>
> But - if this error occurs 3 times within 3 minutes, Eproxy will hang and
> the Gateway will refuse all further connections until restarted. The Eproxy
> Java process itself doesn't crash, as 'ps' shows it is still running. The
> gateway watchdog process also does not catch this condition.
>
> The fatal error message that results is:
>
> ERROR: EProxyConnection cannot accept new connection on
> ServerSocket[addr=0.0.0.0/0.0.0.0/port=0,localport=443]
> java.net.SocketException: Software caused connection ABORT
>
> We have also exhausted all the suggested tweaks iPlanet tech support has
> provided. The best we have come up with is to add our own watchdog to
> monitor iwtGateway logs for this error and to restart the gateway
> automatically.Not foolproof, but a big help.
>
> I was just wondering if anyone else experienced this problem and perhaps
> found an adjustment to fix it for either SP2 or SP3?
>
> Thanks,
>
> Gary
Guest at 2007-6-30 21:18:29 >
