This appendix details
problems you may encounter when running the connector and ways to troubleshoot
the problems.
ID | Message | Type | Component | Class/method | Reason | Resolution |
---|---|---|---|---|---|---|
3 | Exception caught in RetekConnector
Agent::create ConnPool | Error | init | RetekConnector
Agent::createConn Pool | Invalid value for connector configuration property JDBCDriver Class or invalid or missing driver zip file (classes 12.zip). | Make sure that the connector configuration property JDBCDriver has a valid value. JDBCDriver zip file, classes 12.zip must be in the connector agent's run-time class path. |
| Exception caught in
DBConnPool:: DBConnPool | Error | init | DBConn Pool
constructor | Same as above | Same as above |
| Exception caught
in RetekConnector Agent::termi | Error | terminate | Retek
Connector Agent:: terminate | Trying to close invalid references to database connectors. | Contact Development team. |
| Exception caught in RetekBOHandler::
doVerbFor::java.sql
.SQLException::
| Error | Call request processing | RetekBO
Handler:: doVerbFor | Connector is configured for request processing but ConsumeMO property is not set in the connector properties, or the metaobject attributes do not correspond to the CONSUME parameters. | Check the ConsumeMO property value and/or the number and types of attributes in the configured metaobject. |
| Exception caught in
RetekBOHandler:: doVerbFor : java.sql.SQL Exception: ORA-06550: line 1, column 7: PLS-00201: identifier 'RDMONESUB _VENDOR MOD
.CONSUME' must be declared ORA-
| Error | Call request processing | RetekBO
Handler:: doVerbFor | Incorrect name for the CONSUME
-stored procedure. |
Make sure the ApplicationName property value is correct. Make sure the message type in the BO is correct. Make sure the database is configured properly and the stored procedure
exists in the DB.
|
| Exception caught in <method_name> :
<exception_info> | Error | various | various | An exception was caught in the named method. | Use the exception information to debug the problem, if possible. Otherwise, contact Development. |
10 | Could not retrieve connector configuration | Error | init | MTCon-nectorAgent::
init | Connector's call to retrieve its configuration properties failed. | Connector infrastructure issue. Contact Development. |
11 | No value for configuration property
<property name>. Using default value: <value> | Warn-ing | init | RetekCon-nectorAgent::
validate Configuration | A required property has not been set in the connector configuration. The default value will be used. | No action if default value is appropriate. |
12 | Business object creation failed for <spec_name> | Error | various | PollingUtils::
getBOs | The BO spec name is invalid or unsupported by the connector. | Check whether the BO definition exists and it is part of the connector's list of supported BOs. |
13 | No value for configuration property <property_name> | Error | init | RetekCon-nectorAgent::
validate Configuration | A required property has not been set in the connector configuration. | Set the appropriate value for the property. |
24 | Message type is null | Error | Call request processing | RetekBO
Handler:: doVerbFor | Message type in the request BO is NULL. | Make sure the message type in the BO Passed in from the collaboration object/flow has the correct value. |
35 | ThreadMetaObjects property is not set | Error | init | MTConnector
Agent:: init | The ThreadMeta Objects property has not been set for a publishing connector. | Set the Thread MetaObjects property to at least one thread MO name. |
2001 | Duplicate event file <filename> .dup from previous
run is not cleared | Error | init | MFManager::
check Previous Failure | <message
family name>.dup file exists in the working directory of connector. |
Verify that the .dup file really contains a duplicate event. If yes, remove next event from the message family staging table, delete the .dup file and then restart the connector to start polling the message family. If not, delete the .dup file and then restart the connector to start
polling the message family.
|
2002 | Invalid PollQuantity
<number> for MessageFamily <mf> | Error | init | MFManager::init | Default value for pollQuantity attribute in the Message family metaobject is invalid. | Correct the value. Valid values are either blank or any number greater than or equal to 1. |
2004 | No RIHeader in
lost event file <filename> from previous run. It cannot be processed automatically | Error | event processing | MFManager::
process Event | The business object created from <message family
name>.lost file does not contain RIHeader child object. |
Verify that the .lost file really contains a lost event. If yes, edit the .lost file to add RIHeader, and then restart the connector to process the lost event and continue polling the message family. If not, delete the .lost file and restart the connector to continue
polling the message family.
|
2005 | Failed to deliver lost event to broker from file <filename> | Error | event processing | MFManager::
process Event | The connector failed to deliver the lost event to the broker. |
Verify that the .lost file really contains a lost event. If yes, check subscription, connector status, and delivery transport status. If not, delete the .lost file and restart the connector to continue
polling the message family.
|
2006 | Failed to execute callable statement for message family <mf_name>. Additional Information: <info> | Error | event processing | MFManager::
process Event | Database access error occurred while executing the GETNXT- stored procedure call. | Check database status. |
2007 | Exception in reading output parameters of GETNXT for message family <mf_name>. Additional Information: <info> | Error | event processing | MFManager::
process Event | Database access error occurred while reading the output parameters of GETNXT-stored procedure. | Check database status. The connector will attempt to rollback the message to the message family staging table. |
2008 | Exception in rollback for message family <mf_name>. Additional Information: <info> | Error | event processing | MFManager::
process Event | Database access error occurred during rollback operation. | Check database status. The connector will attempt to write the failed message as <message family name>.lost file in the working directory. |
2009 | Exception in commit for message family <mf_name>. Additional Information: <info> | Error | event processing | MFManager::
process Event | Database access error occurred during commit operation. | Check database status. The connector will attempt to write the failed message as <message family name>.dup file in the working directory. |
2010 | Exception converting XML string into business object for message family <mf_name>. Additional Information: <info> | Error | event processing | MFManager::
process Event | The connector failed to create a business object from the XML string retrieved during polling operation. | Verify supported business objects list in connector configuration. Verify the business object definitions. Verify that the message type obtained during polling is valid. |
2011 | Invalid message type <type>. No verb support. | Error | event processing | MFManager::
process Event | The message type retrieved during the polling operation is invalid. It should have a suffix Cre or Mod or Del. The case does not matter. | Contact Retek support team. |
2013 | Message Family Manager failed to start. Additional Information: <info> | Error | init | RetekEvent
Handler constructor | The Message Family Manager failed to initialize. The additional information in log message contains actual reason for failure. | Fix the problem for that message family, and then restart connector. |
2014 | All Message Family Manager(s) failed to start | Fatal error | init | RetekEvent
Handler constructor | All Message Family Managers supported by the event handler failed to initialize. The additional information in log message contains actual reason for failure for each message family. | Fix the problem for each message family, and then restart connector. |
2015 | No message family metaobjects defined for Thread Metaobject <mo_name> | Fatal error | init | MFManager::
createMF Managers | The business object level AppSpecificInfo is blank in the thread metaobject. | Add the name of the appropriate message family metaobject to the AppSpecificInfo of thread metaobject |
2016 | Failed to create message family metaobject <mo_name>. Additional information: <info> | Error | init | MFManager::
createMF Managers | The event handler failed to create a business object from the name of the message family metaobject. |
Verify name of message family metaobject specified in the thread metaobject. Verify that all required metaobjects are listed in connector property and
the connector has access to their definitions.
|
2017 | Failed to create all message family metaobjects | Fatal error | init | MFManager::
createMF Managers | The event handler failed to initialize all message family metaobjects. |
Verify name of message family metaobjects specified in the thread metaobject. Verify that all required metaobjects are listed in connector property and
the connector has access to their definitions.
|
2018 | Polling request resulted in fatal error in all the Message Family Manager(s) | Fatal error | Event
processing | RetekEvent
Handler:: process Events | All message families polled by the event handler resulted in fatal error. | The log output contains enough information to diagnose the problem for each message family failure. |
2019 | Attribute Type <type> not supported | Error | init | MFUtil::get
SQL Type | The data type of an attribute in the message family metaobject is not supported. | The output parameters in the message family metaobject should be of type String. For input parameters only basic data types are supported. |
2021 | Failed to delete lost event file <filename> | Warning | Event processing | MFManager::
process Event | The connector failed to delete the .lost file after successful lost event delivery to the broker. | Delete the .lost file manually from the current working directory. This ensures that the same lost event is not picked up again if the connector is restarted due to some reason. |
2022 | BOPrefix not set in the XML data handler config object | Warn-ing | init | RetekMessage
Formatter constructor | The BOPrefix attribute in the XML data handler metaobject is blank. | If the business object names have a prefix, then it should be set as the value of BOPrefix. |
2024 | SQL Type <type>
is not supported | Error | init | MFUtil::
setIn Parameter | The equivalent SQL type for the data type of an attribute in the message family metaobject is not supported by the connector. | Only basic data types and their equivalent SQL types are supported for the input parameters. |
2025 | Could not get business object name from xml string. | Error | Event processing | RetekMessage
Formatter:: getBO Name | There is no DOCTYPE declaration in the XML string retrieved during polling. | Contact Retek support team. |