Advanced Features: Debugging Tools
Dernière mise à jour
Dernière mise à jour
K2 Geospatial 2022
This section presents debugging tools available in JMap Admin. These tools help identify JMap Server operating and performance problems.
The tools in this section of JMap Admin are at the experimental stage. Technical support is not offered for them.
This section is not displayed by default because it includes advanced tools that are not commonly used. To display the Debugging Tools section:
In the JMap Server / Log files / Configuration section, select the Logging level: Debug. The icon appears at the bottom of the menu sidebar.
Click on to open the Debugging Tools section, which is only in English.
Several tools are available. Some of the information provided by the tools may be requested during technical support.
View process threads
View the JMap server threads as well as their status.
Active sockets connexions
View the socket usage of the server where JMap Server is installed.
Environment variables / System properties
View the environment variables as well as the properties of the server where JMap Server is installed.
Ping an address
Allows to send a ping from the server where JMap Server is installed.
Resources management
Function used for the development of JMap, used to manage JMap source code translation files.
Worker threads jobs
View active worker threads and pending tasks of the JMap server. A thread is used while updating a data source, caching, calculating statistics, etc.
Layer configuration troubleshooting
This section provides information on the layers of a project, in order to identify the source of a operational JMap application problem. The Layer configuration troubleshooting section provides details of this tool.
JMap Cloud
This section details in tables the files, spatial data sources, projects and tasks that are shared with JMap Cloud. For each resource, data such as name, type, creation date, ID, are displayed.
This section allows JMap Server administrators to identify the source of an application performance problems caused by layer configuration.
You can display the Configuration section of a layer by clicking on its name.
For each layer the table displays the following data:
Name
Name of the layer. An icon indicates whether the layer is visible by default or not on the map. You can sort layers by name. The number in blue indicates the order in which this attribute is considered in the sorting of the layers.
Feature count
Number of map elements from the layer's spatial data source. An icon indicates the element type of the layer (point, line, polygon, text). You can sort the layers according to the number of elements it contains. The number in blue indicates the order in which this attribute is considered in the sorting of the layers.
Visibility thresholds
Visibility thresholds. This section provides the details of this setting.
Request mode
Layer request mode. Three modes are possible: Tile (manual): Load by tile, the administrator has determined the grid. Tile (automatic): Load by tile, JMap Server has calculated the optimal grid. Region: Loading by region. This section provides the details of this setting.
Exten
Layer extent. X and Y parameters indicate the coordinates of the lower left point, in project coordinates. W and H parameters specify the width and height of the layer's extent rectangle, in project mapping units.
Tiling (C x R)
For layers loading by tile, this attribute indicates the number of columns (C) and rows (R) of the grid.
Biggest tile
Indicates the size, in volume, of the largest tile in the layer. This measurement is based on the tiles cache.
Biggest tile (features)
Indicates the size, in number of elements, of the largest tile in the layer. This measurement is based on the tiles cache.
Avg. non empty tile size
Shows the average size (in volume) of tiles that are not empty. This measurement is based on the tiles cache.
Id
Layer Id.
The section displays a table of vector layers on a project. To populate the table, select the project and press to display the project layers. By default, layers in the table are sorted in descending order based on the number of map elements in the spatial data source.