WSNAT Messages 1000-1099

1001

ERROR: Unused arguments passed to buildwsh

Description

The command line option passed to the buildwsh command is not recognized as a valid option. This could also be caused by an extra "-" in the command line.

Action

Examine the command line that calls buildwsh and remove the extraneous option.

See Also

buildwsh(1)

1002

ERROR: Unable to execute the command command_string

Description

While invoking the C compilation system to build a new Workstation Handler, an error was detected. This 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 Workstation 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 Workstation Handler. This should be roughly the same as the existing WSH and the added object files. Examine the $CC and $CFLAGS variables and, if set, make sure the options are correct for your C compilation environment.

See Also

cc(1) in UNIX system reference manuals, buildwsh(1)

1004

ERROR: Memory allocation failure

Description

An attempt dynamically to 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 physical memory on the machine. Increase the space on the swap device.

See Also

malloc(3) in UNIX system reference manuals

1008

ERROR: Could not establish listening address on network string

Description

This error occurs if the WSH or the WSL cannot advertise its listening address on the network. This could happen for one of the following conditions.

The format of the address supplied to the WSL 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 WSL is already in use by another process. For TCP/IP, this can be verified by using the netstat command.

The system has run out of network addresses for the WSH. The WSH requests a new address from the system. If there are no addresses available, the request is rejected.

A previously used address has not completed the close sequence. This occurs if the WSL or WSH was killed in an abortive manner such as kill -9. Some transports (among them, TCP/IP) keep the connection open for an "implementation dependent" time to flush the existing data on the buffered network connection.

Action

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

• Check that the address format is correct. For TCP/IP, the format is 0x0002ppppaaaaaaaa. This is a hexadecimal representation of the TCP/IP address, where pppp is a unique port number and aaaaaaaa is the IP dotted number in the /etc/hosts file for the machine on which the WSL will run.

• See if 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, check with the system administrator to increase the number of addresses to use.

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

See Also

netstat(3) in UNIX system reference manuals, Administering the BEA TUXEDO System

1010

ERROR: Couldn't convert buffer to current release format

Description

This error occurs if a Workstation client and the native UNIX system machine are of different TUXEDO System/T releases and the message is from an older release. The error can also occur if the message received by the WSH or WSL is corrupted.

Action

Contact BEA Customer Support.

1011

ERROR: Couldn't convert buffer to native site format

Description

The WSH was unable to convert a message from a workstation client format to the native format. This indicates that the buffer type is unknown to the WSH.

Action

Check the userlog for a message indicating the nature of the failure (in particular, the type and subtype of the buffer that could not be converted). It may be necessary to rebuild the WSH using buildwsh to include additional application buffer types.

See Also

buildwsh(1)

1017

ERROR: Invalid data length, data not self describing

Description

Pre-processing of the message being sent to the workstation client by the presend function for the buffer type failed.

Action

Check the userlog for additional messages indicating why the pre-processing failed. If the buffer type or the presend function is provided by the application, contact your system administrator. If this is one of the TUXEDO System/T-provided buffer types, contact BEA Customer Support.

See Also

typesw(5)

1018

ERROR: Invalid data length of 0, data not self describing

Description

Pre-processing of the message being sent to the workstation client by the presend function for the buffer type returned 0. This indicates that a message length of 0 was presented by the application and the buffer type is not self-describing, such that the presend function cannot infer the desired transfer length.

Action

The application must provide a length for sending messages of the particular buffer type.

See Also

typesw(5)

1019

ERROR: Message conversion to workstation format failed

Description

The WSH was unable to convert a message from a native format to workstation client format.

Action

This error should not occur. Contact BEA Customer Support.

1023

WARN: No client context space available in handler

Description

While setting up a connection for a new workstation client, the WSH ran out of room to keep context for clients.

Action

This error should occur rarely since the WSL transfers control of workstation client connections to WSH programs based on their current degree of multiplexing. Contact BEA Customer Support.

See Also

WSL(5)

1024

ERROR: Memory allocation failure

Description

An attempt dynamically to 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 physical memory on the machine. Increase the space on the swap device.

See Also

malloc(3) in UNIX system reference manuals

1025

ERROR: Expected numeric argument to -x option

Description

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

Action

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

See Also

WSL(5)

1026

ERROR: Handler received unexpected message

Description

The WSH received a message without a client context (that is, intended for the Workstation Handler) that is not in the right format (it is not a workstation message).

Action

The message will be ignored. Contact BEA Customer Support.

1027

ERROR: Handler received unexpected opcode 0xcode

Description

The WSH received a message without a client context (that is, intended for the Workstation Handler) that has an unrecognized operation code (normally, a shutdown message from the WSL).

Action

The message will be ignored. Contact BEA Customer Support.

1028

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

Description

The Workstation Handler encountered an error switching to the context of a client when 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 sending a reply message to a client, the operation failed.

Action

Check the userlog for messages indicating the nature of the failure. It may indicate that the client is no longer accessible (either the network or machine may have failed). Contact BEA Customer Support.

1030

INFO: Work Station Handler joining application

Description

This message indicates that a WSH process was started by the WSL, based on the command line options for the listener and the current demand by workstation clients.

Action

No action required.

See Also

WSL(5)

1031

ERROR: Invalid command line argument 'arg' ignored

Description

An illegal command line option was found in the command line options for the WSH.

Action

This should be a rare event since the WSH is started by the WSL (it is not started directly by the administrator). Contact BEA Customer Support.

See Also

WSL(5)

1032

ERROR: Memory allocation failure

Description

An attempt dynamically to 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 physical memory on the machine. Increase the space on the swap device.

See Also

malloc(3) in UNIX system reference manuals

1033

ERROR: Memory allocation failure

Description

An attempt dynamically to 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 physical memory on the machine. Increase the space on the swap device.

See Also

malloc(3) in UNIX system reference manuals

1034

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

Description

The Workstation Handler, WSH, failed in an attempt 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.

1035

ERROR: Handler table entry already occupied by pid

Description

The WSL started a WSH and assigned it a slot that is already occupied by another WSH process with process identifier pid.

Action

Contact BEA Customer Support.

See Also

WSL(5)

1036

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

Description

The length of the network address that the WSH is using to establish a connection is 0. This is not valid (and should not occur).

Action

Contact BEA Customer Support.

1037

ERROR: Can't synchronize with /WS listener ... continuing

Description

The connection between the WSL and the WSH that it is executing was lost by the forked WSH process. The pipe with WSL was lost and may be due to the WSL process being killed.

Action

No action required, although the cause of WSL dying should be investigated if not known.

See Also

WSL(5)

1038

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

Description

The Workstation Handler encountered an error switching to the context of a client when dropping all connections during shutdown.

Action

The connection is ignored. Contact BEA Customer Support.

1039

WARN: Can't use TPGETANY flag with tpcall()

Description

The workstation client called tpcall with the TPGETANY option. This is not valid, and TPEINVAL will be returned to the application.

Action

No action required.

See Also

tpcall(3)

1040

WARN: tpsprio() call failed, tperrno = tperrno_val

Description

A call to tpsprio in the WSH on behalf of the workstation client failed with tperrno set to tperrno_val.

Action

No action required.

See Also

tpsprio(3c)

1041

ERROR: Memory allocation failure

Description

An attempt dynamically to 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 physical memory on the machine. Increase the space on the swap device.

See Also

malloc(3) in UNIX system reference manuals

1042

ERROR: tpcall() call failed, tperrno = tperrno_val

Description

A call to tpcall in the WSH on behalf of the workstation client failed with tperrno set to tperrno_val.

Action

No action required.

See Also

tpcall(3c)

1043

ERROR: tpacall() call failed, tperrno = tperrno_val

Description

A call to tpacall in the WSH on behalf of the workstation client failed with tperrno set to tperrno_val.

Action

No action required.

See Also

tpacall(3)

1044

ERROR: tpgprio() call failed, tperrno = tperrno_val

Description

A call to tpgprio in the WSH on behalf of the workstation client failed with tperrno set to tperrno_val.

Action

No action required.

See Also

buildwsh(1)

1045

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

Description

An attempt to send an acknowledgment of a tpacall request to the Workstation Client has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support.

1046

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

Description

An attempt to send an acknowledgment of a tpinit request to the Workstation Client has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support.

1047

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

Description

An attempt to send an acknowledgment of a tpterm request to the Workstation Client has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support.

1048

ERROR: Sending of error reply to call client failed

Description

An attempt to send an acknowledgment message to the Workstation Client has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. 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.

Action

This error indicates a resource problem. If there is not sufficient memory to allocate buffers, the Workstation Handler process can not operate. Please contact your System Administrator for help. If machine resources are sufficient, this would indicate an internal problem with the Workstation Handler. In this case, contact BEA Customer Support.

1050

ERROR: Error switching to the handler's context

Description

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

Action

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

1052

ERROR: Failed to process network event

Description

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

Action

The error indicates an internal problem with the Workstation Handler or the LIBNET software. Contact BEA Customer Support.

1053

ERROR: Error polling network connections

Description

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

Action

The error indicates a network error. Check that the network connection to the Workstation Client has not gone down. If it has, the Workstation Client will have to rejoin the application. Contact BEA Customer Support.

1054

ERROR: Error generating network event list

Description

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

Action

The error indicates a network error. Check that the network connection to the Workstation Client has not gone down. If it has, the Workstation Client will have to rejoin the application. Contact BEA Customer Support.

1055

ERROR: Connection to unassigned WSH rejected

Description

The connection for the Workstation Client was timed out.

Action

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

1056

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

Description

The Workstation Handler encountered an error switching to the context of a client to do a tpterm.

Action

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

1057

ERROR: Error processing message received from network

Description

The Workstation Handler encountered an error receiving a message from the network.

Action

This error could indicate a network problem or an internal System/T problem. Contact BEA Customer Support.

1058

ERROR: Received message with opcode other than init for non-existant context

Description

The Workstation Handler has received a message from a process that has not joined the application.

Action

This message indicates an internal problem in communication between the Workstation Handler and the Workstation Client. Contact BEA Customer Support.

1059

ERROR: Received network message with unknown context

Description

The Workstation Handler has received a message from a process that it does not know about.

Action

This message indicates an internal problem in communication between the Workstation Handler and the Workstation Client. Contact BEA Customer Support.

1060

ERROR: Received message with context associated with a different connection

Description

The Workstation Handler, working on behalf of one client context, has received a message intended for a different client context.

Action

This message indicates an internal problem in communication between the Workstation Handler and the Workstation Client. Contact BEA Customer Support.

1061

ERROR: Received a reply message from a workstation

Description

The Workstation Handler has received a message containing the reply protocol from a Workstation Client.

Action

A Workstation Client should never send a message with this protocol. This situation indicates an internal problem in communication between the Workstation Handler and the Workstation Client. Contact BEA Customer Support.

1062

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

Description

An attempt to send an acknowledgment of a tpbegin request to the Workstation Client has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client process. Contact BEA Customer Support.

1063

ERROR: No more workstation handlers available

Description

An attempt to start a new Workstation Handler process has failed because the maximum limit of Workstation Handlers has already been started.

Action

The maximum number of Workstation Handlers specified in the configuration file have been started. In order to increase this number, the "CLOPT -M maxh" value must be changed. This can be done in two ways: first, shut the application down and change the configuration file and reboot the application, or second, change the value dynamically with tmconfig(1), shut down and reboot only the Workstation Listener (WSL) server.

1064

ERROR: Error formatting command line options for handler

Description

An error was encountered formatting the argument string needed for booting a Workstation Handler.

Action

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

See Also

WSL(5), servopts(5)

1065

ERROR: Error retrieving machine table entry of the listener

Description

An error was encountered trying to get internal machine information while booting a Workstation Handler.

Action

Contact BEA Customer Support.

1066

ERROR: Work Station Handler died, attempting restart

Description

If a Workstation Handler process has died and the number of Workstation Handler processes booted is below the minimum specified in the configuration file, the BEA TUXEDO system attempts to boot a new Workstation Handler. This message is written to the userlog when this happens.

Action

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

1067

ERROR: Work Station Handler died, cleaning up

Description

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

Action

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

1068

ERROR: Invalid command line argument 'arg' ignored

Description

An illegal command line option was found in the CLOPT string.

Action

Check the BEA TUXEDO Reference Manual for correct options.

See Also

WSL(5), servopts(5)

1069

ERROR: Sending of reply to tpbroadcast() or tpnotify() call to client failed

Description

An attempt to send an acknowledgment of a tpbroadcast or tpnotify request to the Workstation Client has failed.

Action

Contact BEA Customer Support.

1070

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

Description

The Workstation 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 Workstation Listener failed in an attempt to create a buffer for storing Workstation 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. 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

malloc(3) in UNIX system reference manuals

1072

ERROR: Memory allocation failure

Description

The Workstation Listener failed in an attempt 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. 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

malloc(3) in UNIX system reference manuals

1073

ERROR: Memory allocation failure

Description

The Workstation Listener failed in an attempt to create a buffer for storing a Workstation 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. 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

malloc(3) in UNIX system reference manuals

1074

ERROR: Memory allocation failure

Description

The Workstation Listener failed in an attempt 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. 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

malloc(3) in UNIX system reference manuals

1075

ERROR: Can't get machine entry for listener

Description

The Workstation Listener encountered an error attempting to read the *MACHINES entry from the configuration file.

Action

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

1076

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

Description

The Workstation Listener failed in an attempt 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.

See Also

Uunix_err(3c)

1077

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

Description

The Workstation Listener failed in an attempt to update the Bulletin Board.

Action

Check that the shared memory segment that contains the Bulletin Board has not been removed. If it has, then the application will need to be rebooted. Otherwise, this error would indicate an internal error. In this case, contact BEA Customer Support.

See Also

tperrno(5)

1078

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

Description

The Workstation Listener failed in an attempt 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.

See Also

tperrno(5)

1079

ERROR: Error starting minimum number of handlers

Description

The Workstation Listener encountered an error attempting to boot the minimum number of Workstation Handlers.

Action

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

1080

ERROR: Error polling network connections

Description

The Workstation Listener encountered an error polling a network connection.

Action

This error indicates a network error. Check with your system administrator to see if the network is down.

1082

ERROR: Error adding connection request to event list

Description

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

Action

This error indicates a resource problem. If there is not sufficient memory to allocate buffers, the Workstation Listener process can not operate. Please contact BEA Customer Support for help.

1083

ERROR: Error assigning connection request, can't create any more handlers

Description

The Workstation Listener was unable to start a new Handler.

Action

The most likely problem is that the maximum number of Workstation Handlers specified in the configuration file have been started. In order to increase this number, the CLOPT -M maxh value must be changed. This can be done in two ways: first, shut the application down and change the configuration file and reboot the application, or second, change the value dynamically with tmconfig(1), shut down and reboot only the Workstation Listener (WSL) server.

Another possible source of the problem could be that the number of processes allowable by a user (ulimit) has been reached. If this is the case, consult with your System Administrator to increase this limit.

1086

ERROR: Message conversion to release rel format failed

Description

The Workstation Handler/Listener was unable to change the release structure to 4.2.

Action

Contact BEA Customer Support.

1088

ERROR: tpinit() failed, tperrno = tperrno_val

Description

The tpinit(3c) function call used to connect a workstation client to a TUXEDO System/T 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 on the tpinit(3c) reference page.

Action

Refer to the tpinit(3c) reference page for causes of the specific tperrno value that was reported to the application. Eliminate the potential causes of such an error and retry the failed operation.

See Also

tpinit(3c), tperrno(5)

1089

ERROR: tpscmt() failed, tperrno = tperrno_val

Description

While attempting to commit a transaction on behalf of a workstation client, the workstation handler process was unable to set the transaction commit control characteristic for the transaction to TP_CMT_LOGGED. (For further information on the transaction commit control characteristic, refer to the tpscmt(3c) reference page.) For this reason, the attempt to commit the transaction failed.

Action

Since the transaction cannot be committed, it will be necessary for the user to abort it. The value of tperrno and immediately preceding messages in the userlog may provide further information as to the cause of the error.

See Also

tpabort(3c), tpcommit(3c), tpscmt(3c), tperrno(5)

1090

ERROR: tpscmt() failed, tperrno = tperrno_val

Description

While attempting to commit a transaction on behalf of a workstation client, the workstation handler process was unable to set the transaction commit control characteristic for the transaction to TP_CMT_COMPLETE. (For further information on the transaction commit control characteristic, refer to the tpscmt(3c) reference page.) For this reason, the attempt to commit the transaction failed.

Action

Since the transaction cannot be committed, it will be necessary for the user to abort it. The value of tperrno and immediately preceding messages in the userlog may provide further information as to the cause of the error.

See Also

tpabort(3c), tpcommit(3c), tpscmt(3c), tperrno(5)

1096

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

Description

An attempt to send an acknowledgment of a tpcommit request to the Workstation Client has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client 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 Workstation Client has failed.

Action

This is an internal message. This failure indicates a problem with the network, with the Workstation, or with the Workstation client 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 workstation listener process, the workstation listener found an inconsistency in the existing workstation specific shared memory regarding the number of workstation handler processes. The WSL attempts to shut down any associated WSH processes that it knows about, removes the inconsistent shared memory, and exits.

Action

The administrator should check for any stray workstation handler (WSH) processes associated with this particular workstation listener, and see that they are manually terminated. The administrator may then re-boot the workstation listener process.