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

Similar Messages

Weblogic proxy plugin closes keep-alive connections to clients randomly

In short we have following arhitecture:
clients ---> wl proxy plugin 1 ----> weblogic 1
clients ---> wl proxy plugin 2 ----> weblogic 2
Beacuse of the application/installation specific requirements, we are not using failover, one wl proxy always forwards requests to one weblogic (simple configuration).
Application is TR-069 protocol based (SOAP over HTTP) so it very much relays on persistence TCP connections (Connection: keep-alive). This TCP persistence has to work correctly in order that TR-069 messages are exchanged in required order, otherwise we have a error on application layer.
Here and there we've noticed applications errors which suggest that we have some problems in TCP connection between the client and the weblogic server. After sniffing, we've noticed that weblogic proxy plugin (Apache) randomly, or because of some other reason we do not know, decides to close TCP connection to client, even app on weblogic did not request so ???
As a result, client opens new connection to the server with new TR-069 session and it gets bounced beacuse it allready has one open on weblogic server.
We've sniffed, traced everything we could, we were searching for patterns in time, etc... but we can not find the reason why proxy plugin decides to close the connection to the client (not to the weblogic server).
Trace (replaced sensitive information):
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: StatusLine set to [200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> parsed all headers OK
Thu Apr 29 15:05:50 2010 <958012725463463784> sendResponse() : r->status = '200'
Thu Apr 29 15:05:50 2010 <958012725463463784> canRecycle: conn=1 status=200 isKA=1 clen=545 isCTE=0
Thu Apr 29 15:05:50 2010 <958012725463463784> closeConn: pooling for '$IP$/$PORT$'
Thu Apr 29 15:05:50 2010 <958012725463463784> request [$URL$] processed successfully..................
!!!! Now it closes the TCP connection and inserts "Connection: close" HTTP header !!!
WL proxy plugin conf params are:
WebLogicCluster $IP$:$PORT$
DynamicServerList OFF
KeepAliveTimeout 90
MaxKeepAliveRequests 0
KeepAliveSecs 55
Apache worker configuration is:
<IfModule mpm_worker_module>
PidFile var/run/httpd-worker.pid
LockFile var/run/accept-worker.lock
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 200
ThreadsPerChild 200
MaxClients 2000
MaxRequestsPerChild 0
AcceptMutex pthread
</IfModule>
Why weblogic proxy plugin ignores Keep-alive directive and decides to close connection to the client by itself?
Any help?

If a WebLogic Server instance listed in either the WebLogicCluster parameter or a dynamic cluster list returned from WebLogic Server fails, the failed server is marked as "bad" and the plug-in attempts to connect to the next server in the list.
MaxSkipTime sets the amount of time after which the plug-in will retry the server marked as "bad." The plug-in attempts to connect to a new server in the list each time a unique request is received (that is, a request without a cookie).
Note: The MaxSkips parameter has been deprecated as the MaxSkipTime parameter.
See also here: http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/plugins/plugin_params.html
You said the problem arises under significant load. Maybe, it is wise to tune the number file descriptor's on your operating system. HTTP connections are nothing more than TCP sockets on the operating system. All modern operating systems treat sockets as a specialized form of file access and use data structures called file descriptors to track open sockets and files for an operating system process. To control resource usage for processes on the machine, the operating system restricts the number of open file descriptors per process. You should be aware that all TCP connections that have been gracefully closed by an application will go into what is known as the TIME_WAIT state before being discarded by the operating system.
On most unix systems you can use netstat -a | grep TIME_WAIT | wc -l to detemine the number of socket in time_wait state. You have to check with your system adminstrator how to tune the tcp_time_wait_interval. On solaris you can use: /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000

Keep-alive connection between app and servlet

Hi,
I have searched the forum for information about how to keep a
connection alive between a client app and a servlet, but I have not been
able to find anything.
Does someone have an example of how to do this? Please send it!
Thanks!

HTTP connections are transient, they're not meant to be kept open.
HTTP 1.1 can support this feature, check the RFC and servlet specification (and probably the appserver documentation for configuration).
Best use another protocol though, ftp for example (or something else entirely).

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

Can not keep a connection using Wi-Fi or 4G mobile.

No matter what I use either Wi-Fi or Mobile connection I get booted every few minutes. More like having a 2 G network instead of 4. Any suggestions?

Hey there, Jewelster! I regret that your Ellipsis is having such difficulty keeping a wireless connection. You've described it as being 'booted'. Can you share some additional details? I'd like to help! When this 'booting' occurs, are you just losing connection or do you see an error message as well? If there's a message, what does it say? Does the device reconnect on its own or do you have to do something to force it? If it reconnects on its own, how long does it take to re-establish connection? Are you streaming video and / or audio at the time this occurs?
DionM_VZW
Follow us on Twitter www.twitter.com/vzwsupport

IllegalStateException Keep Alive Connection not initialized

Dear all,
I would like to solicit for some helpful hints. I have a small midlet running under the WTK22 emulator just fine on my dev machine.
However, on another machine, I get the following exception:
Exception in thread "main" java.lang.IllegalStateException: KeepAliveConnection not initialized
at com.sun.kvem.environment.KeepAliveConnection.run(Unknown Source)
at com..sun.kvem.environment.EmulatorWrapper.main(Unknown Source)
While there are few reports of this nature, I can't seem to find any answers on the net.
I'm using Windows XP, with WTK22 on both environments. On both environments, all the demos seem to run fine.
Any helpful comments would be welcome.
Thanks.
KHK

I get the same issue with WTK2.2 under FC5 64bit Linux. Any ideals about what is causing this??
Thanks

Keep-alive message bridge connection

Hi,
I have setup messaging bridge between WLS 10.3.0.0 and a JBoss Messaging queque, after about 4 hours of inactivity in a queue bridge was disconneted, is there any way to configure keep-alive connection in WLS bridge ?
Thanks,
Lukasz

You can try to set the IdleTimeMaximum setting on your bridge configuration to a very large number. It specifies the maximum amount of time, in seconds, that a messaging bridge instance remains idle.
In “asynchronous” mode, this is the longest amount of time a messaging bridge instance stays idle before it checks the sanity of its connection to the source. In “synchronous” mode, this is the amount of time the messaging bridge can block on a receive call if no transaction is involved.
-Dongbo

URLConnection POST to external server requiring keep-alive fails because request is HTTP/1.0

          I have a class that when run as a "main" transmits a HTTP/1.1 post successfully
          to an external server. This external server requires keep-alive connections.
          However when instantiated inside a weblogic servlet container, the post fails
          because the HTTP protocol is set to HTTP/1.0. I have tried this with V5.1 SP11
          and then with V6.1 SP2 with the same result. The code works under Tomcat.
          I can find no way to force HTTP/1.1 in the URLConnection. Any suggestions?


Great. I have a question to BEA folks, if they ever read this newsgroup:
          what is the reason for installing WLS protocol handlers, and, if there is
          one, why the implementation is still buggy? I saw many, many instances when
          code making outgoing connections failed to work in WLS, and the solution is
          always the same - use handler which comes with the JVM.
          Bob Bowman <[email protected]> wrote:
          > <[email protected]> wrote:
          >>If it works as a standalone application and fails inside WebLogic, most
          >>likely this
          >>is caused by WebLogic http handler implementation. You can try to modify
          >>your code
          >>like this:
          >>
          >>URL url = new URL(null, "http://some_url", new sun.net.www.protocol.http.Handler());
          >>HttpURLConnection conn = (HttpURLConnection)url.openConnection();
          >>
          >>(you will need to modify weblogic.policy to allow your code to specify
          >>protocol
          >>handler).
          >>
          >>Bob Bowman <[email protected]> wrote:
          >>
          >>> I have a class that when run as a "main" transmits a HTTP/1.1 post
          >>successfully
          >>> to an external server. This external server requires keep-alive connections.
          >>> However when instantiated inside a weblogic servlet container, the
          >>post fails
          >>> because the HTTP protocol is set to HTTP/1.0. I have tried this with
          >>V5.1 SP11
          >>> and then with V6.1 SP2 with the same result. The code works under
          >>Tomcat.
          >>
          >>> I can find no way to force HTTP/1.1 in the URLConnection. Any suggestions?
          >>
          >>--
          >>Dimitri
          > Worked like a champ! Thanks.
          Dimitri

GRE VPN & KEEP ALIVE

Dear all,
i am having problem with make keep alive connectivity all the time between 2 nodes.
I have A and B cisco routers established GRE VPN over ISP. Problem starts with when there are no active connection from host of A to host of B. It looks like VPN down. Another problem is when A 's having temp power outage and when power comes there is no active connection even WAN protocol is down.When reload A router manually then connection comes up.
I am thinking that maybe some configuation like keep alive retry something like that.
Do guys have any idea on this matter ?

GRE tunnels are usually used in combination with a dynamic routing protocol that keeps the tunnel up and active. If you are using static routes there is no traffic to keep the tunnels up when the applications are not transmitting.
You have two options:
1. Increase the isakmp/ipsec lifetimes.
http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_configuration_guide_chapter09186a00800d981f.html#1001095
2. Setup keepalives (Best Option)
crypto isakmp keepalive (Number of seconds between keep alives) (Number of seconds between retries if keepalive fails)

HttpConnection keep-alive

Hello!
Guys i need your help to create a connection to web server with DataOutputStream and DataInputStream.
The problem is that I need to create connection that can be open all the time and I can write and read data from server.
I had make some variant but it's working only first time, after it say's connection already open.
here are code, little bit different, now it says Write attempted after request finished
here is source code
package super_7_blackjack;
import java.io.DataInputStream;
import java.io.DataOutputStream;
import java.io.IOException;
import java.io.InputStream;
import javax.microedition.io.Connector;
import javax.microedition.io.HttpConnection;
public class HTTPQuery {
        private HttpConnection connection;
        private DataOutputStream dos;
        private DataInputStream dis;
        private String URL;
        private String sessionId;
        public HTTPQuery(String URL, String sessionId) {
            System.out.println("URL=" + URL);
            this.URL = URL;
            this.sessionId = sessionId;
            try {
                connection = (HttpConnection)Connector.open(URL);
                connection.setRequestProperty("Content-type", "application/x-www-form-urlencoded");
                connection.setRequestProperty("cookie","JSESSIONID=" + sessionId + "; AnyJavaPresent=1.4.2_05");
                connection.setRequestProperty("Cache-Control","no-cache");
                connection.setRequestProperty("Pragma","no-cache");
                connection.setRequestProperty("User-Agent","Mozilla/4.0 (Windows XP 5.1) Java/1.4.2_05");
                connection.setRequestProperty("Accept","text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2");
                connection.setRequestProperty("Connection","keep-alive");
                connection.setRequestMethod("POST");
                if( connection.getResponseCode() == HttpConnection.HTTP_OK ) {
                    dos = new DataOutputStream(connection.openOutputStream());
                    dis = new DataInputStream(connection.openInputStream());
            } catch (IOException ieox) {
             System.out.println("Error while opening connection.");
     public synchronized String executeRequestQuery(String query) {
          StringBuffer b = new StringBuffer();
          long len = 0;
          try {
               dos.write(query.getBytes());
               dos.flush();
               DataInputStream dis = new DataInputStream(connection.openInputStream());
               len = connection.getLength();
               if (len!=-1) {
                            byte servletData[] = new byte[(int)len];
                            dis.readFully(servletData);
                            b.append(new String(servletData));
                         } catch (Exception e) {
                    System.out.println("Error while closing: " + e.getMessage());
          System.out.println(b.toString());
          return b.toString();
}and I use it
httpQuery = new HTTPQuery(URL,sessionId);
httpQuery.executeRequestQuery("CREATESESSION=NO&CMD=ENTER&DBLINK=DBLINKFREE1");

jhd
package super_7_blackjack;
import java.io.DataInputStream;
import java.io.DataOutputStream;
import java.io.IOException;
import java.io.InputStream;
import javax.microedition.io.Connector;
import javax.microedition.io.HttpConnection;
public class HTTPQuery {
        private HttpConnection connection;
        private DataOutputStream dos;
        private DataInputStream dis;
        private String URL;
        private String sessionId;
        public HTTPQuery(String URL, String sessionId) {
            System.out.println("URL=" + URL);
            this.URL = URL;
            this.sessionId = sessionId;
            try {
                connection = (HttpConnection)Connector.open(URL);
                connection.setRequestProperty("Content-type", "application/x-www-form-urlencoded");
                connection.setRequestProperty("cookie","JSESSIONID=" + sessionId + "; AnyJavaPresent=1.4.2_05");
                connection.setRequestProperty("Cache-Control","no-cache");
                connection.setRequestProperty("Pragma","no-cache");
                connection.setRequestProperty("User-Agent","Mozilla/4.0 (Windows XP 5.1) Java/1.4.2_05");
                connection.setRequestProperty("Accept","text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2");
                connection.setRequestProperty("Connection","keep-alive");
                connection.setRequestMethod("POST");
                if( connection.getResponseCode() == HttpConnection.HTTP_OK ) {
                    dos = new DataOutputStream(connection.openOutputStream());
                    dis = new DataInputStream(connection.openInputStream());
            } catch (IOException ieox) {
             System.out.println("Error while opening connection.");
     public synchronized String executeRequestQuery(String query) {
          StringBuffer b = new StringBuffer();
          long len = 0;
          try {
                                                           dos = new DataOutputStream(connection.openOutputStream());
               dos.write(query.getBytes());
               dos.flush();
               DataInputStream dis = new DataInputStream(connection.openInputStream());
               len = connection.getLength();
               if (len!=-1) {
                            byte servletData[] = new byte[(int)len];
                            dis.readFully(servletData);
                            b.append(new String(servletData));
                         } catch (Exception e) {
                    System.out.println("Error while closing: " + e.getMessage());
          System.out.println(b.toString());
          return b.toString();
dos.close();
dis.close();
}see in block latter what you need to change is>>>>
this will not going to close your HttpConnection but it will close only ur Stream connection and that will not required never at all.
try with this code i hope this will helps you.
Regards,
Jasmit vala
[email protected]

Speed limit on pipelining keep-alive requests?

Hi all,
          I was wondering if anyone knows of a limit in how fast weblogic can
          handle multiple servlet requests over a keep-alive connection.
          We were trying to throw a bunch for testing purposes, and it seems that
          if we bunch them closer together than ~300ms, it won't handle more than
          two. (I can recreate the problem by hand, too)
          Is this a limit in Weblogic 6?
          Thanks,
          Dave
          ps: here's the exception trace:
          <Mar 5, 2001 4:15:53 PM EST> <Error> <Posix Performance Pack> <Uncaught
          Throwable in processSockets
          java.lang.NullPointerException
          at weblogic.socket.TunnelContext.getServlet(TunnelContext.java:24)
          at weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTT
          P.java:459)
          at
          weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.jav
          a:449)
          at
          weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java
          :378)
          at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
          23)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >


Hi all,
          I was wondering if anyone knows of a limit in how fast weblogic can
          handle multiple servlet requests over a keep-alive connection.
          We were trying to throw a bunch for testing purposes, and it seems that
          if we bunch them closer together than ~300ms, it won't handle more than
          two. (I can recreate the problem by hand, too)
          Is this a limit in Weblogic 6?
          Thanks,
          Dave
          ps: here's the exception trace:
          <Mar 5, 2001 4:15:53 PM EST> <Error> <Posix Performance Pack> <Uncaught
          Throwable in processSockets
          java.lang.NullPointerException
          at weblogic.socket.TunnelContext.getServlet(TunnelContext.java:24)
          at weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTT
          P.java:459)
          at
          weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.jav
          a:449)
          at
          weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java
          :378)
          at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
          23)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >

How to keep the connection alive?

Hello! Happy new year!
I have to write an HTTP server that comunicates with many clients in the same time,but keeps the connection with a client open if there the corresponding header is Keep-Alive. I have used threads,and I've tested my program in the following way: I've requested the one page of the site and then I've followed a link from that page. I expected that the broowser and the server talk to the same thread every time,but it seems that they don't. The code I've written is:
//HTTPServer class
ServerSocket serverSocket = null;
        boolean listening = true;
        try {
            serverSocket = new ServerSocket(80);
        } catch (IOException e) {
            System.err.println("Could not listen on port: 80.");
            System.exit(-1);
        while (listening)
              new HTTPMultiServerThread(serverSocket.accept()).start();
//HTTPMultiServerThread
public void run() {
     //     System.out.println(socket.toString());
          try {
while(!serverSocket.isClosed())){
              DataOutputStream out = new DataOutputStream(socket.getOutputStream());
              DataInputStream in = new DataInputStream( socket.getInputStream());
              int nrBytes = in.available();
              if(nrBytes > 0){
                   byte[] bytes = new byte[nrBytes];
                   in.read(bytes);
                   System.out.println("Procesez mesajul:" + nrBytes + new String(bytes));
                   HTTPMessage processedMess = new HTTPMessage(bytes).processMessage();
                   System.out.println("Inchid conexiunea.");
                    log("log.txt", new HTTPMessage(bytes).getStatusLine() + " " + new Data().getCurrentTime());
               //send the message
out.write(processedMess.getBytes(),0,processedMess.getBytes().length);
                   /* inchid conexiunea
              else{
                   String ret = new String("HTTP/1.1 500 Internal Server Error\n");
                    ret += "Host: cristi\n";
                  ret += "Date: " + new Data().getCurrentTime()+"\r\n";
                  ret += "\r\n";
                  ret += "<html><body><p>HTTP/1.1 500 Internal Serve Error</p> </body><html>\r\n";
                  out.write(ret.getBytes());
              out.close();
              in.close();
                   if(new HTTPMessage(bytes).getHeaderValue("Connection").equals("Close"))
              socket.close();
     }//end while
          } catch (IOException e) {
              e.printStackTrace();
    }I would also like to know how many clients are waiting to be served,in order to develop statistics about the server response time. 10X

hi
same to u .
i think what i get from ur code that ....
use some vector at the server side and whenever any client is connected (offcourse first time or not (depend on u !!)) create an object corresponding(generally created by server for every client) ..
save this in the vector .. and pass it the size of vector to the client with the response .
may this help u .
regards
akash
Indiagames Ltd
[email protected]
India

Which port to use for the peer-keep alive

Hi All,
We have 2 Nexus 6001s in our data center.
The management port of each 6001 is connected to the other and this link is used as the peer keep alive link.
My colleague is suggesting that we use one of the inline data ports as the keep alive link.
Can you please advise on the pros and cons of using management/inline port as keep live link and the best practise to follow in this case?
Thanks,
Pete

Hi Pete,
Here are the best recommendation in order of preference.
1. Use mgmt0 (along with management traffic)
* Pros: whats good on this option is you are totally separating the VPC Peer keepalive link on another VRF (management) and does not mingle with the data or global vrf..
* Cons: VPC PKL is dependent on the OOB management switch.
2. Use dedicated 1G/10GE front panel ports.
* Pros - can just be a direct link between the N6K pair and not dependent on other boxes.
* Cons - you need extra SFPs for VPC PKL while the VPC PKL traffic join the global VRF.
HTH
Jay Ocampo

ADK - Keeping EIS Connections Alive

Hi,
          I am using the ADK that comes with WL 8.1 SP3. The challenge I am facing is to keep my connections alive while there is no activity (at the TCP/IP socket level) between the app server and the EIS.
          The EIS closes any sockets after 30 minutes of inactivity causing the connections to go into CLOSE_WAIT state.
          Is there any method I can use within the connector to keep pinging the server and make sure these connections have TCP/IP traffic?
          Has anyone used the <test-frequency-seconds> weblogic-ra.xml? What is its purpose? pinging?
          Appreciate your insight..

Hi
          I have a requirement, which is some what similar to what is mentioned above.
          I too have to ping the interface at regular intervals to keep the connection alive. I also assumed that, we can use the test-frequency-seconds attribute. But for that to work, we have to implement the interface, http://java.sun.com/j2ee/1.4/docs/api/javax/resource/spi/ValidatingManagedConnectionFactory.html, which is there only from weblogic 9.
          But since our client is using weblogic 8.1, we are tied to that version.
          Can anyone please assist in solving this.

How do I change the http connection type from close to keep-alive

I am using a browser that appears as though it needs a connection type of keep-alive. When a page is requested the server sends back a connection type of close. It appears images are not requested from the server when this connection type is requested.

Some older web server provides inaccurate content-length information.If the content length value is less than the amount of data,the web server treats the difference as a new request, this creates problem with iplanet Web Server.
If you are using browser with HTTP1.1 enabled, choose the option to enable it manually and try once again by posting the request.
Hope it helps.

LDAP keep-alive connection ? (use of ldap_io_fns)

Similar Messages

Maybe you are looking for