Broken Connection between Reverse HTTP Gateway and Internal Server

Hello Support Team,

we have set up a Reverse HTTP Gateway, evertything has been worked for last two months. But last week and today, the external Clients-Requests dont be forwarded to the Internal Server.This Message has be shown in the Log:

7 Requests are waiting (for an available connection) to be forwarded across Registration Port 6666 to an Internal Integration Server

I have to login on Internal Server, and deactivate and finally activate the well-setted HTTP Port (Registration Internal). Afterwards the Request will be forwarded to the Internal Server. Why nedd I to do this (disable the Port / then enable the Port)?

Especially our Customer has to tell us, that they got a Time-out Session.

Now my Question:
How can we monitor the Reverse HTTP Gateway and Internal Server?

Best Regards

Iftikhar Ahmad

You can set up a monitor ping on the ports (RI side) that way timeouts or ports hung can be monitored alerted unless you don’t any OFI installed.

Also there are differrent reasons that would stop working and you may need to tune up the RI and Internal IS threads/memory usage/keep alive timeouts/enable private thread pool configurat on the External/Internal IS ports.

Also set this on RI side:
Extended Settings:
watt.net.clientKeepaliveTimeout=300
watt.net.maxClientKeepaliveConns=0

Apart from above make sure your IS servers has all latest fixes (core and protocol fixes) patched/ installed in order for SAG support resolves it faster.

HTH,
RMG

In addition to RMG suggestion,

please keep the same user time-out in internal servers.

Thanks,
Rankesh

Solution by SAG:

Also fine tune the servers and port resources:

Explain about the message “[ISC.0064.0027C] XX Requests are waiting”


If the Internal Server detects that there have been no requests
received from the Reverse Gateway Server on a given connection after a
specified amount of time, the Internal Server will close the connection
and attempt to reopen it. This time period is controlled by the
following property on the Internal Server:

watt.server.rg.internalregistration.timeout

Specifies the time (in seconds) the Internal Server will wait
before closing an unresponsive connection to the Reverse Gateway Server.
The default is 0, which means do not time out (a timeout period of
infinity).

If the Reverse Gateway Server does not make a request to the
Internal Server on a given connection within a specified amount of time,
the Reverse Gateway Server will make a ping request to the Internal
Server on that connection. This time period is controlled by the
following property on the Reverse Gateway Server:

watt.server.rg.gateway.pinginterval

Specifies how often (in seconds) the Reverse Gateway Server will
send a ping request to the Internal Server. The default is 60 seconds.

Note: The ping interval on the Reverse Gateway Server must be
less than the timeout period on the Internal Server. For example, if the
timeout period on the Internal Server is 180 seconds, the ping interval
must be less than 180 seconds.

Thank You Iftikhar :mrgreen:

Thanks for the update Iftikhar!..It is a precious info: