17.3.4 Function restrictions after an error
When an error occurs in the asset management system, the asset management server issues a message of type E. The functions of the asset management system that become restricted by errors are explained below.
- Organization of this subsection
(1) When urgent or serious system errors occur
If an urgent or serious system error occurs from which recovery is not possible or which might corrupt information if operations are continued, all services of the asset management system are stopped.
Urgent or serious system errors are as follows:
-
Invalid settings or read errors in the environment definition file
-
Detection of damaged meta table
-
Program exceptions, such as a general protection exception
-
Internal program errors
(2) When system errors that are not urgent or serious occur
A system error that is not urgent or serious might occur from which recovery is possible over time and which will not corrupt information. When such an error occurs, even if operations continue, the process in which the error was detected will be terminated.
System errors that are not urgent or serious are as follows:
-
Invalid format of messages from Web browser
-
Message log output errors
-
Database connection broken by the DBMS
-
Notification of errors in a program linked to the asset management system
-
Access error notification during addition, updating, or deletion of asset information (except when there is no property data that becomes the key)
-
Internal program errors
(3) When operational errors occur
If either of the following operational errors occurs in the asset management system, no asset management system services will stop:
-
Login error due to invalid user ID or password
-
Import errors during asset management system operation and while importing information from JP1/IT Desktop Management 2 - Manager
(4) When temporary errors occur
If a temporary error occurs from which recovery might be possible by re-executing the command at a later time, the executing process in which the error was detected is terminated, releasing the session.
The following are examples of temporary errors:
-
Memory allocation errors and database connection errors
-
Database lock errors
-
Import errors during asset management system operation and while importing information from JP1/IT Desktop Management 2 - Manager