With the new release, it appears changes were made in XSERVER to better
depend on DNS dependence. We have had a number of performance-related
issues with SAPDB that we have suspected related to DNS.
Here is from the latest release notes:
PTS: 1121278 since: 7.4.03.23
New Feature:
The x_server got two new command line options.
The option 'update' (or -U) will modify the start
bnehaviour. If already an x_server is running, the running
x_servers version is requested and compared with own
version. If the running x_server is 'newer' the update does
not take place. If it is older or equal (identical
major/minor release number and correction level) the
running x_server is informed about the update request. This
will work only with the newest x_server versions
(73.0.35,74.2.18,74.3.18,74.4.1).
NOTE: Older versions cannot react on the update request and
must be stopped manually as before.
If the update request was received, the running x_server
stops listening on its port but does not terminate already
existing connections. The protocol xserver.prt is not
interrupted, since the logging process is also not stopped.
The option '-F' allows a fast mode, where DNS lookup is
skipped.
The means that remote machines are no longer identified by
the kernel by name, but with the IP address (which is the
fallback anyhow). This option makes connection
establishment much faster in an environment, where DNS
lookup is expensive.
On Win32, would I just add the -F in the service start option of XServer?
Are there any negative impacts of running XServer in this mode?
Thanks.
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
