Application Load Manager Log Files

The Application Load Manager generates a log file that lists requests and events that are processed by the Load Manager. This log can help you determine how Application Dispatcher requests are distributed among available servers or to find problems when starting new servers.

Example 1

Here is a sample log file for a socket service with line numbers added for reference:

Line 1 
      Wed Jun 03 2000 09:16:14 GET SERVER default aaa.bbb.com:5612 3
      
Line 2 
      Wed Jun 03 2000 09:16:14 Waiting for default
      
Line 3 
      Wed Jun 03 2000 09:16:18 SET STATE default aaa.bbb.com:5612 IDLE 2 0/1 0
      
Line 4 
      Wed Jun 03 2000 09:16:19 Returned default aaa.bbb.com:5612 3
      
Line 5 
      Wed Jun 03 2000 09:16:23 SET STATE default aaa.bbb.com:5612 BUSY 3 1/1 0
      
Line 6 
      Wed Jun 03 2000 09:16:26 SET STATE default aaa.bbb.com:5612 IDLE 3 0/1 0
      
Line 7 
      Wed Jun 03 2000 09:16:26 SET STATE default aaa.bbb.com:5612 SHUTDOWN

This log file shows the following events:

Line 1	The Application Broker requests an Application Server from the default service. This request is assigned the number 3.
Line 2	No server is available. Load Manager is waiting for an idle server.
Line 3	The server completes a previous request and notifies the Load Manager that the server is IDLE. The 0/1 indicates that the Application Server does not have any programs running but has 1 space available. The trailing 0 is the number of active server sessions.
Line 4	The Load Manager releases the available server to Broker request 3.
Line 5	The Broker has submitted its request to the server. The server notifies the Load Manager that the server is BUSY, with the 1 available space in use and 0 server sessions active.
Line 6	The server completes this request and becomes IDLE again.
Line 7	The Application Server is shut down.

Example 2

Here is another sample log file showing a pool service with line numbers added for reference:

Line 1
Mon Aug 07 2000 13:22:53  GET SERVER pool1 xxx.yyy.com:2 5

Line 2
Mon Aug 07 2000 13:22:53  Started pool1 on xxx.yyy.com  Pid: 17979

Line 3 
Mon Aug 07 2000 13:22:53  Command: /usr/local/bin/sas   /usr/local/intrnet/pool1/appstart.sas
 -rsasuser -noterminal -noprint -nolog -SYSPARM "loadmgr=xxx.yyy.com:5555 serviceid=pool1 port=000000"

Line 4
Mon Aug 07 2000 13:22:53  Waiting for: pool1 5

Line 5
Mon Aug 07 2000 13:22:56  SET STATE pool1 xxx.yyy.com:4525 STARTED

Line 6
Mon Aug 07 2000 13:22:56  Returning: pool1 xxx.yyy.com:4525 5

Line 7
Mon Aug 07 2000 13:22:57  SET STATE pool1 xxx.yyy.com:4525 WORKING 5 1/3 1

Line 8
Mon Aug 07 2000 13:22:58  SET STATE pool1 xxx.yyy.com:4525 IDLE 5 0/3 1

This log file shows the following events:

Line 1	The Application Broker requests an Application Server from the pool1 service. This request is assigned the number 5.
Line 2	No server is available so the Load Manager starts a new Application Server.
Line 3	This is the exact command that is used to start the server.
Line 4	The requesting Broker is placed in the wait queue waiting for the server to start.
Line 5	The server notifies the Load Manager that it has started.
Line 6	The Load Manager releases the available server to Broker request 5
Line 7	The Broker has submitted its request to the server. The server notifies the Load Manager that the server is in a WORKING state, with 1 of the 3 available spaces in use and 1 server session active. Note: The WORKING state will only appear if the Applications Server was started with the PROGRAMS parameter set to be greater than one.
Line 8	The server completes this request and becomes IDLE again.