|
|
|
|
|
|
|
M_ERR_METADATA_DESERIALIZATION_ERROR
|
|
|
|
|
|
|
|
|
Deserialization was attempted on an MTree that does not contain necessary metadata prefix list information. Either correct the sending application or do not attempt to deserialize this Mtree (it may not have been packed by an SDK-based application).
|
|
|
M_ERR_CONFIG_REPOSITORY_CONNECTION
|
|
|
If using a local repository, the file is not present, or corrupted. If connecting to a remote repository, ensure the repoURL is correct and the repository server is running.
|
|
|
M_ERR_CONFIG_REPOSITORY_GET_DOCUMENT
|
|
|
Confirm that the specified document exists in the repository instance being used.
|
|
|
M_ERR_CONFIG_REPOSITORY_CREATE_DOCUMENT
|
|
|
Confirm that the user and password used to launch the adapter has write permissions on the repository.
|
|
|
M_ERR_CONFIG_REPOSITORY_UPDATE_DOCUMENT
|
|
|
Confirm that the user and password used to launch the adapter has write permissions on the repository.
|
|
|
M_ERR_CONFIG_REPOSITORY_COMMIT
|
|
|
Confirm that the user and password used to launch the adapter has write permissions on the repository.
|
|
|
M_ERR_CONFIG_REPOSITORY_ROLLBACK
|
|
|
Re-attempt to commit. If subsequent attempts fail, confirm that the repository instance is running normally.
|
|
|
M_ERR_CONFIG_REPOSITORY_GENERAL
|
|
|
|
|
|
M_ERR_CONFIG_REPOSITORY_CONNECTION_UNAVAILABLE
|
|
|
A remote repository instance has likely gone down. Confirm the state of the repository and restart if necessary.
|
|
|
M_ERR_CONFIG_MISSING_DOC_NAME_TAG
|
|
|
The name of the adapter configuration object pointed to does not match the AppName set in the code. Change one or the other to match and restart the adapter.
|
|
|
M_ERR_CONFIG_MISSING_HAWK_SESSION_INFORMATION
|
|
|
Supply the missing configuration attribute and restart the adapter.
|
|
|
M_ERR_CONFIG_MISSING_MANDATORY_ATTRIBUTE
|
|
|
Supply the missing configuration attribute and restart the adapter.
|
|
|
M_ERR_CONFIG_NO_DEFAULT_SESSION
|
|
|
|
|
|
M_ERR_CONFIG_UNKNOWN_DEFAULT_SESSION
|
|
|
The specified default session does not exist or is invalid. Correct the configuration and restart the adapter.
|
|
|
|
|
|
Change the attribute value to one of the acceptable values and restart the adapter.
|
|
|
M_ERR_CONFIG_ATTRIBUTE_VALUE_LESS_THAN_1
|
|
|
|
|
|
M_ERR_CONFIG_INVALID_FOR_ONEWAY_OPERATION
|
|
|
Most likely, an inout parameter type has been specified for a oneway operation. Returning a value for a oneway operation is not permitted. Correct the configuration and restart the adapter.
|
|
|
|
|
|
Obsolete - An XML file based configuration is missing the file name.
|
|
|
M_ERR_CONFIG_DUPLICATE_HAWK_MICRO_AGENT
|
|
|
Remove the duplicate hawk micro agent from configuration and restart the adapter.
|
|
|
M_ERR_CONFIG_DUPLICATE_HAWK_METHOD
|
|
|
|
|
|
M_ERR_CONFIG_INCORRECT_HAWK_PARAMETER_TYPE
|
|
|
|
|
|
M_ERR_CONFIG_INCORRECT_ATTRIBUTE_CLASS
|
|
|
|
|
|
M_ERR_CONFIG_INCORRECT_ROOT_ELEMENT_NAME
|
|
|
The Adapter configuration object and the appName in code must match. Change one to match and restart the adapter.
|
|
|
|
|
|
Confirm that the configURL being used is correct. A common error is an absolute path that does not start with "/tibco/adapter/private".
|
|
|
|
|
|
|
|
|
|
|
|
Either the element name was incorrect or it does not exist in the XML document being parsed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Either the file does not exist or the user does not have permission to open the file.
|
|
|
|
|
|
|
|
|
|
|
|
The XML engine initialization routines failed due to an unspecified exception. If the problem persists, contact TIBCO Support.
|
|
|
|
|
|
The underlying TIBCO Rendezvous layer is reporting an error condition. Please see the corresponding documentation for details.
|
|
|
|
|
|
The underlying TIBCO Rendezvous TX layer is reporting an error condition. Please see the corresponding documentation for details.
|
|
|
|
|
|
The underlying TIBCO Rendezvous TX does not permit this operation. An example would be to commit the same transaction twice. Please see the corresponding documentation for details.
|
|
|
M_ERR_RVTX_FUNCTION_SYMBOL_NOT_LOADED
|
|
|
The dynamic fetch layer for the tibrvtx shared library is unable to load this method from the shared library. Confirm that the appropriate version of TIBCO Rendezvous TX is installed.
|
|
|
|
|
|
The dynamic fetch layer is unable to load the tibrvtx shared library. Confirm that TIBCO Rendezvous TX is installed and that the corresponding environment variables are set correctly.
|
|
|
|
|
|
|
|
|
M_ERR_USAGE_DUPLICATE_SINK_OBJECT
|
|
|
Do not attempt to insert a sink twice or insert a sink with the same name as an existing one.
|
|
|
M_ERR_USAGE_DUPLICATE_COMPONENT_OBJECT
|
|
|
All component names must be unique within a given MComponentRegistry. Rename the MComponent subclass instance in question and retry (e.g., MPublisher, MSubscriber, ...).
|
|
|
M_ERR_USAGE_DUPLICATE_CLASS_DESCRIPTION_OBJECT
|
|
|
All class description names in a given MClassRegistry instance must be unique.
|
|
|
M_ERR_USAGE_UNSPECIFIED_PARAMETER
|
|
|
This parameter must be set before calling this method. For strings, this means "" is not acceptable.
|
|
|
M_ERR_USAGE_HAWK_METHOD_DESCRIPTION_UNSPECIFIED
|
|
|
Specify a description for this hawk method in configuration and restart the adapter.
|
|
|
M_ERR_USAGE_HAWK_PARAMETER_BAD_DATA_TYPE
|
|
|
Change the configuration to specify only supported data types for parameters and restart the adapter.
|
|
|
M_ERR_USAGE_DUPLICATE_OPERATION
|
|
|
This operation class has already been defined in the metadata loaded by this adapter configuration. Eliminate one or the other, or rename this operation class to remove the conflict and restart the adapter.
|
|
|
M_ERR_USAGE_CLASS_DESCRIPTION_NOT_AVAILABLE
|
|
|
The specified class does not exist in the class registry. Check the loadURL section in configuration and/or confirm that the specified class is supposed to be used with this adapter.
|
|
|
M_ERR_USAGE_MISSING_CLASS_ATTRIBUTE
|
|
|
Do not attempt to use (set/get) an attribute that does not exist for a given class. Either the class description is incorrect and the attribute should be added to the class in question, or the is being attempted on the wrong class.
|
|
|
M_ERR_USAGE_CLASS_DESCRIPTION_ATTRIBUTE_TYPE_MISMATCH
|
|
|
Do not attempt to set an attribute with a type that does not match the metadata. For example, is the metadata type is "string", setting that attribute with an MInteger will result in this error.
|
|
|
M_ERR_USAGE_MISSING_CLASS_RELATION
|
|
|
Do not attempt to check relations on classes that do not have them. This can happen when calling isRelationValid() and passing a bad string.
|
|
|
M_ERR_USAGE_UNSUPPORTED_TRANSPORT_PROTOCOL
|
|
|
Confirm with the documentation that the transport protocol passed is supported in this particular component.
|
|
|
M_ERR_USAGE_RVCM_NOT_ENABLED
|
|
|
Do not attempt to mismatch an RVCM endpoint with an RV session. All RVCM endpoints must be matched with RVCM sessions.
|
|
|
M_ERR_USAGE_RVCMQ_NOT_ENABLED
|
|
|
Do not attempt to mismatch an RVCMQ endpoint with anything other than an RVCMQ session.
|
|
|
M_ERR_USAGE_RVTX_NOT_ENABLED
|
|
|
Do not attempt to mismatch an RVTX endpoint with anything other than an RVTX session. Also, do not attempt to invoke RVTX-specific methods with a non-RVTX endpoint.
|
|
|
|
|
|
Confirm that the specified session name string corresponds to a session in the MComponentRegistry. Both the configuration and code must match.
|
|
|
M_ERR_USAGE_NOT_A_HAWK_MICRO_AGENT
|
|
|
|
|
|
M_ERR_USAGE_CLASS_RELATION_NO_KEY_VALUE
|
|
|
A nonexistent key was passed to the isKeyValid() method. Either the code or the metadata configuration should be modified to match.
|
|
|
M_ERR_USAGE_CLASS_RELATION_KEY_NOT_EQUAL
|
|
|
This is effectively saying that the key passed to isKeyValid() is not valid. It indicates that the keys do not match. Since this method returns void, it indicates the result by throwing exceptions.
|
|
|
M_ERR_USAGE_CLASS_RELATION_KEY_DEF_MISMATCH
|
|
|
This is effectively saying that the key sets do not match when calling MInstance::isKeyValid() and passing an MSequence. Since this method returns void, it indicates the result by throwing exceptions.
|
|
|
M_ERR_USAGE_UNSUPPORTED_CONSTRUCTOR
|
|
|
|
|
|
M_ERR_USAGE_UNSUPPORTED_OPERATION
|
|
|
|
|
|
|
|
|
This deprecated method is not allowed under these circumstances. Refer to the documentation for details on migrating away from deprecated methods.
|
|
|
M_ERR_USAGE_CLASS_DESCRIPTION_VALIDATION_FAILED
|
|
|
One of the restricted MData subclass types had an internal constraint violated. For example, attempting to set a restricted sized binary with data exceeding the stated capacity.
|
|
|
M_ERR_USAGE_BUSINESS_DOCUMENT_NOT_DEFINED
|
|
|
The repository instance being used is missing baseBusinessDocument information. In this case, either refrain from using MBusinessDocument objects, or add the appropriate metadata to the repository instance being used.
|
|
|
M_ERR_USAGE_ADVISORY_DOCUMENT_NOT_DEFINED
|
|
|
The repository instance being used is missing baseAdvisoryDocument information. In this case, either refrain from using MAdvisoryDocument objects, or add the appropriate metadata to the repository instance being used.
|
|
|
M_ERR_USAGE_SEQUENCE_FOR_BUSINESS_DOCUMENT_NOT_DEFINED
|
|
|
The repository instance being used is missing baseBusinessDocument information. In this case, either refrain from using MBusinessDocument objects, or add the appropriate metadata to the repository instance being used.
|
|
|
M_ERR_USAGE_INVALID_FOR_ONEWAY_OPERATION
|
|
|
Certain method and configuration combinations are prohibited. In this case, a oneway invocation has been specified in configuration, and an asyncInvoke() method call is attempted.
|
|
|
M_ERR_USAGE_INVALID_FOR_TWOWAY_OPERATION
|
|
|
Certain method and configuration combinations are prohibited. In this case, a two-way invocation has been specified in configuration, and a onewayInvoke() method call is attempted.
|
|
|
M_ERR_USAGE_OPERATION_PENDING
|
|
|
An attempt to call asyncInvoke() was made before an existing call to asyncInvoke() completed.
|
|
|
M_ERR_USAGE_OPERATION_DESCRIPTION_NOT_AVAILABLE
|
|
|
|
|
|
M_ERR_INTERNAL_ADDING_COMPONENT
|
|
|
Make sure the component does not already exist , and there is a valid component registry.
|
|
|
M_ERR_INTERNAL_REPLY_PUBLISHER_CREATION_FAILED
|
|
|
|
|
|
M_ERR_INTERNAL_MISSING_HAWK_MICRO_AGENT
|
|
|
Specify all microagent names correctly. Make sure the count (total number of microagents) is specified correctly.
|
|
|
M_ERR_INTERNAL_UNEXPECTED_DATA_TYPE
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
M_ERR_TIMER_DOUBLE_ACTIVATION
|
|
|
|
|
|
M_ERR_TRACE_SINK_FILE_OPEN_ERROR
|
|
|
Confirm that the location of the file is correct , make sure that it is not protected.
|
|
|
M_ERR_TRACE_SINK_FILE_SIZE_CHECK_ERROR
|
|
|
|
|
|
M_ERR_TRACE_SINK_FILE_WRITE_ERROR
|
|
|
If a file sink is used ensure that its location is correct and not protected.
|
|
|
M_ERR_WIRE_PROTOCOL_PACKING_ERROR
|
|
|
Confirm that a valid Wire format is specified, make sure that the data that has to be packed is valid.
|
|
|
M_ERR_WIRE_PROTOCOL_UNPACKING_ERROR
|
|
|
Confirm that a valid Wire format is specified. The message might not have been received from another SDK application.
|
|
|
M_ERR_DATA_EMPTY_NODE_PARAMETER
|
|
|
While appending a node to the tree make sure that node to be appended is not empty.
|
|
|
|
|
|
|
|
|
|
|
|
Make sure that the parameter value supplied is valid and matches the type of data.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
M_ERR_UNICODE_CONVERSION_TO_UNICODE
|
|
|
|
|
|
M_ERR_OPERATION_BADREPLY_UNEXPECTED
|
|
|
Make sure that the server has sent the message correctly and make the parameters or the operation is specified properly.
|
|
|
|
|
|
|
|
|
M_ERR_OPERATION_NO_ONEWAY_IMPL
|
|
|
Confirm that there is an implementation of onOneWayInvoke function in the application code.
|
|
|
M_ERR_OPERATION_NO_TWOWAY_IMPL
|
|
|
Confirm that there is an implementation of onInvoke function in the application code.
|
|
|
|
|
|
Make sure that the parameter for the operation has been specified properly.
|
|
|
|
|
|
Increase the time limit for the timeout and make sure the subscriber and server is up and running.
|
|
|
M_ERR_OPERATION_PROXY_NOT_FOUND
|
|
|
|
|
|
|
|
|
Confirm that the plugin name and its location has been specified properly.
|
|
|
|
|
|
|
|
|
|
|
|
This occurs when the address of the function CreateNewPlugin cannot be found on the plugin. Make sure this function is present.
|
|
|
|
|
|
Make sure that the plugin name and its location has been properly specified in command line arguments.
|
|
|
M_ERR_STRING_CANNOT_INITIALIZE
|
|
|
The string could not be initialized. Make sure that the offset lies beyond the end of source string while creating an MWString or MString.
|
|
|
|
|
|
An invalid operation was attempted on Mlist. Make sure that the usage on MList is correct.
|
|
|
|
|
|
|
|
|
|
|
|
Confirm that the operation done on MVector lies within its boundary.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
M_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_CONN_FACTORY
|
|
|
|
|
|
|
|
|
The underlying JMS layer is reporting an error condition. See the TIBCO Enterprise Message Service documentation for details.
|
|
|
M_ERR_USAGE_INVALID_DESTINATION_TYPE
|
|
|
|
|
|
M_ERR_USAGE_INVALID_ENDPOINTSPEC
|
|
|
|
|
|
M_ERR_USAGE_INVALID_COMMANDLINE
|
|
|
|
|
Invalid message format, valid values (M_RV_MESSAGE_FORMAT,M_AERV_MESSAGE_FORMAT,M_XMLJMS_MESSAGE_FORMAT,M_XMLRV_MESSAGE_FORMAT)
|
M_ERR_USAGE_INVALID_MESSAGEFORMAT
|
|
|
|
|
|
|
|
|
The dynamic fetch layer is unable to load the tibjms shared library. Confirm that TIBCO Enterprise Message Service software is installed and that the corresponding environment variables are set correctly.
|
|
|
M_ERR_USAGE_INVALID_SESSION_TYPE
|
|
|
Only an MJmsSession object can be passed to JMS endpoint constructors.
|
|
|
|
|
|
A system level error occurred while creating or running the dispatcher thread. Check if enough memory is available and if the parameter passed is correct.
|
|
|
|
|
|
The wrong object has been passed. Only an MAdvisoryListener object can be passed.
|
|
|
|
|
|
|