5.5 Messages from KDCCP0001 to KDCCP2999, and the KDCCP9000 message
This section describes the messages from KDCCP0001 to KDCCP2999, and also the KDCCP9000 message that is output by the C4Fault class.
-
KDCCP0001-E
FaultCode: {http://c4web.cosminexus.com}Client.ConnectionRefused
FaultString: KDCCP0001-E Connection to SOAP server was refused. details = detailed-information
FaultActor: none
FaultDetail: none
- Description
-
A connection request to the SOAP service is denied. The possible causes are as follows:
-
The connection destination SOAP service or the J2EE server is not running.
-
The URL of the connection destination SOAP service is incorrect.
-
A problem exists in the network environment.
The cause of denial is described in detailed-information.
-
- Action
-
Make sure that there is no problem in the cause described in detailed-information.
-
KDCCP0002-E
FaultCode: {http://c4web.cosminexus.com}Server.NoService
FaultString: KDCCP0002-E The SOAP engine could not find a target service to invoke. targetService is service-name
FaultActor: none
FaultDetail: none
- Description
-
The service-name service is not registered.
- Action
-
Make sure that the service-name service is deployed.
Make sure that the URL of the service-name service is correct.
-
KDCCP0003-E
FaultCode: {http://c4web.cosminexus.com}Server.ClassNotFound
FaultString: KDCCP0003-E Class file not found. Class name = class-name
FaultActor: none
FaultDetail: none
- Description
-
The class file of the SOAP service specified with class-name does not exist.
The possible causes are as follows:
-
The service is not deployed as a J2EE application.
-
- Action
-
Deploy the service according to the operation of the Management Server.
-
KDCCP0004-E
FaultCode: {http://c4web.cosminexus.com}Server.MethodNotFound
FaultString: KDCCP0004-E Method not found. Method name = method-name, Service name = service-name
FaultActor: none
FaultDetail: none
- Description
-
The service cannot be invoked because the method-name method of the service-name service does not exist.
- Action
-
Make sure that the method-name method of the service-name service is implemented. Also check that the arguments of the methods implemented in the method-name method of the service-name service are correct.
-
KDCCP0005-E
FaultCode: {http://c4web.cosminexus.com}Client.HTTPMessageNotPredicted
FaultString: KDCCP0005-E The HTTP message which is not predicted was received. Status Code = status-code, Reason Phrase = detailed-information, Content-Type = content-type
FaultActor: none
FaultDetail: none
- Description
-
The SOAP client library received an unpredicted HTTP message. status-code describes the HTTP return code. detailed-information describes the HTTP return message. content-type describes the content type of the received HTTP message. If status-code is 0 and detailed-information and content-type are null, either of the following might have occurred:
- The connection pooling functionality is enabled and the HTTP server on which the connection destination SOAP service is running or other devices such as relay network equipment are not set up properly.
- The connection is disconnected in, for example, the network path between the SOAP client and the connection destination SOAP service.
- Action
-
-
Make sure that the URL of the SOAP service is correct.
-
Check if the user authentication is required for the SOAP service.
-
If the user authentication is required for the SOAP service, make sure that there are no mistakes in the user ID and in the password specified in the URL of the SOAP service.
-
If the connection pooling functionality is enabled, make sure that the HTTP server on which the connection destination SOAP service is running and other devices such as relay network equipment are set up properly.
If there are no problems in the above details, contact the system administrator.
-
-
KDCCP0006-E
FaultCode: {http://c4web.cosminexus.com}Client.SOAPMessageNotPredicted, or {http://c4web.cosminexus.com}Server.SOAPMessageNotPredicted
FaultString: KDCCP0006-E The SOAP message which is not predicted was received. Detail = maintenance-information
FaultActor: none
FaultDetail: none
- Description
-
- When the local part of FaultCode begins with Client
-
The SOAP client library received an unpredicted SOAP message.
- When the local part of FaultCode begins with Server
-
The SOAP Engine received an unpredicted SOAP message.
- Action
-
Make sure that the URL of the SOAP service is correct.
Make sure that the characters other than a to z, A to Z, and underscores (_) are not used at the beginning of the names described in the WSDL definition of the service.
If there are no mistakes in the URL of the SOAP service or in the characters being used, contact the system administrator.
-
KDCCP0007-E
FaultCode: {http://c4web.cosminexus.com}Server.UserServiceException
FaultString: KDCCP0007-E caught the exception that was not predicted from user implementation service. Detail = detailed-information
FaultActor: none
FaultDetail: none
- Description
-
The exception described in detailed-information is thrown from the SOAP service that is implemented by the user.
- Action
-
Revise the implementation of the SOAP service.
-
KDCCP0009-E
FaultCode: {http://c4web.cosminexus.com}Client.SOAPHeaderNotModifiedNamespace, or {http://c4web.cosminexus.com}Server.SOAPHeaderNotModifiedNamespace
FaultString: KDCCP0009-E SOAP header is not modified namespace.
FaultActor: none
FaultDetail: none
- Description
-
- When the local part of FaultCode begins with Client
-
The names of the child elements of the SOAP header included in the SOAP message sent from the client are not modified. The SOAP message received by the client is also not modified.
- When the local part of FaultCode begins with Server
-
The names of the child elements of the SOAP header that is included in the SOAP messages received by the SOAP Engine or the SOAP messages to be sent by the SOAP Engine are not modified.
- Action
-
Make sure that the names of the child elements of the SOAP header are modified.
-
KDCCP0012-E
FaultCode: {http://c4web.cosminexus.com}Client.IOError, or {http://c4web.cosminexus.com}Server.IOError
FaultString: KDCCP0012-E The IO error occurred. details = detailed-information
FaultActor: none
FaultDetail: none
- Description
-
An IO error has occurred.
- Action
-
Take the following actions depending on detailed-information. The countermeasures corresponding to the respective detailed-information are as follows:
- java.io.IOException: No serializer found for class-name1 in registry class-name2
-
The serializer corresponding to class-name1 does not exist in class-name2. Make sure that there are no mistakes in the service settings.
- java.io.IOException: Cannot serialize a raw object
-
The java.lang.Object type cannot be used directly in the arguments or as a return value type. Use a type that inherits the java.lang.Object type.
- In cases other than above
-
Make sure that there is no problem in the cause described in detailed-information.
-
KDCCP0013-E
FaultCode: {http://c4web.cosminexus.com}Server.ServiceException
FaultString: KDCCP0013-E Could not connect the JNDI service. details = detailed-information
FaultActor: none
FaultDetail: none
- Description
-
An attempt to connect to the JNDI service has failed.
- Action
-
Check that there is no mistake in the contents specified in JNDI name space of the EJB interface and in CORBA NamingService URL.
-
KDCCP0014-E
FaultCode: {http://c4web.cosminexus.com}Client.NoSOAPAction
FaultString: KDCCP0014-E No SOAPAction Header.
FaultActor: none
FaultDetail: none
- Description
-
SOAPAction does not exist in the HTTP headers of the SOAP messages sent from the client.
- Action
-
Either specify SOAPAction in the HTTP headers or set up the value of fault_omit_soapaction in the server definition file to false.
-
KDCCP0015-E
FaultCode: {http://c4web.cosminexus.com}Server.userException
FaultString: KDCCP0015-E The user definition exception occurred.exceptionName = exception-class-name
FaultActor: none
FaultDetail: exception-class-information
- Description
-
A user-defined exception specified in exception-class-name is thrown from the SOAP service implemented by the user.
- Action
-
Take action according to the contents of the exception.
-
KDCCP0016-E
FaultCode: {http://c4web.cosminexus.com}Server.ServiceException
FaultString: KDCCP0016-E Could not narrow <beanJNDIName> to <homeInterfaceName>. details = detailed-information
FaultActor: none
FaultDetail: none
- Description
-
An attempt to downcast objects from beanJNDIName to homeInterfaceName has failed. The name specified in the -J option of the Java2WSDD command will be output in beanJNDIName. Also, the name specified in the -H option of the Java2WSDD command will be output in homeInterfaceName.
- Action
-
Make sure that there is no mistake in the contents specified in the -J option and the -H option of the Java2WSDD command. Take action according to the contents of detailed-information. If you cannot take actions according to the contents of detailed-information, contact the system administrator.
-
KDCCP0020-E
FaultCode: {http://c4web.cosminexus.com}Server.InvalidContentType
FaultString: KDCCP0020-E Invalid content type. ContentType = content-type
FaultActor: none
FaultDetail: none
- Description
-
The SOAP Engine received a request message of an unpredicted content-type.
- Action
-
Make sure that the SOAP client is sending correct messages.
-
KDCCP0025-E
FaultCode: {http://schemas.xmlsoap.org/soap/envelope/}VersionMismatch
FaultString: KDCCP0025-E Invalid namespace associated with the SOAP envelope. Invalid namespace = namespace
FaultActor: none
FaultDetails: none
- Description
-
The SOAP Engine cannot recognize namespace correlated to the SOAP envelope included in the received SOAP message.
- Action
-
Specify http://schemas.xmlsoap.org/soap/envelope/ in namespace correlated to the SOAP envelope.
-
KDCCP0053-E
FaultCode: {http://c4web.cosminexus.com}Client.ConnectionNotAvailable
FaultString: KDCCP0053-E There is no connection that can be used. (connections_under_use = connection-under-use, connections_in_connection_pool=connections-in-connection-pool)
FaultActor: none
FaultDetails: none
- Description
-
A usable connection does not exist.
- Action
-
The possible causes are as follows. Take action depending upon the cause.
-
The value of c4web.common.connection_pool.max_connection is incorrect.
-
The upper-limit value of the file descriptor that can be used in the OS is less.
-
Other processes are inappropriately using too many file descriptors.
-
There are requests exceeding the processing performance of the J2EE server.
-
There is a request with an unduly long processing time.
-
-
KDCCP0054-E
FaultCode: {http://c4web.cosminexus.com}Client.MIMEMessageNotPredicted or {http://c4web.cosminexus.com}Server.MIMEMessageNotPredicted
FaultString: KDCCP0054-E An instance of the javax.activation.DataHandler class is invalid. (detail = detailed-information)
FaultActor: none
FaultDetails: none
- Description
-
An instance of the javax.activation.DataHandler class is invalid.
- Action
-
When generating the instances of the javax.activation.DataHandler class, make sure that the following points hold true in connection with the value specified in the constructor:
- When instances are generated with the constructor DataHandler (DataSource)
-
-
Does the file that is specified during the generation of the javax.activation.FileDataSource object that is used as an argument exist?
-
Is the file path correct?
-
Is the access permission available for the file?
-
- When instances are generated with the constructor DataHandler (Object, String)
-
-
Is the correct MIME type specified in the second argument?
-
Is the object corresponding to the MIME type specified in the first argument?
-
In other cases, take the action according to detailed-information.
-
KDCCP1106-E
FaultCode: {http://c4web.cosminexus.com}Server.NoService
FaultString: KDCCP1106-E=The CosminexusSOAP engine could not find a target service to invoke! targetService is service-name.
FaultActor: none
FaultDetails: none
- Description
-
The service-name service is not registered.
- Action
-
Make sure that the service-name service is deployed.
Make sure that the URL of the service-name service is correct.
-
KDCCP1403-E
FaultCode: {http://c4web.cosminexus.com}Server.IllegalState
FaultString: KDCCP1403-E The SOAP engine is not in an appropriate state for the requested operation. Detail = detailed-information1
FaultActor: none
FaultDetails: none
- Description
-
An invalid or inappropriate operation was performed. The status of the SOAP Engine does not correspond to the requested operation.
- Action
-
Take the following actions depending on the contents of detailed-information1:
-
An EJB object no longer exists. (detailed-information2)
An EJB object does not exist in the EJB container because of the error described in detailed-information2. Remove the cause described in detailed-information2.
-
java.rmi.ServerException: java.rmi.RemoteException: javax.ejb.ConcurrentAccessException: Concurrent method call is forbidden.;
The remove method is invoked during the EJB operation. Check the state of the EJB.
-
An attempt to get a domain name has failed. (detailed-information2)
The domain name cannot be acquired because of the error described in detailed-information2. Remove the cause described in detailed-information2.
-
-
KDCCP1404-E
FaultCode: {http://c4web.cosminexus.com}Server. UnsupportedOperation
FaultString: KDCCP1404-E The requested operation is not supported. Detail = detailed-information
FaultActor: none
FaultDetails: none
- Description
-
The requested operation is not supported.
- Action
-
Take the following action according to the contents of detailed-information:
-
Application scope does not permit a remove() invocation on EJBObject.
In an EJB form of service in which DeployScope is Application, you cannot invoke the remove method. Do not invoke the remove method.
-
-
KDCCP1405-E
FaultCode: {http://c4web.cosminexus.com}Server.IllegalState
FaultString: KDCCP1405-E The requested message has an invalid session Id.
FaultActor: none
FaultDetails: none
- Description
-
An invalid session ID is included in the request message received by the server during the invocation of the service method in a SOAP application that uses RPC or EJB.
The possible causes are as follows:
-
When the scope is Session, the service method is invoked after the session is made invalid by invoking the C4Session.invalidate method in the service side.
-
When the scope is Session, the service method is invoked after the session is made invalid because of the session timeout.
-
- Action
-
To inherit a session, make sure that the session is not invalid because of the timeout. Make changes in the processing at the client side in such a way so that the interval of the service method invocation does not exceed the timeout value.
Furthermore, after invoking the C4Session.invalidate method, do not use the same service class to invoke the service method. If a session need not be inherited, create a new service class object at the client side, and then invoke the method of the service class.
-
KDCCP1406-E
FaultCode: {http://c4web.cosminexus.com}Server.IllegalState
FaultString: KDCCP1406-E Cannot get a HTTP Session in service-name service. Detail = detailed-information
FaultActor: none
FaultDetails: none
- Description
-
The HTTP session cannot be acquired.
- Action
-
Revise the settings of the J2EE server according to the contents of detailed-information.
-
KDCCP1407-E
FaultCode: {http://c4web.cosminexus.com}Server. IndexOutOfBounds
FaultString: KDCCP1407-E Cannot create a new session as the limit on maximum number of sessions has already been reached available-session-numbers in service-name service.
FaultActor: none
FaultDetails: none
- Description
-
A new session could not be created because the number exceeds the maximum value of the usable sessions.
- Action
-
If necessary, increase the maximum value of the number of the usable sessions.
-
KDCCP9000-E
FaultString: KDCCP9000-E C4Fault exception occurred. Detail = detailed-information
- Description
-
The C4Fault exception is thrown.
This message is output even when the C4Fault exception is thrown from a user-implemented SOAP application. In such a case, the value specified during the generation of the C4Fault class will be set up in FaultCode, FaultActor, and in FaultDetail.
- Action
-
Take action according to the contents of detailed-information. If the action to be taken according to detailed-information is not clear, contact the system administrator.