Messages
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.
300 |
ERROR: Cannot expand object info table | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
301 |
ERROR: Cannot allocate reply input stream | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
302 |
ERROR: Cannot preserve input buffer | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
303 |
ERROR: Cannot register service val: val | |
|
Description |
An error occurred while attempting to register the specified service to the Jolt registry. |
Action |
Contact BEA Customer Support. | |
304 |
ERROR: Cannot advertise service val: val | |
|
Description |
An error occurred while attempting to advertise the specified service. |
Action |
Contact BEA Customer Support. | |
305 |
ERROR: Cannot unadvertise service val: val | |
|
Description |
An error occurred while attempting to unadvertise the specified service. |
Action |
Contact BEA Customer Support. | |
306 |
ERROR: tptypes() failed: val | |
|
Description |
An error occurred while attempting to get the buffer type from the message header in the Tuxedo-to-Jolt buffer conversion. |
Action |
Contact BEA Customer Support. | |
307 |
ERROR: Jolt protocol error (msg len=val) | |
|
Description |
An error occurred while attempting to construct a Jolt protocol object. |
Action |
Contact BEA Customer Support. | |
308 |
ERROR: Missing REPNAME param in the protocol | |
|
Description |
The service name was missing in the Jolt protocol object while attempting to convert the Jolt protocol to ATMI. |
Action |
Contact BEA Customer Support. | |
309 |
ERROR: Unsupported Jolt opcode val | |
|
Description |
An invalid opcode in the Jolt protocol object was found while attempting to convert the Jolt protocol to ATMI. |
Action |
Contact BEA Customer Support. | |
310 |
ERROR: Invalid opcode val in Tuxedo to Jolt conversion | |
|
Description |
An invalid Jolt opcode was found while attempting to convert ATMI results to the Jolt protocol. |
Action |
Contact BEA Customer Support. | |
311 |
ERROR: Cannot allocate val bytes for CARRAY | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
312 |
ERROR: tpalloc(val,val) failed: val | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
313 |
ERROR: tpalloc(val,val) failed: val | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
314 |
ERROR: Not enough memory: data is dropped | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and for the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
315 |
ERROR: Out of memory | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine, or increase the amount of physical memory on the machine. | |
316 |
ERROR: Sending reply with outstanding async replies | |
|
Description |
A method completed with outstanding message replies. |
Action |
Check the method code and make sure that it does not complete before all
the | |
317 |
WARN: Sending reply failed because of subordinate conversations open | |
|
Description |
A method that created ATMI conversations via JNI completed in an invalid conversational context. The method code failed to successfully end all conversations it had initiated before completing. |
Action |
Modify the application logic so that the method ends all conversations it started before completing. | |
See Also |
| |
318 |
INFO: val jar management in effect | |
|
Description |
JAR management is in effect. |
Action |
No action required. | |
325 |
WARN: xa_start() failed in pre-prepare phase with error = err | |
|
Description |
This is a warning message to indicate that an attempt by the WLE infrastructure to
call |
Action |
None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG. |