12.5.4 Changes in messages
In Application Server version 11 and Developer version 11, the message IDs and their content output to the message log were changed or abolished. The following table lists the message IDs of Application Server version 11 and Developer version 11 that are output under the equivalent conditions. If you monitored the relevant messages, replace the message IDs according to the following table.
|
Output source |
Message in Application Server version 9 and Developer version 9 |
Replacement ID in Application Server version 11 and Developer version 11 |
Log level |
|
|---|---|---|---|---|
|
ID |
Content |
|||
|
Web container |
KDJE39236-I |
Web server integration will start. |
None |
Error |
|
KDJE39237-I |
The in-process HTTP server will start. The Web server integration functionality will be disabled. |
KDJE39562-I |
Error |
|
|
KDJE39238-W |
The host name specified in the property webserver.connector.inprocess_http.permitted.hosts could not be resolved. |
KDJE39563-W |
Error |
|
|
KDJE39239-W |
Access to the in-process HTTP server from a forbidden host was denied. |
KDJE39564-W |
Error |
|
|
KDJE39240-W |
The host ({0}) specified in the property webserver.connector.inprocess_http.bind_host could not be resolved. |
KDJE39565-W |
Error |
|
|
KDJE39241-E |
The in-process HTTP server could not be started on the specified port number ({0}). |
KDJE39566-E |
Error |
|
|
KDJE39242-W |
The host ({0}) specified in the property webserver.connector.inprocess_http.bind_host could not be resolved. |
KDJE39567-W |
Error |
|
|
KDJE39243-E |
The HTTP method of the sent request is not allowed. |
None |
Error |
|
|
KDJE39244-E |
The request line of the sent request has exceeded the maximum size. |
None |
Error |
|
|
KDJE39245-E |
The request header of the sent request has exceeded the maximum size. |
KDJE39568-E |
Error |
|
|
KDJE39246-E |
The request body of the sent request has exceeded the maximum size. |
KDJE39569-E |
Error |
|
|
KDJE39247-E |
The number of HTTP headers included in the sent request has exceeded the maximum number. |
KDJE39570-E |
Error |
|
|
KDJE39256-W |
The file sent as the response body of the redirect functionality could not be read. |
None |
Error |
|
|
KDJE39257-E |
An error occurred while the file sent as the response body of the redirect functionality was being read. |
None |
Error |
|
|
KDJE39258-W |
An error occurred while the response body of the redirect functionality was being sent. |
None |
Information |
|
|
KDJE39259-W |
The file sent as the response body of the error contents customization functionality was not sent to the client because it could not be read. |
None |
Error |
|
|
KDJE39260-E |
An error occurred while the file sent as the response body of the error contents customization functionality was being read. |
None |
Error |
|
|
KDJE39261-W |
An error occurred while the response body of the error contents customization functionality was being sent. |
None |
Information |
|
|
KDJE39262-E |
The request processing will be denied because the number of connections with the Web client has exceeded the maximum value. |
None |
Error |
|
|
KDJE39263-W |
The number of request processing threads is insufficient. |
None |
Error |
|
|
KDJE39265-E |
A timeout occurred while the request header from the client was being read. |
KDJE39576-E |
Warning |
|
|
KDJE39267-W |
The accessed request was denied. A request beginning with /ejb/ or /web/ cannot be used on the in-process HTTP server. |
KDJE39571-W |
Error |
|
|
KDJE39268-E |
The file sent as the response body of the redirect functionality could not be read. |
None |
Error |
|
|
KDJE39269-E |
The in-process HTTP server denied the accessed request because the body information of the HTTP request was too large. |
None |
Error |
|
|
KDJE39270-W |
The error page could not be customized because the response was already committed. |
None |
Error |
|
|
KDJE39274-E |
A failure occurred while a connection with the client was being established. |
KDJE39572-E |
Error |
|
|
KDJE39276-W |
An attempt to establish a connection with the client succeeded although a failure occurred while a connection with the client was being established. |
KDJE39573-W |
Error |
|
|
KDJE39277-E |
The in-process HTTP server denied the accessed request because an invalid request header was received. |
KDJE39574-E |
Error |
|
|
KDJE39514-W |
Some request processing threads have not finished. |
KDJE39575-W |
Error |
|
|
KDJE39561-W |
The function that narrows the search range of ServletContainerInitializer is enabled. |
None |
Error |
|
|
Redirector |
KDJE41000 to KDJE41041 |
All messages |
None# |
-- |
- #
-
Use the error log of HTTP Server as a substitute.