|
|
|
|
|
|
|
|
|
|
The sending and receiving applications may be using different repositories with different definitions of the same class. Or the sending application does not conform to the wire format.
|
|
|
|
|
|
This is an internal error, the program may be out of java virtual memory or another internal jvm exception occurred.
|
|
|
|
|
|
|
|
|
|
|
|
A sequence class description name appears to be of the self-documenting form, but is incomplete or malformed.
|
|
|
|
|
|
|
|
|
|
|
|
The MTree contains a node not supported by the SDK during serialization. Do not attempt to construct structured data from it.
|
|
|
|
|
|
|
|
|
|
|
|
An error was reported by the TIBCO Rendezvous layer. Please refer to the relevant documentation for details.
|
|
|
|
|
|
Most likely, the sending and receiving adapters use a different definition for a particular metadata class. Preferably the same repository instance should be used, and definitely both metadata definitions for a particular class must be identical if the repositories are separate.
|
|
|
ERR_COMPONENT_NULL_PARAMETER
|
|
|
|
|
|
ERR_COMPONENT_OPERATION_ERROR
|
|
|
|
|
|
ERR_COMPONENT_UNEXPECTED_CLASS
|
|
|
|
|
|
|
|
|
The operation class specified should be in the metadata loaded by the adapter configuration instance.
|
|
|
|
|
|
|
|
|
ERR_METADATA_BAD_DATA_TYPE_FORMAT
|
|
|
One of the self-describing class descriptions is malformed. See the documentation for the correct format for the self-describing class description strings. For example, "fixed.p.s" cannot be "fixed.p".
|
|
|
|
|
|
Some aspect of opening and parsing the file as an XML document failed. Confirm the presence of the file, permissions on the file, and that the contents are indeed a valid XML document.
|
|
|
ERR_MARSHALLER_UNEXPECTED_CLASS
|
|
|
|
|
|
|
|
|
There is no resolution for this. A java.lang.InterruptedException was thrown during event dispatch.
|
|
|
|
|
|
The dependent component (typically a session) required by this endpoint cannot be found in the component registry. Either the component name is incorrect, or the configuration needs to be updated to include this component.
|
|
|
|
|
|
This can occur if there is a mismatch between the actual data and the class description provided (metadata). One of the two must change. Typically, this is the result of two applications using different sources for the metadata information, which have become out of sync. Either use the same source for metadata, or ensure that all sources are in sync.
|
|
|
ERR_METADATA_CLASS_NOT_FOUND
|
|
|
The specified metadata class must be loaded by the adapter by specifying either the loadUrl or the searchUrl in configuration.
|
|
|
|
|
|
|
|
|
ERR_COMPONENT_HAWK_PARAMETER_ERROR
|
|
|
One of the hawk parameters for methods that return data must specified as the output parameter. Correct the configuration and restart the adapter.
|
|
|
|
|
|
Generic error applies to many different conditions that may cause RPC invocations to fail. The resolution is best determined by examining the specific error text in detail.
|
|
|
ERR_COMPONENT_HAWK_METHOD_OUTPUT_TYPE_MISMATCH
|
|
|
The description of the hawk method and the code disagree on the type of the output parameter. Correct one or the other to match.
|
|
|
|
|
|
|
|
|
ERR_COMPONENT_UNEXPECTED_COMPONENT
|
|
|
Pre-registration or unregistration of listeners requires the use of a publisher with the RVCM protocol. The specified publisher must be changed to RVCM.
|
|
|
ERR_METADDATA_DEPRECATED_METHOD
|
|
|
|
|
|
ERR_COMPONENT_UNSUPPORTED_FEATURE
|
|
|
|
|
|
ERR_PROPERTIES_CONNECTION_FAILED
|
|
|
|
|
|
ERR_COMPONENT_INCORRECT_USAGE
|
|
|
|
|
|
ERR_COMPONENT_UNKNOWN_PROTOCOL
|
|
|
|
|
|
ERR_METADATA_UNEXPECTED_CLASS
|
|
|
|
|
|
ERR_METADATA_OPERATION_ERROR
|
|
|
|
|
|
ERR_MARSHALLER_OPERATION_ERROR
|
|
|
Unable to pack or unpack. Check the wireformat protocol. The data may have been received from a non SDK application.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ERR_PROPERTIES_OPERATION_ERROR
|
|
|
|
|
|
ERR_METADATA_OUT_OF_RANGE_PRECISION
|
|
|
|
|
|
ERR_METADATA_OUT_OF_RANGE_SIZE
|
|
|
|
|
|
ERR_METADATA_OUT_OF_RANGE_INDEX
|
|
|
|
|
|
ERR_METADATA_OUT_OF_RANGE_START_LT_ZERO
|
|
|
|
|
|
ERR_METADATA_OUT_OF_RANGE_START_GT_LEN
|
|
|
|
|
|
ERR_METADATA_OUT_OF_RANGE_START_GT_END
|
|
|
|
|
|
ERR_METADATA_OUT_OF_RANGE_END_GT_LEN
|
|
|
|
|
|
ERR_METADATA_OUT_OF_RANGE_POS_LT_ZERO
|
|
|
|
|
|
|
|
|
|
|
|
ERR_PROPERTIES_INVALID_ASSOC_KEY
|
|
|
|
|
|
ERR_COMPONENT_ACTIVATE_ERROR
|
|
|
Check if the component has been created first , then check if the parameters passed are correct.
|
|
|
ERR_COMPONENT_OPERATION_ERROR_SESS_CREATION
|
|
|
|
|
|
ERR_COMPONENT_OPERATION_ERROR_SESS_INCOMPATIBLE
|
|
|
|
|
|
ERR_COMPONENT_OPERATION_ERROR_NOT_ACTIVATED
|
|
|
|
|
|
ERR_COMPONENT_OPERATION_ERROR_TIMEOUT
|
|
|
|
|
|
ERR_COMPONENT_OPERATION_UNSUPPORTED_OBJ_METHOD
|
|
|
|
|
|
ERR_COMPONENT_OPERATION_ERROR_TX_CTL_USED_UP
|
|
|
|
|
|
ERR_COMPONENT_OPERATION_ERROR_SINK_CREATE
|
|
|
|
|
|
ERR_PROPERTIES_INCORRECT_USAGE_NOT_SETTABLE
|
|
|
The attribute that is being modified is not settable. Try to make it settable using the repository or do not try to modify it.
|
|
|
ERR_PROPERTIES_INCORRECT_USAGE_NULL_REPO
|
|
|
|
|
|
ERR_RPC_OPERATION_NOT_FOUND_OP
|
|
|
Check if the correct parameter was passed, if the operation description is present.
|
|
|
|
|
|
|
|
Operation error: SAX parser not found. Either property org.xml.sax.parser'isnotdefinedorcom.microstar.xml.SAXDriverisnotinclasspath.'
|
ERR_XML_OPERATION_ERROR_PARSER_NOT_FOUND
|
|
|
|
|
|
|
|
|
|
|
|
ERR_MARSHALLER_DATA_ERROR_SER
|
|
|
|
|
|
ERR_MARSHALLER_DATA_ERROR_SER_BUF_SIZE_TOO_SMALL
|
|
|
|
|
|
ERR_MARSHALLER_DATA_ERROR_SER_TYPE_MISMATCH
|
|
|
|
|
|
|
|
|
|
|
|
ERR_COMPONENT_HAWK_PARAMETER_UNEXPECTED
|
|
|
|
|
|
ERR_COMPONENT_HAWK_PARAMETER_NOT_SPECIFIED
|
|
|
|
|
|
ERR_RPC_OPERATION_ERROR_NULL_EX
|
|
|
|
|
|
ERR_RPC_OPERATION_ERROR_NULL_VALUE
|
|
|
|
|
|
ERR_COMPONENT_HAWK_METHOD_NUM_OUTPUT_MISMATCH
|
|
|
|
|
|
ERR_RPC_INCORRECT_USAGE_INPUT_PARAMETER
|
|
|
|
|
|
ERR_RPC_INCORRECT_USAGE_UNASSIGNABLE
|
|
|
|
|
|
ERR_RPC_INCORRECT_USAGE_ONE_WAY
|
|
|
|
|
|
ERR_RPC_INCORRECT_USAGE_NOT_ONE_WAY
|
|
|
|
|
|
ERR_RPC_INCORRECT_USAGE_USER_IMPL
|
|
|
|
|
|
ERR_RPC_INCORRECT_USAGE_NOT_OUTPUT_PARAMETER
|
|
|
Check the repository for the parameter or check the parameter that been passed. It has to match.
|
|
|
ERR_METADATA_UNSUPPORTED_CLASS_ALONE
|
|
|
|
|
|
ERR_METADATA_INCORRECT_DEFINITION
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_LONG_NAME_EXPECTED
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_MIX
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_UNSUPPORTED
|
|
|
|
|
|
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_MULTI_MIN_GT_MAX
|
|
|
|
|
|
ERR_METADATA_UNION_MEMBER_NOT_FOUND
|
|
|
|
|
|
ERR_METADATA_ATTRIBUTE_NOT_FOUND
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_ATTRIB_READ_ONLY
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_NULL_ATTRIB
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_UNASSIGNABLE
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_IDX_NOT_NUMERIC
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_ATTRIB_LIST_READ_ONLY
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_OP_LIST_READ_ONLY
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_MEMBER_LIST_READ_ONLY
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_ILLEGAL_TOKEN
|
|
|
|
|
|
ERR_PROPERTIES_INCORRECT_USAGE_VALUE
|
|
|
|
|
|
ERR_RPC_INCORRECT_USAGE_ILLEGAL_PARAMETER
|
|
|
|
|
|
ERR_COMPONENT_HAWK_TYPE_UNEXPECTED
|
|
|
|
|
|
ERR_COMPONENT_NOT_HAWK_METHOD
|
|
|
|
|
|
|
|
|
|
|
|
ERR_COMPONENT_INCORRECT_USAGE_CONFIRM
|
|
|
Only CM messages can be confirmed. Do not use confirm on a non CM message.
|
|
|
ERR_COMPONENT_UNSUPPORTED_METHOD
|
|
|
|
|
|
|
|
|
|
|
|
ERR_CONFIG_INCORRECT_USAGE_UNSPECIFIED_URL
|
|
|
|
|
|
|
|
|
|
|
|
ERR_PROPERTIES_OPERATION_ERROR_URL_LOCKED
|
|
|
|
|
|
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_MULTI_MIN_LT_ZERO
|
|
|
|
|
|
ERR_METADATA_INCORRECT_USAGE_MULTI_MAX_LT_ZERO
|
|
|
|
|
|
ERR_COMPONENT_INCORRECT_USAGE_CUSTOM_DB
|
|
|
Make sure that a custom database handle is not passed. Adapter SDK does not handle it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ensure with your Admin that you have sufficient Access rights to perform the operation.
|
|
|
|
|
|
|
|
|
|
|
|
This error occurs when any of the adapter properties on the command line ( -system:tibco.clientVar.myVariable=), in the properties or the .tra file used by the adapter is empty. To fix this either delete or omit the variable or set the variable value to the default value " ;".
|
|
|
|
|
|
When a property file could not be read by adapter, this error is thrown. Check whether the property file exists and has proper file permission.
|
|
|
|
|
|
When you send a request without a reply subject, the adapter does not consider the sent message as a request and throws an error. Make sure that you send the message with a reply subject.
|
|
|
|
|
|
An error was reported by the JMS layer. Please refer to the relevant documentation for details
|
|
|
ERR_USAGE_UNSUPPORTED_TRANSPORT
|
|
|
This method is not currently supported for the specified transport. Use a transport that is supported for this method.
|
|
|
M_ERR_USAGE_INVALID_COMMANDLINE
|
|
|
|
|
Invalid message format, valid values (MMessageFormat.RV,MMessageFormat.AERV,MMessageFormat.XMLJMS,MMessageFormat.XMLRV)
|
M_ERR_USAGE_INVALID_MESSAGEFORMAT
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Check that there is a JMS session is available. If the application is not intended to use JMS, use the correct message transport.
|