Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs.beasys.com   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
WLE Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

IJINFRA Messages 100-199

105	ERROR: tpcommit reported err in reply processing
	Description	An attempt to call the tpcommit() function failed during reply processing. The detailed error is provided in the error string err.
	Action	Contact BEA Customer Support.
106	WARN: transaction processing failure in reply processing
	Description	A transaction processing failure has been encountered during the processing of a reply.
	Action	None. This may result in a more severe problem that will be logged as an error.
107	WARN: _tmfmsg_copy_tcm fails
	Description	A call to the _tmfmsg_copy_tcm() function to copy the message has failed.
	Action	None. This may result in a more severe problem that will be logged as an error.
108	ERROR: Failed to send reply: err
	Description	An attempt to send a reply has failed. The detailed error is provided in the error message err.
	Action	Contact BEA Customer Support.
109	WARN: Number of worker threads specified is too high. Resetting to 500.
	Description	The number of the worker threads specified in the UBBCONFIG file exceeds the upper limit of 500. It is being reset to 500.
	Action	None.
112	ERROR: Cannot open internal temporary file
	Description	The program could not create or open an internal temporary file in this directory.
	Action	Make sure that permissions have been set so that this program can open, read, and write internal temporary files.
113	ERROR: Out of memory
	Description	An attempt to allocate space for internal data structures failed as 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.
114	ERROR: Cannot write to internal temporary file
	Description	The program could not create or open an internal temporary file in this directory.
	Action	Make sure that permissions have been set so that this program can open, read, and write internal temporary files.
127	ERROR: Cannot convert client_id field
	Description	An error occurred when converting client_id field of client info.
	Action	Contact BEA Customer Support.
131	WARN: Access control violation - user sub on sub tried to access sub sub
	Description	This is a warning message indicating an EJB method access control violation. A proper exception will be returned.
	Action	Check the deployment descriptor for proper security setting.
132	WARN: .SysACLPerm: User sub on sub tried to access sub sub
	Description	This is a warning message indicating an EJB method access control violation. A proper exception will be returned.
	Action	Check the deployment descriptor for proper security setting.
133	ERROR: ax_reg returns err
	Description	An attempt by the multithreaded JavaServerXA to dynamically register with the WLE infrastructure failed. The details of the error are provided in the error code err.
	Action	Contact BEA Customer Support.
134	ERROR: Cannot init TLS
	Description	An attempt to initialize the WLE internal thread of the local storage data structure failed.
	Action	Contact BEA Customer Support.
135	ERROR: xa_open returns err
	Description	An attempt by the WLE infrastructure to initialize the Resource Manager via an xa_open call failed. The XA error code is specified in err.
	Action	Refer to the X/Open XA specification for a definition of the XA error code. Also check the resource manager vendor's trace file for additional information, if any. If applicable, correct any resource manager problems. If it is a CORBA application, make sure TP.open_xa_rm is called from Server.initialize(). If the problem persists, contact BEA Customer Support.
136	ERROR: xa_start returns err
	Description	An attempt by the WLE infrastructure to perform xa_start failed. The XA error code is specified in err.
	Action	Refer to the X/Open XA specification for a definition of the XA error code. Also check the resource manager vendor's trace file for additional information, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support.
137	ERROR: xa_end returns err
	Description	An attempt by the WLE infrastructure to perform xa_end failed. The XA error code is specified in err.
	Action	Refer to the X/Open XA specification for a definition of the XA error code. Also check the resource manager vendor's trace file for additional information, if any. If applicable, correct any resource manager problems. If the problem persists, contact BEA Customer Support.
138	ERROR: Out of memory
	Description	An attempt to allocate memory for WLE internal data structure failed.
	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. If the problem persists, contact BEA Customer Support.
139	ERROR: Cannot init TLS
	Description	An attempt to initialize the WLE internal thread of the local storage data structure failed.
	Action	Contact BEA Customer Support.
140	ERROR: Cannot init TLS
	Description	An attempt to initialize the WLE internal thread of the local storage data structure failed.
	Action	Contact BEA Customer Support.
141	WARN: Attempt to use multithreaded JavaServer without setting multithreaded RM option
	Description	This is a warning message to indicate that the multithreaded JavaServerXA is used without specifying the multi-threaded option for the particular resource manager.
	Action	It is highly recommended that the multithreaded JavaServer should be used with the multithreaded resource manager option turned on. Otherwise, unexpected run-time behavior may result. Ignore this warning if the resource manager being used does not have a specific multithreading option.
142	WARN: xa_start() failed with error: err
	Description	This is a warning message to indicate that an attempt by the WLE infrastructure to call xa_start during transaction callback failed. The XA error code is specified in err.
	Action	None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG.
143	WARN: xa_end() failed with error: err
	Description	This is a warning message to indicate that an attempt by the WLE infrastructure to call xa_start during transaction callback failed. The XA error code is specified in err.
	Action	None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG.
144	ERROR: xa_open returns err
	Description	An attempt by the WLE infrastructure to initialize the resource manager via the xa_open call failed. The XA error code is specified in err.
	Action	Refer to the X/Open XA specification for a definition of the XA error code. Also check the resource manager vendor's trace file for additional information, if any. If applicable, correct any resource manager problems. If it is a CORBA application, make sure TP.open_xa_rm is called from Server.initialize(). If the problem persists, contact BEA Customer Support.
145	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 xa_start during the transaction pre-prepare phase failed. The XA error code is specified in err.
	Action	None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG.
146	WARN: xa_end() 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 xa_end during the transaction pre-prepare phase failed. The XA error code is specified in err.
	Action	None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG.
147	WARN: xa_start() failed in rollback with error = err
	Description	This is a warning message to indicate that an attempt by the WLE infrastructure to call xa_start during transaction rollback failed. The XA error code is specified in err.
	Action	None. This may subsequently result in a more severe error. If so, the error message will be displayed in the ULOG.
148	WARN: Switching to FASTPATH; PROTECTED is not supported for JavaServers
	Description	This is a warning message indicating that PROTECTED was specified in the SYSTEM_ACCESS keyword in the UBBCONFIG file. As PROTECTED mode is not supported for JavaServers, it will be switched to FASTPATH mode.
	Action	None.
149	ERROR: Cannot allocate FML32 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.
150	ERROR: Call to TMIB failed
	Description	The server process was unable to call the TMIB at initialization.
	Action	Contact BEA Customer Support.
151	ERROR: No MODULE specified
	Description	The MODULE attribute was missing in the SERVERS section of the UBBCONFIG file. The JavaServer cannot be started.
	Action	Check and correct the UBBCONFIG file.
152	ERROR: Invalid Module name
	Description	Invalid MODULE name was found in the SERVERS section of the UBBCONFIG file. The JavaServer cannot be started.
	Action	Check and correct the UBBCONFIG file.
153	ERROR: Failed to initialize Request Level Interceptors
	Description	A problem was encountered while reading the Registry for Request Level Interceptors.
	Action	Contact BEA Customer Support.
154	WARN: JAVA_HOME not set. Cannot add tools.jar to CLASSPATH for debugging
	Description	This is a warning message indicating that JAVA_HOME was not set, hence Java debugging may not be possible.
	Action	Set the JAVA_HOME environment variable properly if debugging is needed.
155	ERROR: Cannot initialize Request Level Interceptors
	Description	A problem was encountered while setting up the Request Level Interceptors.
	Action	Contact BEA Customer Support.
156	ERROR: Cannot initialize buffer pool
	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.
157	ERROR: Exception occurred in server main init
	Description	The server process initialization has failed because of an internal error.
	Action	Contact BEA Customer Support.
158	ERROR: Cannot get input buffer type
	Description	An attempt to get the incoming request buffer type failed.
	Action	Contact BEA Customer Support.
159	ERROR: Cannot allocate request 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 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.
160	ERROR: Cannot get service definition for sub
	Description	Cannot find the definition for the specified service request.
	Action	Contact BEA Customer Support.
161	ERROR: Cannot preserve input buffer
	Description	After the incoming request was processed, the associated internal buffer failed to be released.
	Action	Contact BEA Customer Support.
162	WARN: Unexpected context switch
	Description	This is a warning message indicating that an unexpected context switch occurred.
	Action	None.
163	ERROR: Cannot reattach to Bulletin Board
	Description	An attempt to reattach the server process to the Bulletin Board failed while the JavaServer was trying to switch to FASTPATH mode at initialization.
	Action	Contact BEA Customer Support.
164	ERROR: Cannot change FML32 buffer
	Description	An internal error occurred when the server process was preparing the data buffer to make the TMIB call at initialization.
	Action	Contact BEA Customer Support.
165	ERROR: Cannot initialize server main
	Description	The server process initialization has failed because of an internal error.
	Action	Contact BEA Customer Support.
166	ERROR: Failed read of Orb Registry
	Description	The JavaServer's attempt to read the Request Level Interceptor configuration failed on opening the Registry or accessing the appropriate configuration set.
	Action	Contact BEA Customer Support.
167	ERROR: Cannot access file sub
	Description	The jar file that contains the Request Level Interceptors cannot be found on the specified path.
	Action	Check the Registry to see if the file was configured properly and check the path to see if it is correct and the file exists.
168	ERROR: Cannot access file sub in APPDIR sub
	Description	The jar file that contains the Request Level Interceptors cannot be found relative to any path specified in the APPDIR environment variable.
	Action	Check the Registry to see if the file was configured properly and check the paths in APPDIR to see if the file exists.
169	ERROR: Cannot change FML32 buffer
	Description	An internal error occurred when the server process was preparing the data buffer to make the TMIB call at initialization.
	Action	Contact BEA Customer Support.
170	ERROR: Call to TMIB failed
	Description	The server process was unable to call the TMIB at initialization.
	Action	Contact BEA Customer Support.
171	ERROR: System Registry open failed
	Description	The JavaServer failed to open the Registry.
	Action	Contact BEA Customer Support.
172	ERROR: AppRequestInterceptors key not found
	Description	The entry was not found in the Registry.
	Action	Contact BEA Customer Support.
173	ERROR: ImagePath key not found
	Description	The entry was not found in the Registry.
	Action	Contact BEA Customer Support.
174	ERROR: EntryPoint key not found
	Description	The entry was not found in the Registry.
	Action	Contact BEA Customer Support.
175	ERROR: EntryPoint value cannot be empty
	Description	The entry was not found in the Registry.
	Action	Contact BEA Customer Support.
176	ERROR: DisplayName key not found
	Description	The entry was not found in the Registry.
	Action	Contact BEA Customer Support.
177	ERROR: Group key not found
	Description	The entry was not found in the Registry.
	Action	Contact BEA Customer Support.
178	ERROR: ErrorControl key not found
	Description	The entry was not found in the Registry.
	Action	Contact BEA Customer Support.
179	ERROR: JavaServer cannot be part of MSSQ set
	Description	JavaServer will not work on an MSSQ set. The JavaServer is not started.
	Action	Contact BEA Customer Support.
180	WARN: REPLYQ=Y not supported in multithreaded mode. Reverting to REPLYQ=N
	Description	This is a warning message indicating that REPLYQ=Y is not supported in multi-threaded mode, so the server reverts to REPLYQ=N.
	Action	None.
181	ERROR: Green Thread is not supported on HPUX
	Description	An attempt to use Green Thread to build the JavaServer failed; the Green Thread model is not supported on HPUX.
	Action	Check for a proper JDK development environment on your HPUX system.
182	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.
183	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.
184	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.
185	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.
186	ERROR: Cannot find com.beasys.Tobj.xml.Generator.Generator.main
	Description	While executing buildjavaserver, the process was unable to find the main() method in the class com.beasys.Tobj.xml.Generator.Geeenerator.main.
	Action	Contact BEA Customer Support.
187	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.
188	ERROR: Type switch buffer uninitialization routine failure
	Description	An internal error occurred while attempting to free the request buffer after the request is finished.
	Action	Contact BEA Customer Support.
189	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.
190	ERROR: Reply length is zero
	Description	A zero length reply message was received for the service request.
	Action	Contact BEA Customer Support.