ISNAT Messages 1000-1099

1001

ERROR: Unused arguments passed to buildish

Description

The command-line option passed to the buildish command is not recognized as a valid option. An extra hyphen (-) in the command line also might cause this error.

Action

Examine the command line that calls buildish and remove the extra option.

1002

ERROR: Unable to execute the command command_string

Description

While the C compilation system was being invoked to build a new IIOP Server Handler, an error was detected.

This error could happen for one of the following reasons:

• The C compilation system command was not found.

• The CC command returned an error while linking the new IIOP Server Handler.

• The $CC environmental variable was not set correctly.

• The $CFLAGS environmental variable has invalid options.

Action

Make sure the C compilation system is present on your machine. Make sure there is enough disk space available for the new IIOP Server Handler. The amount of disk space should be roughly the same as the existing IIOP Server Handler and the added object files. Examine the $CC and $CFLAGS variables and, if these variables are set, make sure the options are correct for your C compilation environment.

1004

ERROR: Memory allocation failure

Description

An attempt to allocate memory dynamically 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1008

ERROR: Could not establish listening address on network string

Description

This error occurs if the IIOP Server Listener cannot advertise its listening address on the network.

This error could happen for one of the following reasons:

• The format of the address supplied to the IIOP Server Listener is incorrect. If the address format is incorrect, the network provider will be unable to advertise the address and the request fails.

• The address used in the -n command-line option to the IIOP Server Listener is already in use by another process. For TCP/IP, this condition can be verified by using the netstat command.

• A previously used address has not completed the close sequence. This condition occurs if either the IIOP Server Listener or the IIOP Server Handler were killed in an abortive manner, such as kill-9. Some transports (among them, TCP/IP) keep the connection open for an implementation-dependent amount of time to flush the existing data on the buffered network connection.

Action

To correct the problem, match one of the following solutions with the previous problem descriptions:

• Check the address format. For TCP/IP, the address must be specified in either of the following two formats:
  
  //hostname:port_number"
"//#.#.#.#:port_number"

  The #.#.#.# is in dotted decimal format. In dotted decimal format, each # should be a number from 0 to 255.

• See whether other processes are using the requested network address. For TCP/IP, use the netstat command and, if the address is already in use, select a different address.

• If the system is out of network addresses, ask the system administrator to increase the number of addresses.

• If the connection is not closed yet, wait a few minutes and try again.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1023

WARN: No client context space available in handler

Description

While setting up a connection for a new client application, the IIOP Server Handler ran out of space to keep context for client applications.

Action

This error should occur rarely because the IIOP Server Listener transfers control of client application connections to IIOP Server Handler programs based on their current degree of multiplexing. Contact BEA Customer Support.

See Also

For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1024

ERROR: Memory allocation failure

Description

An attempt to allocate memory dynamically 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1025

ERROR: Expected numeric argument to -x option

Description

An invalid argument was passed to the ISL command-line option. The argument to the -x option, the degree of multiplexing, needs to be numeric. This error causes the IIOP Server Listener not to be booted.

Action

Make sure the argument to the -x option is numeric.

See Also

The ISL command. For information about the ISL command, see the Administration Guide.

1026

ERROR: Handler received unexpected message

Description

The IIOP Server Handler received a message without a client application context (that is, a message intended for the IIOP Server Handler that is not in the correct format.) It is not a WLE message.

Action

The message is ignored. Contact BEA Customer Support.

1027

ERROR: Handler received unexpected opcode 0xcode

Description

The IIOP Server Handler received a message without a client application context (that is, a message intended for the IIOP Server Handler that has an unrecognized operation code). This message is normally a shutdown message from the IIOP Server Listener.

Action

The message is ignored. Contact BEA Customer Support.

1028

WARN: Couldn't change to client context context_number, continuing

Description

The IIOP Server Handler encountered an error while it was switching to the context of a client application when the IIOP Server Handler was dropping all connections during shutdown.

Action

The connection is ignored. Contact BEA Customer Support.

1029

ERROR: Sending of reply message to client failed

Description

While a reply message was being sent to a client application, the operation failed.

Action

Check the user log for messages that indicate the nature of the failure. This warning may indicate that the client application is no longer accessible (that is, either the network or the machine has failed). Contact BEA Customer Support.

1030

INFO: IIOP Handler joining application

Description

The IIOP Server Listener started an IIOP Server Handler process based on the command-line options for the listener and the current demand by clients.

Action

None.

See Also

For information about ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1031

ERROR: Invalid command line argument 'arg' ignored

Description

An illegal command-line option was found in the command-line options for the IIOP Server Handler.

This error is rare because the IIOP Server Listener, not the system administrator, starts the IIOP Server Handler.

Action

Contact BEA Customer Support.

See Also

For information about ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1033

ERROR: Memory allocation failure

Description

An attempt to allocate memory dynamically 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1034

ERROR: Failed to attach to shared memory for listener table, errno = errno_val

Description

The IIOP Server Handler failed to attach a shared memory segment.

Action

This is an operating system error. Check the value of errno_val for an indication of the problem. Contact BEA Customer Support.

1035

ERROR: Handler table entry already occupied by pid

Description

The IIOP Server Listener started an IIOP Server Handler and assigned it a slot that is already occupied by another IIOP Server Handler process that has the process identifier pid.

Action

Contact BEA Customer Support.

See Also

For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1036

ERROR: Network provider returns a zero length network address, can't establish network address

Description

The length of the network address that the IIOP Server Handler is using to establish a connection is 0. This is invalid (and should not occur).

Action

Contact BEA Customer Support.

1037

ERROR: Can't synchronize with IIOP listener ... continuing

Description

The forked IIOP Server Handler process lost the connection between the IIOP Server Listener and the IIOP Server Handler that it is executing. The pipe with IIOP Server Listener may have been lost because the IIOP Server Listener process is being stopped.

Action

No action is required. However, the cause of the IIOP Server Listener disconnection should be investigated if the cause is not known.

See Also

For information about ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.

1038

WARN: Couldn't change to client context index, continuing

Description

The IIOP Server Handler encountered an error while it was switching to the context of a client application when the IIOP Server Handler was dropping all connections during shutdown.

Action

The connection is ignored. Contact BEA Customer Support.

1041

ERROR: Memory allocation failure

Description

An attempt to allocate memory dynamically 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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1047

ERROR: Sending of reply to tpterm() call to client failed

Description

An attempt to send an acknowledgment of a tpterm request to the WLE remote client application failed.

This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process.

Action

Contact BEA Customer Support.

1048

ERROR: Sending of error reply to call client failed

Description

An attempt to send an acknowledgment message to the WLE remote client application has failed.

This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process.

Action

Contact BEA Customer Support.

1049

ERROR: Couldn't create buffer for receiving messages

Description

An attempt to create a buffer with tpalloc failed. This buffer is used to receive messages.

This error indicates either a resource problem or an internal problem with the IIOP Server Handler.

Action

If there is insufficient memory to allocate buffers, the IIOP Server Handler process cannot operate. Contact BEA Customer Support.

If machine resources are sufficient, there is an internal problem with the IIOP Server Handler. In this case, contact BEA Customer Support.

1050

ERROR: Error switching to the handler's context

Description

The IIOP Server Handler was attempting to switch from a client application context to the IIOP Server Handler context when it experienced an error.

Action

The error indicates an internal problem with the IIOP Server Handler. Contact BEA Customer Support.

1052

ERROR: Failed to process network event

Description

The IIOP Server Handler was unable to process a network event using tmnwevent.

Action

The error indicates an internal problem with the IIOP Server Handler software. Contact BEA Customer Support.

1053

ERROR: Error polling network connections

Description

The IIOP Server Handler encountered an error polling a network connection using tmnwcpoll.

Action

The error indicates a network error. Check that the network connection to the WLE remote client application has not gone down. If the network connection has gone down, the WLE remote client application has to rejoin the application. Contact BEA Customer Support.

1054

ERROR: Error generating network event list

Description

The IIOP Server Handler encountered an error when polling a network connection using tmnwcpoll.

Action

The error indicates a network error. Check that the network connection to the WLE remote client application has not gone down. If the network connection has gone down, the WLE remote client application has to rejoin the application. Contact BEA Customer Support.

1055

ERROR: Connection to unassigned ISH rejected

Description

The connection for the client application was timed out.

Action

This situation may occur if the system or the network is very busy, or if the network has gone down. The client application should try again to join the application.

1056

WARN: Couldn't change to client context index, continuing

Description

The IIOP Server Handler encountered an error when switching to the context of a client application to do a tpterm.

Action

This error indicates an internal problem. Contact BEA Customer Support.

1059

ERROR: Received network message with unknown context

Description

The IIOP Server Handler has received a message from an unknown process.

Action

This message indicates an internal problem in communication between the IIOP Server Handler and the WLE remote client application. Contact BEA Customer Support.

1063

ERROR: No more IIOP handlers available

Description

An attempt to start a new IIOP Server Handler process has failed because the maximum limit of IIOP Server Handlers has already been reached.

Action

The maximum number of IIOP Server Handlers specified in the configuration file have been started. To increase this number, the CLOPT -M maxh value must be changed. This can be done in one of two ways:

• Shut down the application, change the configuration file, and reboot the application.

• Change the value dynamically with tmconfig (1), and shut down and reboot only the IIOP Server Listener.

1064

ERROR: Error formatting command line options for handler

Description

An error was encountered while the argument string needed for booting an IIOP Server Handler was being formatted.

Action

This message occurs if there are more than 256 characters in the CLOPT string in the configuration file.

See Also

ISL command and servopts(5). For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter. For information about servopts(5), see the BEA TUXEDO Reference Manual.

1065

ERROR: Error retrieving machine table entry of the listener

Description

An error was encountered while an IIOP Server Handler was trying to get internal machine information during an IIOP Server Handler boot process.

Action

Contact BEA Customer Support.

1066

ERROR: IIOP Handler died, attempting restart

Description

If an IIOP Server Handler process has died and the number of IIOP Server Handler processes booted is below the minimum number specified in the configuration file, the BEA WLE system attempts to boot a new IIOP Server Handler.

Action

IIOP Server Handlers should not die. If IIOP Server Handlers do die, it could indicate an internal problem that requires attention. Additional IIOP Server Handlers may need to be booted, if the system is very busy.

1067

ERROR: IIOP Handler died, cleaning up

Description

An IIOP Server Handler process has died and the number of IIOP Server Handler processes booted is below the minimum number specified in the configuration file. An attempt to boot a new IIOP Server Handler has failed.

Action

This could either be an operating system error or an internal WLE error. In the former case, contact your system administrator. In the latter case, contact BEA Customer Support.

1070

ERROR: Cannot boot ISL with MAXWSCLIENTS for machine set to 0

Description

The IIOP Server Listener process has failed to boot because the MAXWSCLIENTS parameter was not specified in the configuration file.

Action

The MAXWSCLIENTS parameter must be specified either in the RESOURCES section or in the MACHINES section of the configuration file.

1071

ERROR: Memory allocation failure

Description

The IIOP Server Listener failed to create a buffer for storing IIOP Server Handler information.

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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1072

ERROR: Memory allocation failure

Description

The IIOP Server Listener failed to create a buffer for storing a device name.

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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1073

ERROR: Memory allocation failure

Description

The IIOP Server Listener failed to create a buffer for storing an IIOP Server Handler's name.

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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1074

ERROR: Memory allocation failure

Description

The IIOP Server Listener failed to create a buffer for storing a network address.

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. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1075

ERROR: Can't get machine entry for listener

Description

The IIOP Server Listener encountered an error when attempting to read the MACHINES entry from the configuration file.

Action

Make sure the TUXCONFIG file has not been removed or corrupted. If the TUXCONFIG file is all right, contact BEA Customer Support.

1076

ERROR: Failed to create to shared memory for listener table, errno = errno_val

Description

The IIOP Server Listener failed to create a shared memory segment.

Action

This is an operating system error. Check the value of errno_val for an indication of the problem. Contact BEA Customer Support.

See Also

The Uunix_err(3c) command. For information about the Uunix_err(3c) command, see the BEA TUXEDO Reference Manual.

1077

ERROR: Failed to update server table entry, tperrno = tperrno_val

Description

The IIOP Server Listener failed to update the Bulletin Board.

Action

Check that the shared memory segment that contains the Bulletin Board has not been removed. If this segment has been removed, the application needs to be rebooted. Otherwise, this error indicates an internal error and you should contact BEA Customer Support.

See Also

The tperrno(5) command. For information about the tperrno(5) command, see the BEA TUXEDO Reference Manual.

1078

ERROR: Failed to attach to shared memory for listener table, errno = errno_val.

Description

The IIOP Server Listener failed to attach a shared memory segment.

Action

This is an operating system error. Check the value of errno_val for an indication of the problem. Contact BEA Customer Support.

See Also

The tperrno(5) command. For information about the tperrno(5) command, see the BEA TUXEDO Reference Manual.

1079

ERROR: Error starting minimum number of handlers

Description

The IIOP Server Listener encountered an error when attempting to boot the minimum number of IIOP Server Handlers.

Action

This could be an operating system error. Perhaps there are too many processes running. This could also be an internal error. Check the log file for other messages relating to this message. Contact BEA Customer Support.

1080

ERROR: Error polling network connections

Description

The IIOP Server Listener encountered an error when polling a network connection.

Action

This error indicates a network error. Check with your system administrator to see whether the network is down. If the network is all right, contact BEA Customer Support.

1082

ERROR: Error adding connection request to event list

Description

The IIOP Server Listener was unable to allocate space on the event list.

Action

This error indicates a resource problem. If there is insufficient memory to allocate buffers, the IIOP Server Listener process cannot operate. Contact BEA Customer Support.

1088

ERROR: tminit() failed, tperrno = tperrno_val

Description

The tminit(3c) function call used to connect a client application to a WLE server application has failed. Further information about the cause of the failure is provided by the value of tperrno. By examining the <atmi.h> header file, this numeric tperrno value may be converted to a symbolic value. Potential causes of each such symbolic value are listed for the tminit(3c) command.

Action

For causes of the specific tperrno value that was reported to the application, see the tminit(3c) command in the BEA TUXEDO Reference Manual. Eliminate the potential causes of such an error and retry the failed operation. Contact BEA Customer Support.

See Also

The tminit(3c) and tperrno(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1089

ERROR: tpscmt() failed, tperrno = tperrno_val

Description

While attempting to commit a transaction on behalf of a client application, the IIOP Server Handler process was unable to set the transaction commit control characteristic for the transaction to TP_CMT_LOGGED. For this reason, the attempt to commit the transaction failed. For further information about the transaction commit control characteristic, refer to the tpscmt (3c) command in the BEA TUXEDO Reference Manual.

Action

Because the transaction cannot be committed, the user must abort the transaction. The value of tperrno and immediately preceding messages in the user log may provide further information as to the cause of the error.

See Also

The tpabort (3c), tpcommit (3c), tpscmt (3c), and tperrno (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1090

ERROR: tpscmt() failed, tperrno = tperrno_val

Description

While attempting to commit a transaction on behalf of a client application, the IIOP Server Handler process was unable to set the transaction commit control characteristic for the transaction to TP_CMT_COMPLETE. For this reason, the attempt to commit the transaction failed. For further information about the transaction commit control characteristic, refer to the tpscmt(3c) command in the BEA TUXEDO Reference Manual.

Action

Because the transaction cannot be committed, the user must abort the transaction. The value of tperrno and immediately preceding messages in the user log may provide further information as to the cause of the error.

See Also

The tpabort (3c), tpcommit (3c), tpscmt (3c), and tperrno (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1096

ERROR: Sending of reply to tpcommit() call to client failed

Description

An attempt to send an acknowledgment of a tpcommit request to the WLE remote client application has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process. Contact BEA Customer Support.

1097

ERROR: Sending of reply to tpabort() call to client failed

Description

An attempt to send an acknowledgment of a tpabort request to the WLE remote client application has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process. Contact BEA Customer Support.

1099

ERROR: Could not find correct number of active handlers, found num1, expected num2

Description

While being restarted after the death of a previous IIOP Server Listener process, the IIOP Server Listener found an inconsistency in the existing specific shared memory regarding the number of IIOP Server Handler processes. The IIOP Server Listener attempts to shut down any associated IIOP Server Handler processes that it knows about, removes the inconsistent shared memory, and exits.

Action

The system administrator should check for any stray IIOP Server Handler processes associated with this particular IIOP Server Listener, and see that they are manually terminated. The system administrator may then reboot the IIOP Server Listener process.