HOW TO

Interpret the ArcIMS Spatial Server LOG files

Last Published: April 25, 2020

Summary

The ArcIMS Spatial Server writes LOG files on Windows to <ArcIMS Installation Directory>\Server\log and to $AIMSHOME/log on UNIX. In a typical installation, a total of eight (version 3.x) or nine (version 4.x) LOG files are created each time the ArcIMS Monitor process is started. Each component of the ArcIMS Spatial Server--image, query, feature, geocode, extract, and metadata (4.x only)--has its own LOG file. In addition, two LOG files are created for third party applications and one LOG file describes the overall state of the Spatial Server. Optional extensions and multiple Spatial Servers add to the total number of LOG files.

Note:
The LOG file related to the metadata component is created only after a Metadata Service has been initialized for the site. Additional metadata LOG files are not created unless the initial file is deleted.


Note:
For ArcIMS 9.2 see ArcIMS Help topic 'About interpreting Spatial Server log files'

Procedure

The following is an example of the information written to the LOG files when the log mode is set to 'On'. The LOG file mode is 'Error' by default and must be altered in order to retrieve this information. To learn about the various modes available and how to select them, see the link in Related Information below.


Code:
Tue Jun 13 09:14:51 2000][462 489 INFO1] SERVICE: reg

Tue Jun 13 09:14:51 2000][462 489 INFO2] AXL Parse Time: 0.010000s

AXL Parse Time is the total time required to complete the three steps involved in parsing the map configuration file:

1) Build a tree from the .axl file.
2) Create objects the .axl file needs.
3) Interpret the .axl file objects. The objects are made available to the Spatial Server.


Code:
Tue Jun 13 09:14:51 2000][462 489 INFO2] RENDERER SETUP: 0.000000s

Tue Jun 13 09:14:51 2000][462 489 INFO2] FEATURE LAYER:

KERRMCGEE.VALID_PIPES

Tue Jun 13 09:14:52 2000][462 489 INFO2] DATA SEARCH TIME: 0.701000s

Data Search Time is the time required to prepare and send the query with its attribute and spatial constraints.


Code:
Tue Jun 13 09:15:09 2000][462 489 ERROR] SE_stream_fetch :
The specified coordinate exceeds the valid coordinate range.

Tue Jun 13 09:15:09 2000][462 489 INFO2] SR FEATURES PROCESSED: 8478

Tue Jun 13 09:15:09 2000][462 489 INFO2] DATA RETRIEVAL TIME: 17.385000s

Data Retrieval Time is the time used to fetch and draw the data.


Code:
Tue Jun 13 09:15:09 2000][462 489 INFO2] TOTAL PROCESSING TIME: 18.086000s

Total Processing Time is the total time required to prepare, send, fetch, and draw the data.


Code:
Tue Jun 13 09:15:09 2000][462 489 INFO2] OUTPUT TIME: 0.060000s

Output Time is the time spent in generating the image file.


Code:
Tue Jun 13 09:15:09 2000][462 489 INFO3] RESPONSE:
<?xml version="1.0"?>
<ARCXML version="1.0">
<RESPONSE>
<IMAGE>
<ENVELOPE minx="344816.831000000470000" miny="5743678.860000000300000"
maxx="741447.900999999610000"
maxy="5923965.710000000000000" />
<OUTPUT file="C:\ArcIMS\output\reg_GRIOT4624894.jpg"
url=http://griot/output/reg_GRIOT4624894.jpg />
</IMAGE>
</RESPONSE>
</ARCXML>

The Response gives information such as the name and location of the output image. For more details on the elements included in the ArcXML Response, see the ArcXML Programmer's Reference Guide, included with ArcIMS.

In addition to the information described above, the LOG files would also include any error messages generated by the Spatial Server.

Article ID:000003829

Software:
  • Legacy Products

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options

Related Information

Discover more on this topic