Hi Ajit, i just confirmed Marco that there is a reverse hostname lookup call in the x_server code. If it fails, it uses the ip address. In the knldiag each remote connection is logged and therefore its nice to have the hostname instead of an IP address. If you look into 'xserver.prt' (found in independend working directory) you will find lines like
2003-01-29 09:34:08 7793 ERR 11379 CONNECT Error getting TCP/IP host by address: '10.31.165.88.' SAPDB kernel itself will not notice that x_server had problems, since it does not do any reverse hostname lookup. That is the reason you will not find this message in knldiag. CU jrg > -----Original Message----- > From: ajit_cus [mailto:[EMAIL PROTECTED]] > Sent: Mittwoch, 29. Januar 2003 04:43 > To: Watz; [EMAIL PROTECTED] > Subject: RE: slow connection establishment jdbc > > > Hi Marco, > Maybe its just my point of view,but i could live with just > an ip in the logs/display and would be a whole lot happier if > atleast SAPDB would warn me that dns lookup is failing/timing > out/taking a hell of a long time. > Anyway i dont see why it can't do a dns lookup just for the > logs and simultaneously connect to the database using the ip > address it already has.Of course as you say we dont really > know that sapdb is doing this so this is just theory.Anyone > from SAP can confirm? > Thanks for telling me about reverse dns lookup,i didnt know > such a thing existed. > thanks and regards, > Ajit > > -----Original Message----- > From: Watz [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 29, 2003 1:46 AM > To: ajit_cus; [EMAIL PROTECTED] > Subject: Re: slow connection establishment jdbc > > > Many servers do it for logging or display purposes. They like > to know their clients hostnames to display it in a logfile or > in a session listing displayed in administrative tools. They > attempt to reverse lookup the ip that connected to them to get it. > I don't know if SAPDB does this, but many server applications > do. And since DNS is UDP based timeouts may be involved if no > DNS Server is present. > > ----- Original Message ----- > From: "ajit_cus" <[EMAIL PROTECTED]> > To: "Watz" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Tuesday, January 28, 2003 4:24 AM > Subject: RE: slow connection establishment jdbc > > > > Hi Marco, > > I guess u r right.But why resolve a host name when you > have an IP addresss?i.e.reverse name lookup. > > I dont see any reason why i shouldn't be able to work with > only ip addresses and no host names.It sounds faster too.... > > regards, > > Ajit > > > > -----Original Message----- > > From: Watz [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, January 28, 2003 2:28 AM > > To: ajit_cus; [EMAIL PROTECTED] > > Subject: Re: slow connection establishment jdbc > > > > > > Hi, > > > > this might not only be a problem for your client resolving > the servers IP from a hostname....even if you just use the IP > instead of the hostname these DNS timeouts may also happen > because your server is unable to do a reverse name lookup (ip > to host) to get the hostname of the client. I don't know if > the SAPDB server does this, but its possible. > > > > Greetings, > > > > Marco > > > > > > ----- Original Message ----- > > From: "ajit_cus" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Monday, January 27, 2003 12:37 PM > > Subject: slow connection establishment jdbc > > > > > > > > > > Hi, > > > The problem occurs due to no DNS.An entry in > winNT\system32\drivers\etc\host fixes this. > > > Note that this happens despite the jdbc connection > string having an IP address instead of machine name. > > > I think this should be fixed.I should be able to use ip > addresses only and work without DNS. > > > regards, > > > Ajit > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, January 27, 2003 4:15 PM > > > To: [EMAIL PROTECTED] > > > Subject: sapdb.general digest, Vol 1 #788 - 1 msg > > > > > > Today's Topics: > > > > > > 1. RE: slow connection establishment jdbc (Schroeder, > Alexander) > > > > > > --__--__-- > > > > > > Message: 1 > > > From: "Schroeder, Alexander" <[EMAIL PROTECTED]> > > > To: "'ajit_cus'" <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > > > Subject: RE: slow connection establishment jdbc > > > Date: Mon, 27 Jan 2003 11:51:02 +0100 > > > > > > Hi Ajit, > > > > > > it must have something to do with the network, and there is no > > > known problem in that area for JDBC (as the other 'slow > connection' > > > problems do massively affect the query execution time too). > > > > > > So I can only suggest e.g. making a small Java Server & > Client application > > > and check the speed and reliability of the network > connections between > > > the affected computers, or use other network > monitoring/checking/testing > > > tools if available and appropriate. > > > > > > Regards > > > Alexander Schr�der > > > SAP Labs Berlin > > > > > > > > > > -----Original Message----- > > > > From: ajit_cus [mailto:[EMAIL PROTECTED]] > > > > Sent: Monday, January 27, 2003 8:51 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: slow connection establishment jdbc > > > > > > > > > > > > > > > > Hi, > > > > I'm running sapdb 7.3.0.30 when connecting to from a machine > > > > on the same lan it takes over 12 secs to get a connection > > > > however queries execute under 20 ms.What could the problem be. > > > > It runs fine in another test environment. JDBC ver is > > > > 7.4.04.00b .Part of jdbc trace follows .. > > > > regards, > > > > Ajit > > > > PS:listserv search is down!!!! > > > > > > > > ---- Thread 5a8767 main Timestamp: 2003-01-27 12:20:53.765 > > > > ================================== > > > > package com.sap.dbtech.jdbc, SAP DB JDBC Driver, SAP AG, > > > > 7.4.4 Build 000-000-156-685 on Java 1.3.1_02 > > > > new Connection 'jdbc:sapdb://10.48.2.61/mmp' > > > > > > > > ---- Thread 6e70c7 Finalizer Timestamp: 2003-01-27 12:21:36.796 > > > > new RTEException: -708 Could not send data. > > > > whereAmI > > > > java.lang.Throwable > > > > at com.sap.dbtech.util.Tracer.whereAmI(Tracer.java:426) > > > > at > > > > > com.sap.dbtech.rte.comm.RTEException.<init>(RTEException.java:69) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.sendData(SocketComm.java:732) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.release(SocketComm.java:620) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.finalize(SocketComm.java:344) > > > > at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) > > > > at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:86) > > > > at java.lang.ref.Finalizer.access$100(Finalizer.java:17) > > > > at > > > > java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:163) > > > > > > > > ---- Thread 5a8767 main Timestamp: 2003-01-27 12:21:36.906 > > > > using com.sap.dbtech.rte.comm.SocketComm@2a1e44 on > > > > Socket[addr=OMBCLTEL/10.48.2.61,port=7210,localport=1492] > > > > => com.sap.dbtech.jdbc.ConnectionSapDB@50a5d9 > > > > > [EMAIL PROTECTED] (2) > > > > ================================== > > > > package com.sap.dbtech.jdbc, SAP DB JDBC Driver, SAP AG, > > > > 7.4.4 Build 000-000-156-685 on Java 1.3.1_02 > > > > new Connection 'jdbc:sapdb://10.48.2.61/mmp' > > > > > > > > ---- Thread 6e70c7 Finalizer Timestamp: 2003-01-27 12:22:19.968 > > > > new RTEException: -708 Could not send data. > > > > whereAmI > > > > java.lang.Throwable > > > > at com.sap.dbtech.util.Tracer.whereAmI(Tracer.java:426) > > > > at > > > > > com.sap.dbtech.rte.comm.RTEException.<init>(RTEException.java:69) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.sendData(SocketComm.java:732) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.release(SocketComm.java:620) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.finalize(SocketComm.java:344) > > > > at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) > > > > at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:86) > > > > at java.lang.ref.Finalizer.access$100(Finalizer.java:17) > > > > at > > > > java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:163) > > > > > > > > ---- Thread 5a8767 main Timestamp: 2003-01-27 12:22:19.968 > > > > using com.sap.dbtech.rte.comm.SocketComm@52906a on > > > > Socket[addr=OMBCLTEL/10.48.2.61,port=7210,localport=1494] > > > > => com.sap.dbtech.jdbc.ConnectionSapDB@72ffb > > > > > [EMAIL PROTECTED] (2) > > > > ================================== > > > > package com.sap.dbtech.jdbc, SAP DB JDBC Driver, SAP AG, > > > > 7.4.4 Build 000-000-156-685 on Java 1.3.1_02 > > > > new Connection 'jdbc:sapdb://10.48.2.61/mmp' > > > > using com.sap.dbtech.rte.comm.SocketComm@16a786 on > > > > Socket[addr=OMBCLTEL/10.48.2.61,port=7210,localport=1496] > > > > => com.sap.dbtech.jdbc.ConnectionSapDB@507fb2 > > > > > [EMAIL PROTECTED] (2) > > > > ================================== > > > > package com.sap.dbtech.jdbc, SAP DB JDBC Driver, SAP AG, > > > > 7.4.4 Build 000-000-156-685 on Java 1.3.1_02 > > > > new Connection 'jdbc:sapdb://10.48.2.61/mmp' > > > > using com.sap.dbtech.rte.comm.SocketComm@26e85f on > > > > Socket[addr=OMBCLTEL/10.48.2.61,port=7210,localport=1498] > > > > => com.sap.dbtech.jdbc.ConnectionSapDB@61f10f > > > > > [EMAIL PROTECTED] (2) > > > > ================================== > > > > package com.sap.dbtech.jdbc, SAP DB JDBC Driver, SAP AG, > > > > 7.4.4 Build 000-000-156-685 on Java 1.3.1_02 > > > > new Connection 'jdbc:sapdb://10.48.2.61/mmp' > > > > using com.sap.dbtech.rte.comm.SocketComm@916a2 on > > > > Socket[addr=OMBCLTEL/10.48.2.61,port=7210,localport=1500] > > > > => com.sap.dbtech.jdbc.ConnectionSapDB@2ce908 > > > > > [EMAIL PROTECTED] (2) > > > > ================================== > > > > package com.sap.dbtech.jdbc, SAP DB JDBC Driver, SAP AG, > > > > 7.4.4 Build 000-000-156-685 on Java 1.3.1_02 > > > > new Connection 'jdbc:sapdb://10.48.2.61/mmp' > > > > > > > > ---- Thread 6e70c7 Finalizer Timestamp: 2003-01-27 12:25:11.953 > > > > new RTEException: -708 Could not send data. > > > > whereAmI > > > > java.lang.Throwable > > > > at com.sap.dbtech.util.Tracer.whereAmI(Tracer.java:426) > > > > at > > > > > com.sap.dbtech.rte.comm.RTEException.<init>(RTEException.java:69) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.sendData(SocketComm.java:732) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.release(SocketComm.java:620) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.finalize(SocketComm.java:344) > > > > at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) > > > > at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:86) > > > > at java.lang.ref.Finalizer.access$100(Finalizer.java:17) > > > > at > > > > java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:163) > > > > new RTEException: -708 Could not send data. > > > > whereAmI > > > > java.lang.Throwable > > > > at com.sap.dbtech.util.Tracer.whereAmI(Tracer.java:426) > > > > at > > > > > com.sap.dbtech.rte.comm.RTEException.<init>(RTEException.java:69) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.sendData(SocketComm.java:732) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.release(SocketComm.java:620) > > > > at > > > > com.sap.dbtech.rte.comm.SocketComm.finalize(SocketComm.java:344) > > > > at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) > > > > at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:86) > > > > at java.lang.ref.Finalizer.access$100(Finalizer.java:17) > > > > at > > > > java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:163) > > > > new RTEException: -708 Could not send data. > > > > <More -708 exceptions after this> > > > > > > > > _______________________________________________ > > > > sapdb.general mailing list > > > > [EMAIL PROTECTED] > > > > http://listserv.sap.com/mailman/listinfo/sapdb.general > > > > > > > > > > > > > --__--__-- > > > > > > _______________________________________________ > > > sapdb.general mailing list > > > [EMAIL PROTECTED] > > > http://listserv.sap.com/mailman/listinfo/sapdb.general > > > > > > > > > End of sapdb.general Digest > > > _______________________________________________ > > > sapdb.general mailing list > > > [EMAIL PROTECTED] > > > http://listserv.sap.com/mailman/listinfo/sapdb.general > > > > > > > > _______________________________________________ > > sapdb.general mailing list > > [EMAIL PROTECTED] > > http://listserv.sap.com/mailman/listinfo/sapdb.general > > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
