Service invalidation

Knowing when the configuration is invalid and when it must be modified before the service can start, is provided by the service invalidation feature described here.

A Web service is typically an automated process, called on behalf of a user or process. When a Web service has an invalid configuration, there is no graphical message informing an end user of the error. Requests continue to fail. To prevent requests from failing forever, if the Genero Web Services service (gwsproxy) cannot start within DVM_AVAILABLE time, it informs the dispatcher.

For troubleshooting and monitoring Web services, please see Get list of services invalidated by dispatcher.

The next time a request is received, the dispatcher remembers that the Proxy: gwsproxy cannot be started and sends a 503 HTTP status to the user agent.

The first time a service is not able to start, this message is returned:

Application or service has been stopped due to a fatal error

Any new request returns this message until the configuration is modified and corrected:

Bad configuration prevents application or service to start.

The service resumes when the configuration is updated.

If the service is configured in the Genero Application Server configuration file, you must restart the Genero Application Server.

If the service is configured in an external application configuration file (xcf), the configuration is reloaded each time it is modified. You do not need to restart the Genero Application Server.

This feature is only supported for Genero Web services. It is not supported for Genero Desktop Client or Genero Web Client applications.