DSEException |
A problem occurred with the process associated with the client
operation. The exception may include the following error codes:
|
DSECSSocketException |
A problem occurred with the socket when the server is using
a dynamic connection to send events to the client.
Action: Check
that the port field for the client in the session table is not null. |
DSEReplyErrorException |
A problem occurred with the reply message. The exception may
include the following error codes: - CSS08 (server side) - Error formatting the reply data
Action:
Review the reply format definition in the dsefmts.xml file.
- CSS09 (server side) - Error sending the response to the client
Note: This
exception also fires a CSReplyErrorEvent so that the server application
(provided it is a listener for this event) can know that the client
did not get the reply message and act accordingly.
Action: Check
that the proxy for the connection is still alive.
|
DSECSServerNotStartedException |
The server has not been successfully initiated.
Action: Initiate® the server again using
the initiateServer() method. |
DSECSSessionNotEstablished Exception |
The session was not established. The exception may include
the following error codes: - CSS11 (client side) - Session not established
- CSS00 (server side) - Session not established
Action: Verify that the session is initiated and that the TCP/IP
communications between client and server are active. Try to establish
the session again.
Verify that the channel session cookie support
is synchronized with the servlet engine cookie support. |
DSECSTimeoutException |
Execution has finished due to timeout.
Action: Retry. |
DSECSInvalidRequestException |
The C/S request API was not used properly. The exception may
include the following error code:
CSS11 (client side) - Session
not established
Action: Depends on the exception message: - "Session has not been established" - Establish the session and
retry.
- "Session is already established" - The establishSession method
cannot be used, because the session is already established.
- "Session is being closed" - Wait until the session is successfully
closed.
- "Server was already initiated" - The initiateServer method cannot
be used, because the server is already started.
- "Server was already stopped" - The stopServer method cannot be
used, because the server is already stopped.
|
DSECSServerServiceAlready ExistException |
A CSServer instance already exists.
Action: Either use
the already existing instance, or reset it and create a new one. |
DSECSRemoteOperation Exception |
A problem occurred in the remote operation (process). The exception
may include the following error codes: - CSS12 (client side) - Error formatting the request data.
Action:
Review the request format definition in the dsefmts.xml client file.
- CSS01 (server side) - Error reading the data from the request.
Action:
Check whether the server is started or if there are communication
problems.
- CSS02 (server side) - Error obtaining the data parameters to be
processed
Action: Check whether the server is started or if there
are communication problems.
- CSS03 (server side) - Error instantiating the invoker
Action:
Review the invoker definition and check that the invoker class exists
in the server side.
- CSS05 (server side) - Error instantiating the request format
Action:
Review the request format definition in the dsefmts.xml file and check
that the request format class exists in the server side.
- CSS06 (server side) - Error unformatting the request data
Action:
Review the request format definition in the dsefmts.xml file and check
if the request data is as the data expected.
- CSS13 (client side) - Error receiving data from the server
Action:
Try to re-establish the connection to the server. Check if the server
and the proxy are started. See the note that follows the table.
- CSS14 (client side) - Error instantiating the reply format
Action:
Review the reply format definition in the dsefmts.xml client file
- CSS15 (client side) - Error unformatting the reply data from the
server
Action: Review the data to unformat or the definition format
in the dsefmts.xml client file
- CSS10 (client side) - Error sending data to the server. (This
error may also include a java.net.ConnectionException)
Action:
Try to re-establish the connection to the server. Check if the server
and the proxy are started
|
DSECSSSLException |
Problems either initializing the SSL environment or with a
security issue during the message sending/receiving.
Action:
Look at the message associated with the exception for more information,
and fix the problem. Commonly it will be a configuration problem. |