IJINFRA Messages 200-299
|
|
|
200
ERROR: Cannot find file filename
Description
When executing jmkfldhdr, the specified file,
filename, could not be found.
If the file name was specified on the command line,
jmkfldhdr looks for the file in the current directory.
If the file name was specified in the FIELDTBLS environment variable and
not on the command line,
jmkfldhdr looks for the file in the directories
listed in the FLDTBLDIR environment variable;
otherwise, if the FLDTBLDIR environment variable is not set,
only the current directory is searched.
Action
Check that the file name is correct and that the FLDTBLDIR environment variable is set correctly.
See Also
jmkfldhdr(1), field_tables(5)
201
ERROR: Cannot open input file filename
Description
jmkfldhdr failed to open the specified input file, filename, for reading.
Action
Check that the input file exists and has read permission.
See Also
jmkfldhdr(1)
202
ERROR: Cannot open output file filename
Description
jmkfldhdr failed to create and open the specified output file, filename, for writing.
Action
Check that the directory for the output file exists and has write and execute permissions set correctly. If the file already exists, check that it has write permissions set correctly.
See Also
jmkfldhdr(1)
203
ERROR: Invalid base number, val, in file val; line ignored
Description
While processing a field table file filename with jmkfldhdr,
a line with an invalid base number base_number was encountered and ignored.
Action
The field table file will be processed, but the invalid line is ignored. Correct the base number and re-execute the command.
See Also
field_tables(5)
204
ERROR: Invalid line ignored in file val: val
Description
While processing a field table file filename with jmkfldhdr,
an invalid line was encountered and ignored. The content of the line is printed.
Action
The field table file is processed, but the invalid line is ignored. Normally, the field table should be corrected and the command re-executed.
See Also
field_tables(5)
205
ERROR: Invalid type, val, in file val; line ignored
Description
While processing a field table file filename with jmkfldhdr,
a line with an invalid field type field_type was encountered and ignored.
Action
The field table file is processed, but the invalid line is ignored. Correct the field type and re-execute the command.
See Also
field_tables(5)
206
ERROR: Invalid field number, val, in file val; line ignored
Description
While processing a field table file filename with jmkfldhdr,
a line with an invalid field number field_number was encountered and ignored.
Action
The field table file is processed, but the invalid line is ignored. Correct the field number and re-execute the command.
See Also
field_tables(5)
214
ERROR: [NULL interface name used to get interface information]
Description
The server has encountered an internal error while registering its interfaces with the WLE infrastructure.
Action
Contact BEA Customer Support.
215
ERROR: [Unable to open the *INTERFACES section table]
Description
A BEA TUXEDO system internal function was used to retrieve interface information from the interfaces table, but the open failed.
Action
Contact BEA Customer Support.
216
ERROR: [Unable to read information from the *INTERFACES section table]
Description
A BEA TUXEDO system internal function was unable to read the
INTERFACES section of the TUXCONFIG file.
Action
Contact BEA Customer Support
217
ERROR: Maximum number of types/subtypes, val, has been exceeded
Description
The maximum number of types/subtypes permitted for a particular TUXEDO System/T interface has been exceeded. The number allowed is val.
Action
Review the configuration file, verify that all interfaces use less than the maximum number of types/subtypes, and reload the TUXCONFIG file.
See Also
ubbconfig(5), tmloadcf(1)
218
ERROR: [Invalid buffer type information val]
Description
The buffer type information provided in the configuration file for an interface entry was incorrect.
Action
Check the configuration file, verify that the buffer type provided is correct, and repeat the operation.
See Also
ubbconfig(5), tmloadcf(1)
219
ERROR: [Invalid buffer subtype information val]
Description
The buffer subtype information provided in the configuration file for an interface entry was incorrect.
Action
Check the configuration file, verify that the buffer type provided is correct, and repeat the operation.
See Also
ubbconfig(5), tmloadcf(1)
220
ERROR: Suspended client attempting to generate new request
Description
A suspended client attempted to inject new work into the domain. Clients are suspended by the application administrator using either the /AdminGUI or /AdminAPI.
Action
Contact your application administrator to determine why the client was suspended and when it might be unsuspended.
See Also
Administering the BEA TUXEDO System, BEA TUXEDO Administrator's Guide to the Web-Based GUI, tpacall(3c), tpcall(3c), MIB(5), TM_MIB(5)
221
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() has failed.
Action
Make sure the 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.
222
ERROR: Cannot receive reply because MSSQ is specified but REPLYQ is N
Description
An error has occurred in receiving a reply from either a tpcall(3c) or tpacall(3c) because the configuration file specifies that there should be no reply queue established for that particular server.
Action
If the server is expected to receive tpacall or tpcall replies,
check and edit the UBBCONFIG file and specify REPLYQ=Y to establish a reply
queue for that particular server. If the server is not to receive replies,
use tpacall(3c) with the flags parameter set to TPNOREPLY.
See Also
ubbconfig(5), tpcall(3c), tpacall(3c)
223
ERROR: Memory allocation failure val
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed.
Action
Make sure the 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 swap space and physical memory on the machine.
224
ERROR: MAXOBJECTS is 0: No methods allowed.
Description
An operation related to object methods was executed but no objects are configured.
Action
Reconfigure the application to increase the size of the table
by setting the MAXOBJECTS parameter in
the RESOURCES section of the UBBCONFIG file.
See Also
ubbconfig(5)
225
ERROR: One-way method was not executed
Description
An attempt to execute a one way method failed. No notification goes back to the client.
Action
No action is needed.
226
ERROR: Cannot create call descriptor for callout message, tperrno=val
Description
While generating a descriptor handle for a callout message, an error occurred with tperrno tperrno.
Action
The maximum number of outstanding asynchronous callout method invocations was reached. Retrieve replies to at least one of the invocations and issue the callout again.
227
ERROR: Unable to send callout message to process (val)
Description
While sending a callout message to process pid, an error occurred.
Action
The most common cause of this error message is that the recipient of the callout message has died. Check to see if pid is still running; if it is, contact BEA Customer Support.
228
ERROR: Received unrecognized message type - sending failure reply
Description
The server received an invalid service request message. It will be ignored and a failure reply will be sent to the requestor.
Action
Contact BEA Customer Support.
229
ERROR: Memory allocation failure
Description
An attempt to dynamically allocate memory from the operating system using malloc() failed while receiving a service request in a server.
Action
Make sure the 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.
230
ERROR: Request/response request received in conversational server
Description
A message request was received by a conversational server from a request/response server.
Action
Verify that the service name used in a tpcall, tpacall, or
tpforward belongs to a request/response server and not to a
conversational server.
See Also
tpcall(3c), tpacall(3c), and tpforward(3c).
231
ERROR: Conversational request received in request/response server
Description
A message request was received from a conversational server by a request/response server.
Action
Verify that the service name in tpconnect belongs to a conversational
server and not to a request/response server.
See Also
tpconnect(3c)
232
ERROR: Old M3 request received by new server process
Description
Method requests received by an M3 server that were routed via the Active Object Map (that is, not stateless) must be processed by the same process to which the routing function sent the request. The original server died and this is a restarted server that is rejecting an old enqueued message.
Action
No action required.
233
ERROR: Service request problem, tperrno = val
Description
A message request was received indicating that the message should be handled by the server in transaction mode and the corresponding tpbegin failed.
Action
Verify that the message was not received by an unsolicited message handler,
the server was not part of or registered with the application, the global transaction id
was valid, the server had no outstanding reply messages, the resource manager was not
opened, there was not enough space in the global transaction table, the resource manager
xa_start failed, or a BBL lock or unlock failed.
See Also
tpbegin(3c)
234
WARN: Server groupid/serverid: client process processid: lost message
Description
A server died and the specified server (with group identifier groupid and server identifier serverid) is recovering on its behalf. A message from the client with the specified processid has been lost. Additional information will be printed in subsequent messages.
Action
No action required.
See Also
Messages 235 and 236.
235
WARN: SERVICE=servicename MSG_ID=msgid REASON=server died
Description
A server died while processing the service servicename. The client from which the message was sent is still active so a response message will be sent indicating the failure.
Action
No action required.
See Also
Message 234.
236
WARN: SERVICE=servicename MSG_ID=msgid REASON=server and client died
Description
A server died while processing the service servicename. The client from which the message was sent is no longer active either so a response message cannot be sent indicating the failure.
Action
No action required.
See Also
Message 234.
237
ERROR: Cannot find own server entry
Description
When receiving a service request in a server, the server was unable to find its own entry in the Bulletin Board.
Action
Check the ULOG for earlier messages indicating problems with the application, and check with the application administrator. If the problem persists, contact BEA Customer Support.
238
WARN: Invalid server pool option -p val
Description
The given argument is in an invalid format.
Action
The format for the -p option is:
-p[L][low-water][,[terminate_time]][:
[high_water][,create_time]]
Reformat argument to comply with the format for -p.
See Also
servopts(5)
239
ERROR: Fatal error receiving requests, shutting server down
Description
The system detected a fatal error during the reception on incoming service requests.
Action
This message is supplied when the server has found a condition that does not allow the server to continue operation. The most common causes are lack of memory and corrupted memory, but other conditions could also cause this behavior. The server will shut itself down. If you believe that your system has enough memory and that the memory in the server has not been corrupted, contact BEA Customer Support.
240
ERROR: Invalid mid value during spawn
Description
While getting ready to spawn a conversational server, the calling process failed to retrieve its machine table entry. The machine identifier that is used to retrieve the entry is invalid. The conversational server will, therefore, not be spawned.
Action
Look through the ULOG to see if there are other messages related to this failure. If so, refer to the appropriate system messages. Otherwise, contact BEA Customer Support.
241
ERROR: Argument vector formation error during spawn
Description
While getting ready to spawn a conversational server, the calling process failed to build
the command line arguments for that server. An attempt to dynamically allocate memory from
the operating system using malloc(3) or realloc(3) failed while
building the command line. The conversational server will, therefore, not be spawned.
Action
Make sure the 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.
242
ERROR: aout=val: too many arguments
Description
While getting ready to spawn a conversational server, the calling process failed to set the argument vector for that server. The calling process attempted to pass more than 256 arguments to the conversational server. The conversational server will, therefore, not be spawned.
Action
Make sure the number of arguments passed to the conversational server is not greater than 256. Note that the system may be adding up to eight arguments to the command line obtained from the configuration file.
See Also
ubbconfig(5)
243
ERROR: spawn error: cannot fork
Description
The calling process failed to spawn a conversational server. The call to fork(2) failed.
Action
The system-imposed limit on the total number of processes under execution by a single user may be exceeded. In this case you may either reduce the number of processes the BEA TUXEDO system application administrator is running on the system, or increase the total number of processes allowed per user by reconfiguring the UNIX kernel.
See Also
fork(2) in UNIX reference manuals
244
ERROR: Cannot exec, executable file not found
Description
The calling process failed to spawn a conversational server. The call to exec(2) failed. The conversational server to be spawned does not exist.
Action
Make sure the conversational server is in the application directory.
See Also
exec(2) in UNIX reference manuals, ubbconfig(5)
245
ERROR: Application initialization failure
Description
An application initialization failure occurred in the tpsvrinit(3c) processing for a dynamically spawned conversational server.
Action
Examine application-specific code to determine the cause of the error.
See Also
BEA TUXEDO Programmer's Guide, tpopen(3c), tpsvrinit(3c)
246
ERROR: Cannot exec, network send error
Description
The calling process failed to spawn a conversational server due to a networking problem.
Action
Make sure the network has not been partitioned and that the remote site is booted. If the remote site is not booted, call tmboot(1). If the remote site is booted, use tmadmin(1) to determine the status of the network, and reconnect the remote site to the network, if necessary.
See Also
exec(2) in UNIX reference manuals, tmadmin(1), tmboot(1), ubbconfig(5)
247
WARN: process id=pid ... Assume started (network).
Description
The calling process attempted to spawn a conversational server. The conversational server with a process ID of pid is believed to have been started. However, the calling process did not receive an acknowledgment.
Action
Make sure a conversational server with process ID pid is running. If not, look for a core dump in the application directory.
248
WARN: process id=pid ... Assume started (pipe).
Description
The calling process attempted to spawn a conversational server. The conversational server with a process ID of pid is believed to have been started. However, the calling process did not receive an acknowledgment.
Action
Make sure a conversational server with process ID pid is running. If not, look for a core dump in the application directory.
249
ERROR: No BBL available, cannot boot
Description
The calling process failed to spawn a conversational server. The BBL is not active.
Action
Make sure the BBL is booted on the site on which the conversational server is being spawned.
Use tmadmin(1) to check the status of the application. If the BBL needs to be booted, use tmboot(1).
See Also
tmadmin(1), tmboot(1)
250
ERROR: No DBBL available, cannot boot
Description
The calling process failed to spawn a conversational server. The DBBL is not active on the master site.
Action
Make sure the DBBL is booted on the master site. Use tmadmin(1) to check the status of the application.
See Also
tmadmin(1)
251
ERROR: Spawning process failed.
Description
The calling process failed to spawn a conversational server.
Action
Look through the ULOG to see if there are other messages related to this failure. If so, refer to the appropriate system messages. Otherwise, contact BEA Customer Support.
See Also
Messages 252 and 253.
252
ERROR: Process process at site failed with /T error (errmsg)
Description
The calling process failed to spawn a conversational server, process. The spawned server failed on site site.
Action
Take corrective measures based on errmsg.
253
ERROR: Process process at site failed with code code
Description
The calling process failed to spawn a conversational server, process. The spawned server failed on site site.
Action
Take corrective measures based on error code code.
254
ERROR: The -p option is valid only for SHM mode with load balancing
Description
To use the server pool option -p, the application must be SHM mode and must have load balancing turned on.
Action
Remove the -p option from the CLOPT for the affected server.
Make sure the application is running in SHM mode. Remember that SHM mode applications
should have no NETWORK section in the UBBCONFIG file and
should have
MODEL set to SHM. Turn load balancing on in the application by
specifying LDBAL to Y in the RESOURCES
section of the UBBCONFIG file.
See Also
servopts(5)
255
ERROR: The -p option is not valid for conversational servers
Description
To use the server pool option -p, the server must not be conversational.
Action
Remove the -p option from the CLOPT for the affected server.
Make sure the server is not conversational by specifying CONV=N in the
SERVERS section of the UBBCONFIG file for the affected server.
See Also
servopts(5)
256
ERROR: The -p option is valid only for MSSQ servers
Description
In order to use the server pool option -p, the server must be in an
MSSQ set where MAX is greater than 1.
Action
Remove the -p option from the CLOPT for the affected server.
Make sure the server
is in an MSSQ set by supplying a RQADDR for the server in the
SERVERS section of the UBBCONFIG file.
Make sure that the value of MAX in the SERVERS section
of the UBBCONFIG file is greater than 1 for the affected server.
See Also
servopts(5)
257
ERROR: Invalid -p values val,val:val,val
Description
One of the values lw, tt, hw, or ct is incorrect.
Action
The format for the -p option is:
-p[L][low-water][,[terminate_time]][:
[high_water][,create_time]]
Reformat the argument to comply with the format for -p.
See Also
servopts(5)
258
ERROR: Cannot lock Bulletin Board
Description
While testing the server pool, an error occurred while attempting to lock the bulletin board.
Action
Contact BEA Customer Support.
See Also
servopts(5)
259
ERROR: Null message buffer, cannot dispatch service
Description
The run server function, which continually dequeues messages (service requests), called the server dispatch routine with a null message pointer. This means that the dequeuing of a message failed.
Action
System message resources may be corrupted.
260
ERROR: Unknown service request name
Description
The server dispatch function calls a high-level service dispatch, which attempts to find the entry point address of the service and cannot. The server dispatch function records this error.
Action
Shared memory may be corrupted, or the ipc application key is not correct.
261
ERROR: Failed sending reply
Description
The server dispatch function calls a high-level service dispatch, which attempts to find the entry point address of the service and cannot. The server dispatch function conveys this error to the caller via a message (reply). If the message send fails, this message appears.
Action
System message resources may be exhausted, the application may be partitioned, or shared memory is corrupted.
262
ERROR: Service 'name' failed to call tpreturn or tpforward
Description
The server dispatch function calls the service. Control returning after this call is an indication that tpreturn failed (it does a longjmp and should never return after the call), or tpforward failed (it gives up control to another server). These are the only two ways a service can surrender control after processing a service.
Action
The stack in the service became corrupted. Try running the service under a debugger.
See Also
tpsvrdone(3c)
263
ERROR: NULL service name, cannot dispatch service request
Description
The service start routine, called by the start work routine (which is called by the service dispatch routine), failed because the dispatched message contained no service request name.
Action
Verify that the application ipc key is correct and that not more than one application is using the same ipc key. Also, determine whether some other failure occurred with the associated message queues.
264
ERROR: Function address set to -1
Description
The service start routine, called by the start work routine (which is called by the service dispatch routine), failed because the bulletin board entry for the requested service function address contains a zero.
Action
Verify that the application ipc key is correct and that not more than one application is using the same ipc key.
265
ERROR: Invalid message pointer given
Description
The service dispatch routine passed the service start work routine
a null pointer due to a TPESYSTEM
error that occurred earlier. This occurred in either a (D)BBL or server and indicates that a corrupt or
invalid message was received.
Action
Verify that the correct machine types are set, that the application ipc key is correct, and that not more than one application is using the same ipc key.
266
ERROR: Cannot execute service, address not known
Description
During the service dispatch, the service start function returned null, indicating a failure. This could be due to a null service name appearing in the dispatched message, the requested service not being found, or the bulletin board not being locked.
Action
Verify that the application ipc key is correct, that not more than one application is using the same ipc key, and that the service is advertised.
267
ERROR: Work completed, cannot stop twice
Description
When a service returns from dispatch, a flag is checked to see if the service was started
successfully. If this flag is not set, the above error message appears. This flag is only
turned on if the service starts, and is turned off only when the service done function
completes. Either the service never started or the service done function was called more
than once.
Action
Check the ULOG for additional information about server failures.
268
ERROR: Commit error due to outstanding handles
Description
An attempt to commit a transaction with outstanding handles failed.
Action
This is an application error. Make sure there are no outstanding handles before calling tpcommit().
269
ERROR: Cannot retrieve gtrid for aomhandle val
Description
While attempting to check the entering transaction's validity, an invalid AOM handle was detected.
Action
Contact BEA Customer Support.
270
ERROR: Cannot allocate return gtrid
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.
271
ERROR: buffer pool: Invalid set size val
Description
An invalid set size was specified when requesting a new buffer set in the JNI buffer pool.
Action
Contact BEA Customer Support.
272
ERROR: Cannot allocate buffer 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.
273
ERROR: Cannot create global ref for stream
Description
Cannot create a global reference for the buffer stream.
Action
Contact BEA Customer Support.
274
WARN: Cannot allocate input buffer header
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.
275
ERROR: Cannot allocate input buffer header
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.
276
WARN: Cannot allocate 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.
277
ERROR: Cannot allocate 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.
278
ERROR: Cannot lock buffer pool
Description
Cannot get the lock for the JNI buffer pool.
Action
Contact BEA Customer Support.
279
ERROR: Cannot unlock buffer pool
Description
Cannot release the lock for the JNI buffer pool.
Action
Contact BEA Customer Support.
280
ERROR: Cannot allocate extra free list header
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.
281
ERROR: Cannot allocate Jolt 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 for 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.
282
ERROR: send0: Cannot find request header
Description
Cannot retrieve the header of the request message while attempting to send the reply for the request.
Action
Contact BEA Customer Support.
283
ERROR: sendRequest: Missing objinfo
Description
The object info was missing while attempting to send a TUXEDO request.
Action
Contact BEA Customer Support.
284
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 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.
285
ERROR: Cannot convert buffer to Jolt format: val (val)
Description
An error occurred while converting a received buffer to Jolt format.
Action
Contact BEA Customer Support.
286
ERROR: Native context initialization called after contexts have been created
Description
The contexts have already been created while attempting to initialize native contexts.
Action
Contact BEA Customer Support.
287
ERROR: tpcall(.TMIB) failure val
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.
288
ERROR: Client information not found
Description
Cannot find the client name and username from TMIB.
Action
Contact BEA Customer Support.
289
ERROR: Client information not found
Description
Cannot find the client name and username from TMIB.
Action
Contact BEA Customer Support.
290
ERROR: msgsnd failed in sendSignal with errno val
Description
An error occurred while sending signal (via a zero-length message) to wake up the main thread.
Action
Contact BEA Customer Support.
291
ERROR: Out of memory. Cannot allocate space for Java info
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.
292
ERROR: Cannot find val class
Description
The JNI function FindClass cannot find the specified class.
Action
Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.
293
ERROR: Cannot create ref for val
Description
Cannot create a global reference for the specified class.
Action
Contact BEA Customer Support.
294
ERROR: Cannot find val.val
Description
Cannot find the specified method in the specified class.
Action
Contact BEA Customer Support.
295
ERROR: Cannot find val.val
Description
Cannot find the specified field in the specified class.
Action
Contact BEA Customer Support.
296
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 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.
297
ERROR: Unexpected Jolt opcode val
Description
An unexpected Jolt opcode was specified while attempting to send a Jolt message.
Action
Contact BEA Customer Support.
298
ERROR: Invalid index val into object info table
Description
An invalid object info table index was specified while attempting to retrieve the object info.
Action
Contact BEA Customer Support.
299
ERROR: Object info table entry at index val is free
Description
An invalid object info table entry was found while attempting to retrieve the object info.
Action
Contact BEA Customer Support.
 |
 |
 |