This setting logs load balancing operations that occur in a Dexterity application. It can be added to the defaults file for process servers, the Distributed Process Manager (DPM) as well as any client machine.
|
This setting is designed to be used for troubleshooting and debugging of a load balancing system. It should NOT be included in the final implementation. |
DebugQueue = option
• option - A constant that indicates whether to activate the load balancing log, and if so, what type of log to create:
|
Value |
Description |
|---|---|
|
TRUE |
Specifies that a new log file will be created each time the client, process server, or DPM is started. Any previous log file will be replaced. |
|
APPEND |
Specifies that new load balancing activity information will be added to the end of an existing log file. If a log file doesn’t already exist, a new one will be created. |
|
FALSE |
Inactivates logging of load balancing activities. False is the default value. |
The following table lists the name and contents of the log file that will be created for each load balancing component:
|
Log file name |
Description |
|---|---|
|
QLOGSRVR.TXT |
The file that logs the load balancing operations performed by a process server. This file is created in the same location as the process server application. |
|
QLOGDEMN.TXT |
The file that logs the operations performed by the DPM. This file is created in the same location as the DPM. |
|
QLOGCLNT.TXT |
The file that logs the load balancing operations performed by a client. This file is created in the same location as the runtime engine. |
Use a text editor to view the log files. Each contains information about the events and errors affecting the component generating the file. The following table lists error numbers and their corresponding descriptions:
|
Error |
Description |
|---|---|
|
0 |
No error |
|
1 |
Out of memory |
|
2 |
Network protocol not loaded |
|
3 |
Could not locate machine on the network |
|
4 |
Buffer overflowed while receiving data |
|
5 |
Invalid socket identifier |
|
6 |
Connection was dropped |
|
7 |
No other machine connected |
|
8 |
No data received |
|
9 |
Stream not initialized |
|
10 |
Incorrect version of network protocol loaded |
|
11 |
Too many connections |
|
12 |
Process server not running on machine |
|
13 |
Stream function is not available |
|
14 |
Unknown error |