Keep Alive Timeout

Hi, i have check the CCM logs and it seems that there are a lot of messages like keep alive time out and the ip phone get unregistered. Also there is a switch thats is sending a lot of broadcast to my core switch (more than 1 million of broadcast in less than an hour) do u think that switch is the problem?
Thanks in advanced

Hi pepito,
That switch has IP Phones connected to it?
Other IP Phone that are in other switch or not suing that switch for communication work fine?
What is the topology?

Similar Messages

Need help with HTTP keep-alive

Hi folks!
I have this very simple web server and I would like to add keep-alive support. I've been trying to get my head around it for a while and could need some help (I found this question in the archive, but those replies didn't help)...
This is my starting point (stripped down to the basics):
/* A listener thread that accept incoming requests by creating new request handlers */
public class HTTPListener implements Runnable
    private ServerSocket serverSocket;
    public HTTPListener(int port)
        // Try to create a server socket on specified port
        try
            serverSocket = new ServerSocket(port, 0);
        catch (IOException ex)
            System.err.println("Oops!");
    public void run()
        while (!Thread.interrupted())
            try
                // Listen on server socket until a request arrives
                Socket s = serverSocket.accept();
                // Create handler to service request
                RequestHandler h = new RequestHandler(s);
                new Thread(h).start();
            // Server socket closed when listening
            catch (SocketException ex)
                Thread.currentThread().interrupt();
            // Failed to close socket or failure during server socket accept
            catch (IOException ex)
                System.err.println("Failed to accept request");
        try
            serverSocket.close();
        catch (IOException ex)
            System.err.println("Hmpf...");
/* Handler that prints out requests and always answers with status 200 */
public class RequestHandler implements Runnable
    private Socket socket;
    public RequestHandler(Socket s)
        socket = s;
    public void run()
        System.out.println(">>> New request handler");
        try
            BufferedReader reader = new BufferedReader(new InputStreamReader(socket.getInputStream()));
            String str;
            while ((str = reader.readLine()) != null)
                System.out.println(str);
            sendDummyReplyWithKeepAlive();
            reader.close();
            socket.close();
        catch (IOException ex)
            System.err.println("Crap, got an exception!");
}When I run the server (which in reality has a little more to it) I never get more than one request printed for each ">>> New request handler", which is not surprising!
Now, with keep-alive support I expect to get consecutive requests from the same client printed by the same handler instance. What I have to do (as I've understood from my readings) is to modify the while loop in the request handler that reads from the socket so that it spins until the connection is closed by the client (or a keep-alive timeout occurs) and blocks while there is nothing to read.
Perhaps I'm being stupid now, but how do I actually do this?

ejp wrote:
and also an incorrect implementation of the timeout period. This code will still wait forever if no data arrives.You're right... actually I didn't mean to put that while loop there! What I meant was simply
if (!reader.ready())
    wait(keepAliveTimeout);
if (!reader.ready())
    break mainLoop;
// If we get here there is a new request to read...and I agree that it's ugly, that's why I'm asking you guys for help!
setSoTimeout() is of course a way to go... didn't think of that although I have kind of already added it to my code but with a different timeout. Thanks!
Last question then is:
does reader.readLine() block like reader.read(), or do I have to use the latter?
I would test for myself I could, but at the moment I can't...

Weblogic shutting down keep-alive socket improperly?

We were sometimes experiencing strange IE behaviour when surfing on webapps on our Weblogic application servers. After investigation we found that IE has a bug in its resend behaviour, so when resending a POST request it sends the headers (including Content-Length) but forgets the form-data. This causes the server to time out waiting for the data. (Note: We are using Win2K and IE6 SP1 on the clients.)
The IE resend is triggered on a default installation when 31-59 seconds have passed since the last request.
This is because IE will try to reuse a socket that has been told to keep-alive until it has been idle for 60 seconds but WLS will by default close kept-alive sockets when they have been idle for 30 seconds. So in the range 31-59 seconds IE will consider the socket alive but WLS has closed it.
The resend bug is really an IE bug and doesn't concern WLS, but then I saw that IE would function correctly with an Apache server with a default keep-alive timeout of 15 seconds.
Using Ethereal I could get the information depicted in the tables below:
Weblogic with keep-alive timeout 30 secs
old socket
Time 00 : User navigates : IE POST request -> WLS, WLS HTML -> IE
Time 30 : Socket times out : (no network traffic)
Time 45 : User navigates : IE POST request -> WLS, WLS TCP_FIN -> IE
new socket
Time 45 : : IE resends POST request without form-data
Apache with keep-alive timeout 15 secs
old socket
Time 00 : User navigates : IE POST request -> Apache, Apache HTML -> IE
Time 15 : Socket times out : Apache TCP_FIN -> WLS
new socket
Time 45 : User navigates : IE POST request -> Apache, Apache HTML -> IE
To summarize, IE handles Apache well as Apache sends a TCP FIN telegram (to close the connection) as soon as the kept-alive socket times out.
Therefore IE never tries to reuse the socket but instead starts on a fresh one on the next navigation and a resend is never necessary.
Weblogic, on the other hand, doesn't send the TCP FIN (connection close) telegram until IE actually tries to use the connection even though it timed out 15 seconds earlier. In this case IE needs to resend the POST request and this is when the form-data is forgotten.
So, my question now is if WLS behaviour could be caused by not shutting down kept-alive sockets properly at keep-alive timeout? Or why are there no TCP FIN telegrams sent at timeout?
Mike Wilson

After doing some more investigation I have found that the "silent" shutdown of keep-alive sockets is only seen on the Linux version. The Windows version of Weblogic 8 behaves correctly, like Apache on Linux, but Weblogic on Linux does not...
Anyone can confirm if this is to be considered a bug?

Disabling Keep Alive

We are using GWT with Glassfish and Sun Web server. We're encountering occassional problems causing the servlet to fail with "Client did not send xxxx bytes" exception.
I read in another post elsewhere that people have solved this problem in Glassfish-Apache configuration with the following settings:
SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1
Can someone tell me what is the equivalent setting in Sun Webserver?
Thanks

Try "set-reverse-proxy-prop"
[http://docs.sun.com/app/docs/doc/820-2204/set-reverse-proxy-prop-1?l=en&a=view|http://docs.sun.com/app/docs/doc/820-2204/set-reverse-proxy-prop-1?l=en&a=view]
* use-keep-alive Indicates whether the HTTP client should attempt to use persistent connections. The default value is true.
* keep-alive-timeout The maximum number of seconds to keep a persistent connection open. The default value is 29.
* always-use-keep-alive Indicates whether the HTTP client can reuse the existing persistent connections for all types of requests. The default value is false, indicating that persistent connections will not be reused for non-GET requests or for requests with a body.
* protocol The HTTP protocol version string. By default, the HTTP client uses either HTTP/1.0 or HTTP/1.1 based on the contents of the HTTP request. In general, you should not use the protocol parameter unless you encounter specific protocol interoperability problems.
...So, probably this will work for you:
set-reverse-proxy-prop use-keep-alive=false protocol="HTTP/1.0"

Keep alive TCP setting for port 3998 to avoid fw timeout?

Hello,
in our new DS6.1 env, replication between the master DS is using port 3998 through several firewalls. If there are no changes to the DB (we are still testing), the connection seems to time out on the firewall and the status of the remote masters in the SMC drops to "stopped" even though they are still running. If one clicks on the DS entry in the SMC, it seems to set up a fresh TCP connection and the status is ok again.
Is there a way to define a keep-alive setting for these connections ?
TIA,
heinz

DS 6.3 has bug 5087249 against it for the missing SO_KEEPALIVE socket option.
This bug was fixed a long time ago in the DS 5.x series which got "unfortunately lost" on the way
to the 6.x release :-(
If you have a valid Sun Support contract you can request a hotfix for this bug 5087249 in
DS 6.3 (or the soon to be released 6.3.1), by raising a support service request.
A similar missing SO_KEEPALIVE socket option bug exists in the DPS 6.3 server,
bug 6782659 is open against this and if you have a valid Sun Support contract you can
request a hotfix for this bug 6782659 in DPS 6.3 (or the soon to be released 6.3.1).
Without a valid support contract, I'm afraid you'll have to wait until the next official patch
release of both these servers (DPS & DS) after the 6.3.1 which does not contain these 2 fixes.
This will most probably be at least one year into the future from present.
The problem with CLOSE_WAITs DPS issue is fixed in the same hotfix for bug 6782659 (which
contains many connection handling bug fixes/enhancement in addition).
Hope this helps.

Changing Default "Keep Alive" & " Max Processing Time" values in SMICM

Dear Experts
As you aware the default values in SMICM --> Go to --> Services The default values "Keep Alive" & " Max Processing Time" of services like HTTP & HTTPS is 30 sec & 60 seconds respectively.
Every times when we restart application server - we are increasing the time values manually. once we restart they will be reset to original 30 & 60 sec respectively.
I want to make customozed values permanently which should not be lost even after restart of application server.
Please Help
Regards
PR

If you have not set the PROCTIMEOUT parameter, TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout. Also, as of release 6.40, the keepalive timeout is limited to a maximum of 30 seconds.
In a system where the default timeout settings of 30 seconds for the keepalive timeout and the processing timeout are not sufficient because of long-running applications, we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independently of each other. In addition, we recommend that you do not set the TIMEOUT value higher than necessary, for example, to the usual default value of 30 seconds.
We recommend, for example, the following settings:
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600
to allow a maximum processing time of 10 minutes.
Thanks,
Tanuj

Http keep-alive with SOAP webservices

Just had an interesting experience with a web service setup behind UAG...under low load conditions all SOAP responses were coming across with no issue...once a high load was introduced by the client app the behavior changed where an initial request was
processed and subsequent requests were rejected by UAG with a Bad Parameter : Length message...but high load (relatively) on a web browser ran without issue...the client app had to wait ~100 seconds before the next request would process correctly...browser
works - app has problems...turns out it was the keep-alive "default" settings on both the client app server, as well as my web service in IIS...so -apparently UAG thought the 2nd (and subsequent < 100 seconds) were a parameter of the first request...and
was way too long and got rejected...I unchecked the keep-alive enabled box on the http response header (set common headers) and all is fine now! Apparently the browsers were closing the connection with each page load and the service responded appropriately
- so it looked like all was well. Using SOAP UI revealed the error...but it also had it's connection set to keep-alive...once that was disabled in SOAP UI all requests ran correctly...that's when I poked around and found that response header setting.

ejp wrote:
and also an incorrect implementation of the timeout period. This code will still wait forever if no data arrives.You're right... actually I didn't mean to put that while loop there! What I meant was simply
if (!reader.ready())
wait(keepAliveTimeout);
if (!reader.ready())
break mainLoop;
// If we get here there is a new request to read...and I agree that it's ugly, that's why I'm asking you guys for help!
setSoTimeout() is of course a way to go... didn't think of that although I have kind of already added it to my code but with a different timeout. Thanks!
Last question then is:
does reader.readLine() block like reader.read(), or do I have to use the latter?
I would test for myself I could, but at the moment I can't...

Keep alive using plain DHCP

Hi. My ISP assigns IPs using DHCP and then requires a manual login via an HTML form. After that you will be automatically logged out after some time of inactivity.
I'm looking into buying the WRV200 and wonder if I can set it up to remain connected despite user inactivity. I see it has keep alive for PPPoE etc, but I can't use PPPoE.
Is there any other way to keep the connection alive? By creating a VPN tunnel and set a key lifetime lower than my ISPs timeout??? Or does the VPN disconnect after some inactivity too...?
Thanks in advance.

I keep the same IP for months at a time, so that is not the problem.
The problem is that after 1 hour (or so) with no traffic sent from my IP, all the traffic from my endpoint is blocked until I manually log in again via a web form that, I am redirected to whatever URL I enter in the browser.
So if there is any way to make the router send a package every x minutes, I would stay logged on.
(IPSec key exchange would be such a package, if those are sent even when the tunnel is not in use from any computer on my LAN.)
There is software avalable for the PC that sends these keep alive packages, but I want the router to send them so that I can check my e-mail using my WLAN enabled cell phone even though I have had the PC turned off for hours.

Keep-Alive Portlet

Does anyone know of a keep-alive portlet that will keep the users session alive while they are on a specific page? My problem is that the users are getting logged off of the portal after 20 minutes of inactivity, so what I'd like to do is have a portlet that will post back behind the scenes every 5 minutes or so, in order to keep the portal from logging the user off. Does anyone know of any such portlets?
Thanks
-Ben

Couple of questions:
* What version of the portal are you using?
* Is the portal session timing out or is this a specific portlet?
The portal's session timeout can be controlled by editing config files and restarting. For a portlet - if you're experiencing a session timeout, can you bump up session duration through the remote web server? For portlets we control we usually try to match remote portlet session timeout to the portal's timeout. Since we try to do everything as a gatewayed portlet this usually works well for us.
Thanks,
Eric

LDAP keep-alive connection ? (use of ldap_io_fns)

Hi there,
I am facing a new req. from network security guys that want to close 'idle' connections that crosses firewalls. But as I do use persistent search connection which are not very 'busy' => i.e. not enough traffic to be kept open by FireWall rule.
Consequence my client could not 'detect' this cut of connection and do not receive any more the 'updates' through persistent search.
I am now trying to init my connection setting optional io_fns structure changing the socket func by my socket func that do create a keep-alive socket.
But it does not bind properly ... Init seem ok but bind never get out. LDAP receives bind and do log it but seem not able to respond properly ...
Any idea on how to use this io_fns struct ?
Many thanks.
Hedi.
.

the problem is not that process is in foreground or background: the problem is the timeout: I need to avoid timeout, because the idea is to launch the report and then go out for lunch So I need to find a way in the code to advise the system that user has not to be logged out.
Thanks
Gabriele

Nexus 7000 - Moving vPC keep alive

We have two Nexus 7010 switches running a vPC domain between the two switches. On one of the 7010B, the peer keep alive (from the mgmt VRF) is connected to a 3560B *and* that 3560B also has a data connection back to the same 7010B. Everything is fine with that setup.
Our second 7010A, the peer keep alive link is also connected to a coresponding 3560A switch. However, that 3560A switch is not connected to 7010A.
I want to move the uplink from the 3560A from where it is to the 7010A which will break the keep alive. However, I will not be breaking the vPC peer link as it is a pair of 10G connections between the two 7010 switches.
I have read that the vPC won't come up unless the peer keep alive is present, but it wasn't clear about taking down the keep alive link momentarily. Moving the cable would be quick, but I know the mac table will need to update since 7010B switch will now see the keep alive across it's peer link instead of some other direction.
Can I take the peer keep alive link down providing the peer link stays up?
We are running kickstart and system version 5.0(3).
Thanks!
/alan

Peer keepalive works on UDP port 3200 over IP with 1 sec interval and 5 sec timeout.
Iit is not requirement to have peer-keepalive destination IP in same subnet but if you do not have it in same subnet then you need to make sure you route it properly and your IP routed infrastructure that carries keeplive satisfies above requirement to make sure not a single event cause on that IP infrastructure causes keeplives to loose packets since peer-keepalive is UDP it is not reliable delivery method.
Recommendation in past i heard was to use your managemet ports as peer-keepalive. But one problem happens during ISSU with dual sup, the each supervisor reboots and after it comes up role of active and standby gets switch at the end. So If you did not connect two managment ports(one from each supervisor) to your management network then you will loose keepalives during software upgrade because supervisor switch over occurs and new maangement port becomes active.
So second recomendation is to create one peer-keepalive vrf so that it will have its own address space, if you have M1 1 gig card in each switch then connect one cable between switch and assign IP address (like 1.1.1.1-2/30) and put it in peer-keepalive vrf. With this set up during ISSU you do not loose peer keepalives because line cards does not need to reboot and your peer-keepalive UDP traffic will not depend on any other switch or router.

Keep alive connection

Hi,
I write a report that works on a lot of data and when it starts, it takes about an hour or two for processing. The problem is that on the system there is a timout of 20 minutes of inactivity after which the use il logged out.
The question is: is there a way by code to advise a sort of keep alive so that user is not logged out?
(I can't change the timeout on the system for security issues)
Thanks
Gabriele

the problem is not that process is in foreground or background: the problem is the timeout: I need to avoid timeout, because the idea is to launch the report and then go out for lunch So I need to find a way in the code to advise the system that user has not to be logged out.
Thanks
Gabriele

"Keep Alive" parameter for listener?

Hi all,
we have following problem:
From time to time the client (oracle forms 6i patch 18) gets the error message ORA-03114. Te solution is only to kill forms application and start it again.
This hangs probably on the network breaks in the communication (over VPN) with the database.
Is there any parameter for listener like "Keep alive" or else, which can rebuild the connection once it lost?
Best regards

Paste this into the SQLNET.ORA on the application server or the server that is making the SQL calls to the database.
Trace_level_client=16
Trace_directory_client=<path_to_the_trace_directory> # use the full path to the trace directory
Trace_unique_client=on
Trace_timestamp_client=on
Then review the trace or you can try the keep alive in windows
Use the standard TCP KeepAlive on Windows
1. Open the registry under:
HKEY_LOCAL_MACHINE: SYSTEM: CurrentControlSet: Services: Tcpip:
Parameters
2. Add KeepAliveTime : REG_DWORD to the registry
3. Set the value to a reasonable timeout.(decimal and NOT Hex) Like 480000 equals 8 minutes or 120000 equals 2 minutes etc etc.
- Save this
- Reboot

TCP KEEP ALIVE

Hello we have a problem with TCP/IP keep settings.
We have an apllication that after a while (2 hours) doesnt keep its connection,And after that we are taking of timeouts and disconnection from this application.We saw some threads that there a registery TCP/KEEP ALIVE,we already change this registery but
it doesnt help still.Could it be any other solution?Or advice?

I want to configure it to a lower value so that the connection is not closed by routers/firewalls assuming the connection to be idle.For all TCP clients and servers?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime 30000 30 seconds is an absurdly low value. Routers and firewalls will typically close connections after an hour, if at all. So setting it to 30 minutes should be adequate. Setting it as low as you have only exposes you to more network problems: if someone has a cable out for 30 seconds you will get disconnected, even if the cable was put back after 31 seconds and even if your application doesn't actually exchange data every 30 seconds. Don't do this.
Is there a standard way in which the keep alive time can be configured on all OS platforms? No.
If not, is this a standard way of changing keep alive time for java applications on windows?The registry keys might differ from version to version. It's a Windows question, not a Java question.
Is it necessary that the machine be restarted on changing keep alive time or is there a specific time by which the new keep alive time would be picked up during run time or on restarting the java application?Another Windows question.
But I would review your requirement. More likely you should be building application pings into the applications that actually need them.

GF3.0 - Enabling HTTP keep-alive?

In GF 2.0, there's a handy-dandy tab on the HTTP Listener configs for enabling and configuring HTTP keep-alives. In GF 3.0, there is not.
I've been combing various sites and blogs and docs and have been unable to find any information on enabling HTTP keep-alives. Some data I've found seems to suggest that raising the Max Connections and Timeout values for the listener to values greater than 1 implicitly enables keep-alives, but if I test the server with AB it shows zero keep-alive requests.
Any help that anyone could provide would be greatly appreciated.

[glassfish@appserver ~]$ asadmin get -m \*keep-alive.\*count
Enter admin user name> admin
Enter admin password for user "admin">
Command get executed successfully.
[glassfish@appserver ~]$ asadmin get "server\*keep-alive.\*"
Enter admin user name> admin
Enter admin password for user "admin">
com.sun.enterprise.admin.cli.CommandException: remote failure: Dotted name path server\*keep-alive.\* not found.
Command get failed.

Keep Alive Timeout

Similar Messages

Maybe you are looking for