Package com.highdeal.cnd.message

Class CommunicationFailureException

java.lang.Object

java.lang.Throwable

java.lang.Exception

com.highdeal.cnd.message.CommunicationFailureException

All Implemented Interfaces:

Serializable

public class CommunicationFailureException
extends Exception

Exception internally thrown when the communication between your client application and the SAP CC Core Server system fails via the Message TCP technical interface: This exception is only generated on client-side in your customized charging client. (in opposite to the ServerFailureException that denotes a failure which occurred on server side in the connected SAP CC system).

Note

This exception incorporates all nonbusiness exceptions that can occur on client side when your charging client requests some service operations from the SAP CC system via the Message TCP high-speed technical interface.

Refer also to the business exceptions specified by this Java API Reference documentation.

Reasons

The available reasons that are carried by this exception are:

Failure	Reason Code	Customizing and Integration	Troubleshooting (Next Steps)
Unsupported failure	0	Note To design the exception and error handling functions (automated treatments, logging and manual treatments), see the Field Detail section in this topic. Refer to the information available in the Customizing subsection of each failure to develop your integration code.	Note For troubleshooting investigations, see the Field Detail section in this topic. Refer to the information available in the Next Steps subsection of each failure.
Connection closed	1
Too long message	2
Interrupted timeout communication	3
Server system unreachable	4
Connection queue full (deprecated and now revoked)	5

Consider the detailed information in the Field Detail section.

Note

See the Field Detail section for more information about troubleshooting:

• determine some integration and implementation changes that are necessary during the implementation project
• perform troubleshooting investigations to correct a potential anomaly

Implementation in Your Client Application

Exception and Error Handling

Depending on your business requirements design and develop the handling functions in your client application.

For each exception reason, you determine the expected treatments in your charging client.

See Also:

• Serialized Form

Field Summary

Fields

Modifier and Type	Field	Description
static final int	CONNECTION_CLOSED	1: Failure when the communication between your client application and the SAP CC Core Server system is closed or is closing.
static final int	CONNECTION_QUEUE_FULL	Deprecated. This reason code is deprecated and can no longer be create in your charging client.
static final int	INTERRUPTED_TIMEOUT_COMMUNICATION	3: Failure when the comunication has been interrupted due to timeout specified by the charging client in your client application.
static final int	SERVER_UNREACHABLE	4: Your charging client has lost all connections to the dispatcher instances of the SAP CC Core Server system.
static final int	TOO_LONG_MESSAGE	2: Failure whn the sent or received message cannot be managed by the communication protocol because it is too long.
static final int	UNSUPPORTED_FAILURE	0: The reason is unknown or unsupported; If this reason is signaled, it could denote a bug in the SAP CC software.

Constructor Summary

Constructors

Constructor	Description
CommunicationFailureException(int reason, String msg)	The reason/message exception builder.
CommunicationFailureException(int reason, String msg, Throwable t)	Full Exception builder.
CommunicationFailureException(int reason, Throwable t)	The reason/throwable exception builder.

Method Summary

Modifier and Type	Method	Description
void	attach(Object attachment)
Object	attachment()
String	getMessage()	Returns a comprehensive description of the exception.
int	getReason()	Returns the numerical reason code of the exception.
String	reasonToString()	Returns the reason code as a string; Prefer the numerical codes and available Java constants.

Methods inherited from class java.lang.Throwable

addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, wait, wait, wait

Field Details

UNSUPPORTED_FAILURE

public static final int UNSUPPORTED_FAILURE

0: The reason is unknown or unsupported; If this reason is signaled, it could denote a bug in the SAP CC software. Contact your SAP Support Team.

Recommendation

In a production system landscape, please contact a support specialist from your SAP Support Team and report an incident.

See Also:

• Constant Field Values

CONNECTION_CLOSED

public static final int CONNECTION_CLOSED

1: Failure when the communication between your client application and the SAP CC Core Server system is closed or is closing.

Next Steps

Perform the following investigations to troubleshoot your problem:

• Verify that the instances of the SAP CC Core Server system are up and running
• Verify that firewalls have been disabled

See Also:

• Constant Field Values

TOO_LONG_MESSAGE

public static final int TOO_LONG_MESSAGE

2: Failure whn the sent or received message cannot be managed by the communication protocol because it is too long.

Next Steps

Perform the following investigations to troubleshoot your problem:

• Verify that your client application (mediation system) does not send messages larger than 1 Mb
• Verify that firewalls have been disabled

See Also:

• Constant Field Values

INTERRUPTED_TIMEOUT_COMMUNICATION

public static final int INTERRUPTED_TIMEOUT_COMMUNICATION

3: Failure when the comunication has been interrupted due to timeout specified by the charging client in your client application.

See Also:

• Constant Field Values

SERVER_UNREACHABLE

public static final int SERVER_UNREACHABLE

4: Your charging client has lost all connections to the dispatcher instances of the SAP CC Core Server system.

Next Steps

Monitor the connections between your client application (mediation system) and the SAP CC system:

• In the SAP CC Admin+ user interface with the list_clients command.
• In CA Introscope for SAP
• In SAP Solution Manager

Refer to the SAP CC Operations Guide for more information about monitoring the SAP CC system landscape.

See Also:

• Constant Field Values

CONNECTION_QUEUE_FULL

@Deprecated
public static final int CONNECTION_QUEUE_FULL

Deprecated.

This reason code is deprecated and can no longer be create in your charging client.

5: Failure when the connection queue is full in your client application (mediation system).

See Also:

• Constant Field Values

Constructor Details

CommunicationFailureException

public CommunicationFailureException(int reason,
 String msg,
 Throwable t)

Full Exception builder.

Parameters:

reason - The exception reason

msg - The exception message

t - The nested (Throwable) exception

CommunicationFailureException

public CommunicationFailureException(int reason,
 String msg)

The reason/message exception builder.

Parameters:

reason - The exception reason

msg - The exception message

CommunicationFailureException

public CommunicationFailureException(int reason,
 Throwable t)

The reason/throwable exception builder.

Parameters:

reason - The exception reason

t - The nested (Throwable) exception

Method Details

getReason

public int getReason()

Returns the numerical reason code of the exception. The available codes are:

• UNSUPPORTED_FAILURE
• CONNECTION_CLOSED
• TOO_LONG_MESSAGE
• INTERRUPTED_TIMEOUT_COMMUNICATION
• SERVER_UNREACHABLE
• CONNECTION_QUEUE_FULL (deprecated and revoked)

Returns:

The reason of the exception

getMessage

public String getMessage()

Returns a comprehensive description of the exception.

Overrides:

getMessage in class Throwable

Returns:

A readable exception description

attach

public void attach(Object attachment)

attachment

public Object attachment()

reasonToString

public String reasonToString()

Returns the reason code as a string; Prefer the numerical codes and available Java constants. The available codes are:

• unsupportedFailure
• connectionClosed
• tooLongMessage
• interruptedTimeoutCommunication
• serverUnreachable
• connectionQueueFull (deprecated and revoked)