Hi jrg,
I do see the point of ....If it failed 100 times for one host, it not
necessarily fails for another client.But the command line switch should do.I assume
since under windows xserver runs as a service so the switch will have to be passed
from the services control panel?!
Sounds good and fast:-)
Let me know if those changes ever get into 7.3? i.e. if i haven't moved to 7.4 by
then ;-)
regards,
Ajit
-----Original Message-----
From: Mensing, Joerg [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 3:27 PM
To: ajit_cus
Cc: [EMAIL PROTECTED]
Subject: RE: slow connection establishment jdbc
Hi Ajit,
the x_server lookup does the name lookup for the client host. If it failed 100 times
for one host, it not necessarily fails for another client... We would have to add a
address cache if we do not want to loose the identification in the x_server to make it
faster and thereby could add such an individual lookup suppression to mark individual
hosts as misconfigured. But this is not even planned yet, but could be isolated in a
'sort of' primitiv firewall class, which could also allow to reject certain unwanted
intruders...
But i just got an ok to implement at least a command line switch, that allows to
disable host name lookup code in the x_server completely to make it faster. This will
be possible in one of the next releases.
CU
jrg
> -----Original Message-----
> From: Schroeder, Alexander
> Sent: Donnerstag, 30. Januar 2003 09:00
> To: 'ajit_cus'; [EMAIL PROTECTED]
> Subject: RE: slow connection establishment jdbc
>
>
> Hi Ajit,
>
> > -----Original Message-----
> > From: ajit_cus [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, January 30, 2003 4:30 AM
> > To: Mensing, Joerg; [EMAIL PROTECTED]
> > Cc: Watz
> > Subject: RE: slow connection establishment jdbc
> >
> >
> > Hi,
> > Can confirm that there were errors in the xserver.prt
> > 2003-01-26 20:28:32 0x4AC ERR 18379 CONNECT Error
> > getting TCP/IP host by address: '10.48.2.62'
> > 2003-01-26 20:28:53 0x4AC ERR 18379 CONNECT Error
> > getting TCP/IP host by address: '10.48.2.62'
> > 2003-01-26 20:28:53 0x644 19739 XSERVER ''
> > connected to 'mmp', T:22
> > 2003-01-26 20:30:36 0x644 19740 XSERVER ''
> > disconnect from 'mmp', T:22
> > 2003-01-26 20:31:57 0x4AC ERR 18379 CONNECT Error
> > getting TCP/IP host by address: '10.48.2.62'
> > 2003-01-26 20:32:18 0x4AC ERR 18379 CONNECT Error
> > getting TCP/IP host by address: '10.48.2.62'
> > My log file has atleast a few 100 failed host name look
> > ups.However an acceptable solution --> if host name look up
> > fails N times stop using it (atleast for that ip
> > address).This could make the difference between a series of
> > continous failures and a single failure.
> >
> > Also looking at the jdbc trace i see that too has the
> > hostname of the db server i.e.
> > Socket[addr=OMBCLTEL/10.48.2.61,port=7210,localport=1498].
> > Does the jdbc driver resolve host name too ? My connect
> > string has only an ip address i.e.
> > 'jdbc:sapdb://10.48.2.61/mmp'
>
> The JDBC Driver ( here the java.net.Socket.toString() ) does
> it only in the trace => no trace, no lookup. The java.net.Socket
> class takes care on whether the supplied string is an
> IP address or a name to resolve, and needs no name resolve
> to connect.
>
> Regards
> Alexander Schr�der
> SAP Labs Berlin
> _______________________________________________
> 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
