The server returns error responses to client requests

If clients are requesting operations that legitimately should fail (for example, they are targeting entries that do not exist, are attempting to update entries in a way that would violate the server schema, or are performing some other type of inappropriate operation), then the problem is likely with the client and not the server.

If the PingAuthorize Server work queue is configured with a maximum capacity, and that capacity has been reached, then the server begins rejecting all new requests until space is available in the work queue. In this case, you might need to alter the server configuration, the client requests, or both so that they can be processed more efficiently. Alternatively, you might need to add additional server instances to handle some of the workload.

If an internal error occurs within the server while processing a client request, then the server terminates the connection to the client and logs a message about the problem that occurred. This should not happen under normal circumstances. Contact your authorized support provider for help with diagnosing and correcting the problem.

If the server has an issue while interacting with the underlying database (for example, an attempt to read from or write to disk failed because of a disk problem or lack of available disk space), then the server can begin returning errors for all attempts to interact with the database. This will continue until you close and re-open the back end and give the database a chance to recover itself. For information about this type of issue, review the je.info.* file in the database directory.