Java Server-side Infrastructure Messages

Java Server-Side Infrastructure Messages 1-119

Note: When Java server-side messages are listed in the user log (ULOG), the messages have the prefix IJINFRA_CAT. For example, message 1 is listed as IJINFRA_CAT:1.

1	"ERROR: Cannot allocate request 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.

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.

15	"ERROR: Request failed with error: errnum"
	Description	An attempt by the process to make a request 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.

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\n"
	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.

22	"ERROR: Interface interfaceName not found: errnum"
	Description	The system was not able to get information about the interface specified by interfaceName. Details of the error returned are provided in errnum.
	Action	Take corrective action based on the value of errnum returned. If the problem persists, contact BEA Customer Support.

23	"ERROR: Cannot find org.omg.CORBA.INTERNAL class"
	Description	The server process was unable to find the org.omg.CORBA.INTERNAL class.
	Action	Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.

24	"ERROR: Cannot find com.beasys.CORBA.tgiop.tmintfinfo class"
	Description	The server process was unable to find the com.beasys.CORBA.tgiop.tmintfinfo class.
	Action	Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.

25	"ERROR: Cannot find default constructor for tmintfinfo"
	Description	The server process was unable to find the default constructor for com.beasys.CORBA.tgiop.tmintfinfo class.
	Action	Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.

26	"ERROR: Cannot create tmintfinfo 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.

27	"ERROR: Cannot find intf_id field"
	Description	The server process was unable to find the intf_id field in the com.beasys.CORBA.tgiop.tmintfinfo class.
	Action	Contact BEA Customer Support.

28	"ERROR: Cannot find impl_id field"
	Description	The server process was unable to find the impl_id field in the com.beasys.CORBA.tgiop.tmintfinfo class.
	Action	Contact BEA Customer Support.

29	"ERROR: Cannot find deact_policy field"
	Description	The server process was unable to find the deact_policy field in the com.beasys.CORBA.tgiop.tmintfinfo class.
	Action	Contact BEA Customer Support.

30	"ERROR: Cannot find tx_policy field"
	Description	The server process was unable to find the tx_policy field in the com.beasys.CORBA.tgiop.tmintfinfo class.
	Action	Contact BEA Customer Support.

31	"ERROR: Cannot find state_policy field"
	Description	The server process was unable to find the state_policy field in the com.beasys.CORBA.tgiop.tmintfinfo class.
	Action	Contact BEA Customer Support.

32	"ERROR: Cannot find svc_nm field"
	Description	The server process was unable to find the svc_num field in the com.beasys.CORBA.tgiop.tmintfinfo class.
	Action	Contact BEA Customer Support.

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.

39	"Usage: buildXAJS [-E envlabel] [-v] -r rmname [-o outfile]\n\t Also make sure JAVA_HOME is set in the environment\n"
	Description	This message shows the proper usage of the buildXAJS command.
	Action	Re-execute the buildXAJS command with the proper parameters or environmental variables.

40	"ERROR: Cannot execute prog_name\n"
	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.

41	"Usage: JavaServer [JVM specific options] file.jar [application options]"
	Description	This message shows the proper usage of the JavaServer command in the UBBCONFIG file.
	Action	Make the appropriate modifications to the UBBCONFIG file so that the JavaServer command is executed with the proper parameters.

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.

49	"ERROR: Cannot find com.beasys.Tobj.infrastructure.ServerMain class"
	Description	The server process was unable to find the com.beasys.Tobj.infrastructure.ServerMain class.
	Action	Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.

50	"ERROR: Cannot find com.beasys.Tobj.ObjectManager class"
	Description	The server process was unable to find the com.beasys.Tobj.Objectmanager class.
	Action	Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.

51	"ERROR: Cannot find com.beasys.Tobj.OrbMain class"
	Description	The server process was unable to find the com.beasys.Tobj.OrbMain class.
	Action	Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.

52	"ERROR: Cannot find ServerMain.init"
	Description	The server process was unable to find the init() method in the com.beasys.Tobj.infrastructure.ServerMain class.
	Action	Contact BEA Customer Support.

54	"ERROR: Cannot find ObjectManager.handleTransactionEnd"
	Description	The server process was unable to find the handleTransactionEnd() method in the com.beasys.Tobj.ObjectManager class.
	Action	Contact BEA Customer Support.

55	"ERROR: Cannot find OrbMain.objectManager"
	Description	The server process was unable to find the objectManager() method in the com.beasys.Tobj.OrbMain class.
	Action	Contact BEA Customer Support.

56	"ERROR: Cannot find ObjectManager.txInInvocation"
	Description	The server process was unable to find the txInInvocation() method in the com.beasys.Tobj.ObjectManager class.
	Action	Contact BEA Customer Support.

57	"ERROR: Cannot find ServerMain.release"
	Description	The server process was unable to find the release() method in the com.beasys.Tobj.infrastructure.ServerMain class.
	Action	Contact BEA Customer Support.

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>\n"
	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 buildjavaserver.main\n"
	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.

64	"ERROR: Cannot obtain ObjectManager from OrbMain"
	Description	The server process will not boot because critical information that it needs is missing.
	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 intialization failed"
	Description	The server process initialization has failed because of an internal error.
	Action	Contact BEA Customer Support.

67	"ERROR: Cannot allocate request array"
	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.

68	"ERROR: service returned null"
	Description	The processing of an incoming request to the server process failed because of an internal error in the server process.
	Action	Contact BEA Customer Support.

69	"ERROR: Cannot allocate return 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.

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.

71	"ERROR: You do not have a valid BEA WLE Java server license"
	Description	The server process will not boot because you do not have a valid BEA WLE Java server license.
	Action	Contact BEA Customer Support to acquire an appropriate license.

72	"ERROR: Your license for BEA WLE Java server has expired"
	Description	This server process will not boot because your license for the BEA WLE Java server has expired.
	Action	Contact BEA Customer Support to acquire a new license.

73	"WARN: <pattern> not found in <file>\n"
	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>\n"
	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>\n"
	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> \n"
	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>\n"
	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>\n"
	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\n"
	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\n"
	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>\n"
	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.

119	"ERROR: Server initialization failed"
	Description	The initialization of the JavaServer failed.
	Action	Check the ULOG for additional error information and take appropiate corrective actions.