IJINFRA Messages 0-99
|
|
2
INFO: Starting JVM
Description
This is an informational message indicating that the server process is starting the Java Virtual Machine.
Action
None.
3
ERROR: Cannot create FML buffer for TMIB request
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.
4
ERROR: Cannot call .TMIB: errnum
Description
The server process was unable to call the TMIB. Details about the error that was returned are indicated by errnum.
Action
Take corrective action based on the returned value of errnum. If the problem persists, contact BEA Customer Support.
5
ERROR: Cannot find default constructor for ServerInfo
Description
The server process was unable to find the default constructor for the ServerInfo class.
Action
Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.
6
ERROR: Cannot create ServerInfo object
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.
7
WARN: No server group info
Description
The server process was unable to get any information about the server group.
Action
None. This may result in a more serious error, and a corresponding error message would be written to the user log.
8
ERROR: Cannot find m_srvgp field in ServerInfo
Description
The server process was unable to find the m_srvgp field in the ServerInfo class.
Action
Contact BEA Customer Support.
9
ERROR: Cannot find m_srvid field in ServerInfo
Description
The server process was unable to find the m_srvid field in the ServerInfo class.
Action
Contact BEA Customer Support.
10
WARN: No server ID info
Description
The server process was unable to get any information about the server ID.
Action
None. This may result in a more serious error, and a corresponding error message would be written to the user log.
11
ERROR: Cannot find m_grpno field in ServerInfo
Description
The server process was unable to find the m_grpno field in the ServerInfo class.
Action
Contact BEA Customer Support.
12
WARN: No group number info
Description
The server process was unable to get any information about the group number.
Action
None. This may result in a more serious error, and a corresponding error message would be written to the user log.
13
WARN: No CLOPT info
Description
The server process could not find any command line option information.
Action
None. This may result in a more serious error, and a corresponding error message would be written to the user log.
14
ERROR: Cannot find m_clopt field in ServerInfo
Description
The server process was unable to find the m_cltop field in the ServerInfo class.
Action
Contact BEA Customer Support.
16
ERROR: Cannot allocate reply 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 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.
17
ERROR: Reply failed with error: errnum
Description
An attempt by the process to receive a reply failed. errnum provides details of the error returned by the system.
Action
Take corrective action based on the value of errnum returned. If the problem persists, contact BEA Customer Support.
18
ERROR: Reply length is zero
Description
An attempt by the process to receive a reply failed because the length of the receiving buffer was zero.
Action
Contact BEA Customer Support.
19
ERROR: Out of memory. Cannot allocate space for internal data structure
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.
20
ERROR: Unable to resolve in process or out process method invocation
Description
The process was unable to determine if a particular request was an in process or an out process invocation. The request fails.
Action
Contact BEA Customer Support.
21
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.
33
ERROR: Cannot allocate FML buffer for TMIB call
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.
34
ERROR: Cannot access TMIB: errnum
Description
The server process was unable to access the TMIB. Details about the error that was returned is indicated by errnum.
Action
Take corrective action based on the returned value of errnum. If the problem persists, contact BEA Customer Support.
35
ERROR: Unable to attach BB
Description
This message occurs in the server process if the server process was configured in the PROTECTED SYSTEM_ACCESS mode, and the process is unable to attach itself to the Bulletin Board.
Action
Contact BEA Customer Support.
36
ERROR: Unable to lock BB and detach previous BB
Description
This message occurs in the server process if the server process was configured in the PROTECTED SYSTEM_ACCESS mode, and the process is unable to lock and later detach itself from the Bulletin Board.
Action
Contact BEA Customer Support.
37
ERROR: Unable to lock BB
Description
This message occurs in the server process if the server process was unable to lock the Bulletin Board.
Action
Contact BEA Customer Support.
38
ERROR: Unable to detach BB
Description
This message occurs in the server process if the server process was configured in the PROTECTED SYSTEM_ACCESS mode, and the process is unable to detach itself from the Bulletin Board.
Action
Contact BEA Customer Support.
40
ERROR: Cannot execute prog_nam
Description
The buildXAJS command was unable to execute the buildserver command. The name of the command being executed is given as part of the error message.
Action
If you are compiling executables to run on the same machine type, as is normally the case, verify that the TUXDIR shell variable is properly set, that the program ${TUXDIR}/bin/buildserver exists, is accessible and executable, and that the shell variable XCBINDIR is not set. If you are compiling executables for a different machine type, verify that the shell variable XCBINDIR is set and exported, and that the program ${XCBINIDIR}/buildserver exists and is accessible and executable.
42
ERROR: Missing argument to -M option
Description
The server process will not boot because no argument has been passed on the command line to the -M option.
Action
Make the appropriate changes in the UBBCONFIG file and reboot.
43
ERROR: Missing argument to -classpath option
Description
The server process will not boot because no argument has been passed on the command line to the -classpath option.
Action
Make the appropriate changes in the UBBCONFIG file and reboot.
44
ERROR: Cannot create debugging pipe: errnum
Description
The server process will not boot because it could not create a debugging pipe. Details about the error that was returned is specified by errnum.
Action
Take corrective action based on the value of errnum. If the problem persists, contact BEA Customer Support.
45
ERROR: Cannot reopen stdout for debugging info: errnum
Description
The server process will not boot because it cannot reopen stdout for debugging information. Details about the error that was returned is specified by errnum.
Action
Take corrective action based on the value of errnum. If the problem persists, contact BEA Customer Support.
46
ERROR: Cannot create Java VM
Description
The server process will not boot because it could not create the Java Virtual Machine.
Action
Contact BEA Customer Support.
47
ERROR: No agent password info
Description
The server process will not boot because it could not retrieve the agent password information.
Action
Contact BEA Customer Support.
48
INFO: Debug password buffer: buf
Description
This is an informational message with the debug password buffer specified in buf.
Action
None.
58
ERROR: Cannot create Java VM
Description
Execution of buildjavaserver failed because the process was unable to create the Java Virtual Machine.
Action
Contact BEA Customer Support.
59
ERROR: Cannot find classname class
Description
While executing buildjavaserver, the process was unable to find the class specified in classname.
Action
Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.
60
ERROR: Cannot find buildjobjserver.main
Description
While executing buildjavaserver, the process was unable to find the main() method in the class com.beasys.Tobj.xml.buildjavaserver.
Action
Contact BEA Customer Support.
65
INFO: Server initialized
Description
This is an informational message indicating that the server process has successfully initialized and is now ready to process incoming requests.
Action
None.
66
ERROR: Server initialization failed
Description
The server process initialization has failed because of an internal error.
Action
Contact BEA Customer Support.
70
INFO: Shutting down JVM
Description
This is an informational message indicating that the server process is shutting down the Java Virtual Machine.
Action
Contact BEA Customer Support.
73
WARN: pattern not found in file
Description
This is a warning message that is output while executing m3idttojava if an expected pattern (specified by pattern) is not found in the file (specified by file).
Action
None. This may result in a more serious error and a corresponding error message being written to the user log.
74
INFO: command: PostProcessing: writing file 'file'
Description
This is an informational message that is output while executing the command specified by command. file gives the name of the file being written to during the postprocessing phase.
Action
None.
75
ERROR: Cannot open file: error
Description
While executing m3idttojava, the process was unable to open the file specified by file. error indicates the error returned by the system while attempting to open that file.
Action
Take corrective action based on the error returned.
76
ERROR: Cannot create temp file: error
Description
While executing m3idttojava, the process was unable to create a temporary file. error indicates the error returned by the system while attempting to create that file.
Action
Take corrective action based on the error returned.
77
ERROR: Invalid ImplBase file file
Description
While executing m3idttojava, an invalid ImplBase file was specified. The name of that file is specified by file.
Action
Contact BEA Customer Support.
78
ERROR: Cannot create new file: error
Description
While executing m3idttojava, the process was unable to create a new file specified by file. error indicates the error returned by the system while attempting to create that file.
Action
Take corrective action based on the error returned.
79
ERROR: command: idltojava option 'option' not supported
Description
This error message is output while executing the command (specified by command) if an unsupported idltojava option is specified. option gives details of the option specified.
Action
Do not use the corresponding option. It is not supported.
80
ERROR: command: Out of memory
Description
An attempt to allocate space for internal data structures failed because the process ran out of memory while executing the command (specified by command).
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.
81
ERROR: command: Cannot execute sub-command: error
Description
While executing the command (specified by command), the process was unable to execute a sub-command (specified by sub-command). error gives details of the error returned by the system.
Action
Take corrective action based on the error returned.
82
ERROR: Cannot access file file in APPDIR appdir
Description
The server process will not boot because it cannot access the jar file specified by file in the APPDIR specified by appdir.
Action
Make sure the jar file exists in APPDIR and that the file can be accessed.
83
ERROR: Cannot copy request message
Description
The request cannot be processed by the server because the request message cannot be copied.
Action
Notify BEA Technical Support.
84
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.
86
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.
91
ERROR: Cannot create registry table entry for context
Description
An attempt to create a registry table entry for the new context failed.
Action
Either increase the value of the MAXACCESSERS parameter in the UBBCONFIG file, or reduce the number of concurrent client requests. In the WLE Server Threading architecture, each outstanding request is associated with its own BEA TUXEDO context, which in turns requires its own registry table entry. The MAXACCESSERS parameter in the UBBCONFIG file tells the BEA TUXEDO system how many registry table entries to be reserved. If the problem persists, notify BEA Technical Support.
92
ERROR: Context initialization failed
Description
An attempt to initialize the server context failed.
Action
This could be due to no more server contexts being available, insufficient memory, or a problem creating a registry table entry for the server contexts. A detailed error message should be written to the user log. Take corrective action based on the error message. If the problem persists, notify BEA Technical Support.
93
ERROR: Failed to allocate context
Description
An attempt to allocate the server context failed.
Action
This could be due to no more server contexts being available, insufficient memory, or a problem creating a registry table entry for the server contexts. A detailed error message should be written to the user log. Take corrective action based on the error message. If the problem persists, notify BEA Technical Support.
 |
 |
 |