Loading...
 

Problems: ObjectStore - Network

ObjectStore® in the network

When searching for the causes of performance problems, the interaction between database (ObjectStore) and network should also be considered.

Reverse Naming Lookup

When starting the ClassiX® system (as ObjectStore client) the IP address of the client must be resolved again as client name.
If the start-up phase is unusually long, this could be a problem.

With

ping -a <the IP address of the client>

on the server machine you should check how long the reverse lookup takes.

Acceleration is achieved by entering your name + IP address in the file

WININT\SYSTEM32\DRIVERS\ETC\hosts

of the server.


Gathering information

Information about the network activities of the database ObjectStore can be obtained with

set OS_DEBUG_NETWORK=1

set OS_STDOUT_FILE=fileName

in the file above.

Order of network cards

Microsoft Windows© supports several network cards that allow a PC to be connected to the network. If a network request is made by the software to Windows©, Windows© tries to pass the network request to one network card after the other via its internal priority. After each transfer, Windows© waits for an answer. If there is no answer, for example because no network cable is connected to the corresponding network card, Windows© waits until the defined network timeout and then tries the next one.

To change the priorities of the network cards, the following options are available:

In the window that opens, you can now determine the order of the network cards using the up or down arrow. The standard network card should always be at the top of the list.

It can also help to permanently remove the network cards that were simply removed from the system without removing the entries in the Device Manager. To do this, all devices that are hidden because they are not currently in the system must first be displayed in the Device Manager. They are marked with a red cross and can then be removed via the context menu: