All error messages generated by the connector are stored in a message file named TelcordiaConnector.txt. (The name of the file is determined by the LogFileName standard connector configuration property.) Each error has an error number followed by the error message:
Message number Message text
The connector handles specific errors as described in the following sections.
There are two ways to handle requests that cannot be processed:
<MSG> <CODE> 0173 </CODE> <TEXT> LSO NOT FOUND IN WC MAPING REFERENCE TABLE </TEXT> <ERRTAGPATH> DELV.SR.RU.DATA.CKT.NEWACL.LSO </ERRTAGPATH> </MSG>
Such responses or order state changes must trigger a collaboration object to return to the ICS integration broker.
The error message ABON_APPRESPONSETIMEOUT is returned when:
If the connector retrieves a message that is associated with an unsubscribed business object, the connector delivers a message to the queue specified by the UnsubscribedQueue property.
When a NO_SUBSCRIPTION_FOUND code is returned by the gotApplEvent() method, the connector sends the message to the queue specified by the UnsubscribedQueue property and continues processing other events.
When the gotApplEvent() method returns a CONNECTOR_NOT_ACTIVE code, the pollForEvents() method returns an APP_RESPONSE_TIMEOUT code and the event remains in the InProgress queue.
If the data handler fails to convert a message to a business object, or if a processing error occurs that is specific to the business object (as opposed to the JMS provider), the message is delivered to the queue specified by ErrorQueue. If the ErrorQueue is not defined, messages that cannot be processed due to errors will be discarded.
If the data handler fails to convert a business object to a message, BON_FAIL is returned.