Table 2-4 Tobj_Events Exception Minor Codes
Exception Symbols
|
Definitions
|
Minor Codes (Hexadecimal)
|
CORBA::IMP_LIMIT Exceptions
|
Tobj_Events:: POST_DOMAIN_AND_TYPE_TOO_LONG
This exception is raised by:
|
When posting an event, the user specified a domain name and type name whose combined length was greater than 31 characters.
|
5455580D
|
Tobj_Events:: POST_DOMAIN_CONTAINS_SEPARATOR
This exception is raised by:
|
When posting an event, the user specified a domain name that contained the "." character.
|
54555802
|
Tobj_Events::POST_EMPTY_DOMAIN
This exception is raised by:
|
When posting an event, the user specified an empty domain name.
|
5455580B
|
Tobj_Events::POST_EMPTY_TYPE
This exception is raised by:
|
When posting an event, the user specified an empty type name.
|
5455580C
|
Tobj_Events:: POST_SYSTEM_EVENTS_UNSUPPORTED
This exception is raised by:
|
When posting an event, the user tried to post a BEA Tuxedo system event; that is, the domain name is "TMEVT" and the type name starts with the "." character.
|
54555804
|
Tobj_Events:: POST_TYPE_CONTAINS_SEPARATOR
This exception is raised by:
|
When posting an event, the user specified a type name that contained the "." character.
|
54555803
|
Tobj_Events:: POST_UNSUPPORTED_PRIORITY_VALUE
This is exception is raised by:
|
When posting an event, the user added a "Priority" field in the variable header. However, the user did not set the field's value to a "short" in the range of 1-100.
|
54555801
|
Tobj_Events:: POST_UNSUPPORTED_VALUE_IN_ANY
This exception is raised by:
|
When posting an event, the user put an unsupported type (for example, a structure, union, sequence, etc.) into one of the "anys" in the structured event field. The unsupported type is in the variable header's value field, the filterable data's value field, or the remainder_of_body field.
|
54555800
|
Tobj_Events:: SUB_DOMAIN_AND_TYPE_TOO_LONG
This exception is raised by:
|
When subscribing, the user specified a domain name and type name whose combined length is greater than 255 characters.
|
54555809
|
Tobj_Events:: SUB_DOMAIN_BEGINS_WITH_SYSEV
This exception is raised by:
|
When subscribing, the user specified a domain name that begins with the "." character.
|
54555805
|
Tobj_Events::SUB_EMPTY_DOMAIN
This exception is raised by:
|
The user specified an empty domain name when subscribing.
|
54555807
|
Tobj_Events::SUB_EMPTY_TYPE
This exception is raised by:
|
The user specified an empty type name when subscribing.
|
54555808
|
Tobj_Events::SUB_FILTER_TOO_LONG
This exception is raised by:
|
The user specified a data filter expression longer than 255 characters.
|
5455580A
|
Tobj_Events::SUB_NAME_TO_LONG
This exception is raised by:
|
When subscribing, the user specified a subscription name longer than 127 characters.
|
5455580E
|
Tobj_Events:: TRANSIENT_ONLY_CONFIGURATION
This exception is raised by:
|
The user tried to create a persistent subscription, but the system was configured to support transient subscriptions only.
|
54555806
|
CORBA::BAD_PARAM Exceptions
|
|
|
Tobj_Events::INVALID_CHANNEL_ID
This exception is raised by:
|
When looking up the channel using the Simple Events API, the user specified an invalid channel ID, that is, a channel ID that is not Tobj_SimpleEvents:: DEFAULT_CHANNEL .
|
54555813
|
Tobj_Events:: INVALID_SUBSCRIPTION_ID
This exception is raised by:
|
When unsubscribing using the Simple Events API, the user specified an invalid subscription ID, that is, a non-existent or a CosNotification subscription ID.
When looking up a subscription using the CosNotification Service API, the user specified an invalid subscription ID, that is, a non-existent or a Simple Events API subscription ID.
When calling the exists operation using the BEA Simple Events API, the user passed in a CosNotification subscription_id .
|
54555812
|
Tobj_Events:: SUB_INVALID_FILTER_EXPRESSION
This exception is raised by:
|
When subscribing, the user specified an invalid data filter expression. This either means that there is a syntax error in the expression or that one of the field names in the expression is not defined as an FML field.
Check that you have correctly created FML field tables that contain all fields that you want to data filter on, and check that the UBBCONFIG file is properly configured so that the field table files can be found.
|
54555810
|
Tobj_Events:: SUB_UNSUPPORTED_QOS_VALUE
This exception is raised by:
|
54555811
When subscribing, the user specified an invalid subscription quality of service.
For the Simple Events API, this means that the quality of service specified did not meet one of the following requirements:
For the CosNotification Service API, this means that the quality of service specified did not meet one of the following requirements:
|
CORBA::INV_OBHJREF
|
Tobj_Events:: SUB_NIL_CALLBACK_REF
This exception is raised by:
|
When subscribing, the user specified a NIL object reference for the callback object which receives events.
|
54555830
|