Logfile creation
A new logfile is created every time the GPRSCore Application is restarted. The name of the most actual file is kmgprs.log.0, and the older logs are named with increasing suffix numbers (kmgprs.log.1, kmgprs.log.2, kmgprs.log.3).
Logfile content
Each Logfile starts with a header giving some system details:
- Starting time of the log
- GPRSCore Version
- Information when the Log will be deleted
- Number of processors available to the Java VM
- Total memory available to the Java VM (thats the memory already claimed by the Java VM)
- Maximum memory available to the Java VM
- Free memory in the Java VM (thats the free heap space)
After this generic header there are some lines of GPRSCore specific information:
- The working dir, to store temporary files
- The root dir, thats where GPRSCore and KMCore should reside next to each other
- The content of the configuration file, if one was found
- The result of the parsed KMCSBase.ini file, most prominent are CommServerID and CenterID
Now individual log file entries are following:
- found n new input files, this means KMCore has created n files with requests or information for GprsCore
- Processing: ReqGPRSJob20100325123712347_A0C2300032093.xml, this is a data request. Note that the name contains a internal SessionID and the machineID of the device to request
- delegated manually released Data-Request for COM23.A0C2300032093/7971559, this means the data request was delegated to the cascade server (the server to which the gprs modems are connected). The term 'manually released' is historic. Furthermore the CommServerID, MachineID and an internal requestID are given
- fetched manually released Data-Request for A0C2300032093/7971559, len=7361 Bytes, this means an answer to the above mentioned rAequest has arrived, The CommServerID, MachineID, equestID and the length of the response (in raw format) are given
- CleanUP GPRS-IO/export, deleting 0 alarms or setups, this means a regular cleanup has happened (can be configured in the configuration file), in this case nothing was deleted
- CleanUP GPRS-IO/response, deleting 0 responses, this means a regular cleanup has happened (can be configured in the configuration file), in this case nothing was deleted
- deleted MFP: M2M01[COM23].A0C2300030001. a MFP was deregistered by CSRC
- added new MFP: M2M01[COM23].A300303330004, a MFP was registered by CSRC
- ConnChecker: attempt to check 4 cascade servers, attempt to check for connectivity to the 4 cascade cluster members
- ConnChecker[ssl://195.234.183.226:9610] OK, this means, that the given server can be reached by GPRSCore
- setting CenterID/CommServerID: M2M02/COM_M2M02, reporting of center_id and com_id of the connected KMCore
Since Version 4.3.9 the following entries may be seen:
- Using new Request&Delete Communication Scheme, this means that data is fetched and delete in two steps, this improved the robustness against data loss a lot
- Fetched-1 1 Messages from Server: 59/44, this means that 1 message was fetched from the server, it lenghth was 59 bytes and in compressed form it were 44 bytes
- Deleting 1 Messages on Server, this means that one formerly fetched message was deleted on the cluster
- Sent 1 request to Cluster, this means that one Request (DataRequest, AddMFP, DeleteMFP) was sent to the cluster
Since Version 5.0.0 the following entries may occur:
- ADKConnector Version=0x1000005, this is the Version of the running ADKConnector Service
- ADKConnector.run(), releasing full office list for M2M02, this means a request to fetch all SALES and SERVICE offices for the given center_id was sent to the ADKConnector
- ADConnector.receivedOfficeList: n=6, this means a List with 6 SALES or SERVICE offices was received and is delegated to the cluster
- ADKConnector.run() next full office list in 11044 s, this means in the given amount of time the offices list will be requested again
- ADKConnector.run(), releasing full device list, this means a request to fetch a list with all MFPs was sent to the ADKConnector
- ADConnector.receivedDeviceList: n=784, a list with 784 MFPs was received from the ADKConnector and will be processed
- ADKConnector.run() next full device list in 815747 s, this means in the given amount of time the list with all MFPs will be requested again
When the application is shut down, a footer is generated with similar information to the header