Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems
identified.
See Also: A pointer to related information (not specified
for all messages).
The Oracle Tuxedo System Messages are numbered and organized in
catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are
generated. For information about a specific message, click on the name of the
appropriate catalog.
Note: Some messages for deprecated features may still
display. Be aware that deprecated features are not supported.
mio received an unsolicited message (tpbroadcast or tpnotify) and it could not determine the buffer type for processing. The indicated BEA TUXEDO system error tperrno is the returned error indication from the ATMI routine tptypes().
Action
The most likely cause of this error is a non-BEA TUXEDO system process sending messages via UNIX; queues and mistakenly putting one such message on mio's queue. Examine other operations on your system to ensure that this is not occurring. Additionally, check permissions specified in your UBBCONFIG file to allow write access only as necessary. If the problem cannot be resolved, then please contact your BEA TUXEDO system Technical Support.
WARN: Invalid unsolicited message buffer type type
Description
mio received an unsolicited message (tpbroadcast or tpnotify) with an unsupported buffer type. mio supports unsolicited messages with either the FML or STRING buffer type only. The indicated message will be ignored and mio will continue processing.
Action
Check application clients and servers that send unsolicited messages to see what buffer types are being used. Correct improper uses to use only FML or STRING buffer types when communicating with what may be an mio client.