8.2 Messages from KDJJ10000 to KDJJ19999 : Messages

KDJJ10002-E

The provider class, aa....aa, could not be instantiated. Processing will continue but the class will not be utilized

aa....aa: Provider class name

Description: The provider could not be instantiated. The provider cannot be used.
Action: See the displayed information and then take action. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10003-E

A message body reader for the type, class aa....aa, could not be found

aa....aa: Java type corresponding to the received entity body

Description

Resource-side

MessageBodyReader that reads the received entity body could not be found. An unsupported MIME media type is specified in the Consumes annotation of the Web resource method, or an unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.
Client-side

MessageBodyReader that reads the received entity body could not be found. An unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.

Action

Specify a supported MIME media type in the Consumes annotation of the Web resource method. Check whether the HTTP client or the Web resource sent a message about the unsupported MIME media type.

KDJJ10005-E

The class aa....aa could not be found. This class is ignored.

aa....aa: Specified class name

Description: The class specified in the servlet initialization parameters com.sun.jersey.spi.container.ContainerResponseFilters and/ or com.sun.jersey.spi.container.ContainerRequestFilters in web.xml could not be found. The specified class is ignored.
Action: Specify com.cosminexus.jersey.api.container.filter.LoggingFilter in the servlet initialization parameters com.sun.jersey.spi.container.ContainerResponseFilters and com.sun.jersey.spi.container.ContainerRequestFilters.

KDJJ10006-E

The following errors and warnings have been detected with resource and/or provider classes: aa....aa

aa....aa: List of sub-messages

Description: An error and/ or warning were detected while a resource class and/ or provider was being initialized.
Action: See the displayed sub-message and resolve the error. For details on the examples of sub-messages, see 8.5 Sub-messages. If a sub-message not listed in 8.5 Sub-messages is displayed, determine the cause of the error based on the contents of the message and then resolve the error.

KDJJ10009-E

Error processing resource method, aa....aa, for ResourceMethodDispatchProvider, bb....bb.

aa....aa: Method name

bb....bb: ResourceMethodDispatchProvider class name used in the JAX-RS functionality

Description: An error occurred in the processing of the resource method. An exception is thrown during the process of injection in the parameter annotated in DefaultValue of the resource method or sub-resource method.
Action: See the details and then take action. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10010-E

The RuntimeException could not be mapped to a response, re-throwing to the HTTP container

Description: The runtime exception could not be mapped to an HTTP response, and is re-thrown to the Web container.
Action: See the exception log to remove the cause of the runtime exception.

KDJJ10017-E

The exception contained within MappableContainerException could not be mapped to a response, re-throwing to the HTTP container

Description: A checked exception could not be mapped to an HTTP response, and is re-thrown to the Web container.
Action: See the exception log to remove the cause of the runtime exception.

KDJJ10018-E

Mapped exception to response: aa....aa bb....bb

aa....aa: HTTP header status code

bb....bb: Status string

Description: WebApplicationException occurred while a Web resource was being invoked. WebApplicationException is mapped to an HTTP response based on the response information in WebApplicationException.
Action: See the displayed information and then take action. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10019-E

Mapped exception to response: aa....aa

aa....aa: HTTP header status code

Description: WebApplicationException occurred while a Web resource was being invoked. WebApplicationException is mapped to an HTTP response based on the response information in WebApplicationException.
Action: See the displayed information and then take action. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10020-E

The ResourceConfig instance does not contain any root resource classes.

Description

The Web application (WAR file) does not contain valid root resource classes. The WAR file does not contain any root resource class, or the value specified in the servlet initialization parameter com.sun.jersey.config.property.packages in the web.xml file is incorrect.

Action

Check the following items:

Is the root resource class included correctly in the WAR file?

The root resource class must be deployed in \WEB-INF\lib and/or \WEB-INF\classes of the WAR file.
Is an appropriate package name described in the servlet initialization parameter com.sun.jersey.config.property.packages in the web.xml file

KDJJ10024-E

A message body reader for Java class aa....aa, and Java type bb....bb, and MIME media type cc....cc was not found

aa....aa: Instance class

bb....bb: Generic type

cc....cc: MIME media type

Description: MessageBodyReader that reads the received entity body could not be found. An unsupported MIME media type is specified in the Consumes annotation of the Web resource method, or an unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.
Action: Specify a supported MIME media type in the Consumes annotation of the Web resource method. Check whether the HTTP client sent a message about the unsupported MIME media type.

KDJJ10026-E

A message body writer for Java class aa....aa: , and Java type bb....bb: , and MIME media type cc....cc: was not found

aa....aa: Instance class

bb....bb: Generic type

cc....cc: MIME media type

Description: MessageBodyReader that writes the sent entity body could not be found. An unsupported MIME media type is specified in the Produces annotation of the Web resource method, or an unsupported MIME media type is specified in the Accept HTTP header of the received HTTP message.
Action: Specify a supported MIME media type in the Produces annotation of the Web resource method. Check whether the HTTP client requests a message about the unsupported MIME media type.

KDJJ10028-E

Exception mapper aa....aa for Throwable bb....bb threw a RuntimeException when attempting to obtain the response

aa....aa: Exception mapping provider name

bb....bb: Exception name

Description: A runtime exception occurred while creating a response with the exception mapping provider.
Action: See the exception log to remove the cause of the runtime exception.

KDJJ10031-E

A message body reader for Java class aa....aa, and Java type bb....bb, and MIME media type cc....cc was not found

aa....aa: Object class

bb....bb: Generic type

cc....cc: MIME media type

Description: MessageBodyReader that reads the received entity body could not be found. An unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.
Action: Specify a supported MIME media type in the Content-Type HTTP header of the received HTTP message.

KDJJ10032-E

A message body writer for Java class aa....aa, and Java type bb....bb, and MIME media type cc....cc was not found

aa....aa: Object class

bb....bb: Generic class

cc....cc: MIME media type

Description: MessageBodyWriter that writes the received entity body could not be found. An unsupported MIME media type is specified in the Content-Type HTTP header of the received HTTP message.
Action: Specify a supported MIME media type in the Content-Type HTTP header of the HTTP message.

KDJJ10039-E

Failed to invoke the resource.

Description: An exception occurred while an HTTP request was being processed.
Action: See the exception log to remove the cause of the runtime exception. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ10040-E

There are no matched resources that can consume aa....aa media type

aa....aa: MIME media type

Description: There are no Web resources that can process the MIME media type specified in the Content-Type HTTP header of the received HTTP request.
Action: Implement a Web resource that can process the MIME media type specified in the Content-Type HTTP header. Also, check whether the HTTP client sent a message about the unsupported MIME media type.

KDJJ10041-E

There are no matched resources that can produce aa....aa media type

aa....aa: MIME media type

Description: There are no Web resources that can process the MIME media type specified in the Accept HTTP header of the received HTTP request.
Action: Implement a Web resource that can process the MIME media type specified in the Accept HTTP header. Also, check whether the HTTP client requests a message about the unsupported MIME media type.

KDJJ10042-E

The request parameter count exceeded the maximum number (context root = aa....aa, request URI = bb....bb, max count = cc....cc)

aa....aa: Context root

bb....bb: Request URI

cc....cc: Maximum number of form parameters

Description: The number of form data parameters sent by the client exceeded the maximum value.
Action: Check whether the number of form data parameters sent by the client exceeds the value (maximum number of form parameters) set in the webserver.connector.limit.max_parameter_count key of the user property file for J2EE servers. If the number of form parameters used exceeds the maximum value, change the maximum number of form parameters to an appropriate value. If you change the maximum number of form parameters, you must restart the J2EE server.

KDJJ18888-E

Client API could not complete the requested operation. (detail=aa....aa)

aa....aa: Detail

Description: Client API could not complete the requested operation.
Action: Remove the cause of the error based on the detail. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.

KDJJ19999-E

Error Occurred: (details= aa....aa)

aa....aa: Details

Description: An error occurred.
Action: Remove the cause of the error based on the details. Also, check whether other error messages are being displayed. If another error message is displayed, take action based on the contents of that message.