OpenEdge REST applications can encounter exceptions, especially when attempting to communicate with the AppServer. The following table lists the exceptions and the corresponding HTTP errors that is returned by the application in each case.

Table 1. REST Application exceptions and corresponding HTTP errors
Exception HTTP Status
java.lang.Exception 500 Internal Error
com.progress.common.exception.ProException 500 Internal Error
com.progress.open4gl.Open4GLException 500 Internal Error
com.progress.open4gl.BusySessionException 503 Service Unavailable
com.progress.open4gl.ConnectException 500 Internal Error
com.progress.open4gl.BadURLException 500 Internal Error
com.progress.open4gl.ConnectFailedException 500 Internal Error
com.progress.open4gl.HostUnknownException 500 Internal Error
com.progress.open4gl.InvalidNameServerPortException 500 Internal Error
com.progress.open4gl.MsgVersionInvalidException 502 Bad Gateway
com.progress.open4gl.NameServerCommunicationsException 502 Bad Gateway
com.progress.open4gl.NameServerInterruptException 504 Gateway Timeout
com.progress.open4gl.NameServerMessageFormatException 502 Bad Gateway
com.progress.open4gl.NoSuchAppServiceException 500 Internal Error
com.progress.open4gl.OutputSetException 500 Internal Error
com.progress.open4gl.RunTime4GLException 500 Internal Error
com.progress.open4gl.RunTime4GLErrorException 500 Internal Error
com.progress.open4gl.RunTime4GLQuitException 504 Gateway Timeout
com.progress.open4gl.RunTime4GLStopException 504 Gateway Timeout
com.progress.open4gl.SystemErrorException 500 Internal Error