1200
|
INFO:.SysClientState: User usrname on LMID state change to state
|
|
|
Description
|
This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client are sent in the posted buffer.
|
|
Action
|
This is an informational message.
|
|
See Also
|
EVENT_MIB(5), TM_MIB(5)
|
1201
|
WARN:.SysClientSecurity: User usrname on LMID authentication failure
|
|
|
Description
|
This message indicates that the client specified above failed security validation when trying to join the application. A complete listing of the current attributes of the client are sent in the posted buffer.
|
|
Action
|
Check to make sure that this is not some hacker trying to gain access to your application data.
|
|
See Also
|
EVENT_MIB(5), TM_MIB(5)
|
1204
|
ERROR: Memory allocation failure error_info
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system failed while decoding a workstation client message. Additional information about the problem is printed as part of the message.
|
|
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.
|
1205
|
ERROR: Memory allocation failure error_info
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system failed while decompressing a workstation client message. Additional information about the problem is printed as part of the message.
|
|
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.
|
1206
|
ERROR: Memory allocation failure error_info
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system failed while trying to compress a message. Additional information about the problem is printed as part of the message.
|
|
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.
|
1207
|
ERROR: Expected numeric argument to -c option
|
|
|
Description
|
A non-numeric argument was passed to the WSL -c option.
|
|
Action
|
Change the configuration of the WSL to have a numeric compression limit.
|
|
See Also
|
WSL(5)
|
1208
|
ERROR: Memory allocation failure error_info
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system failed while trying to process a workstation client message for _tmpostrecv. Additional information about the problem is printed as part of the message.
|
|
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.
|
1213
|
ERROR: Type switch uninitialization failure
|
|
|
Description
|
While processing a workstation client buffer, the buffer uninitialization function, _tmuninitbuf, returned an error.
|
|
Action
|
Check the buffer type switch to see that it is correctly set up (that the right uninitialization function is associated with the correct buffer type). If an application-defined buffer type, check the uninitialization function to see that it is coded correctly.
|
|
See Also
|
buffer(3c), typesw(5)
|
1215
|
ERROR: Expected numeric argument to -k option
|
|
|
Description
|
A non-numeric argument was passed to the WSL -k option.
|
|
Action
|
Change the configuration of the WSL to have a numeric compression limit.
|
|
See Also
|
WSL(5)
|
1216
|
ERROR: Expected numeric argument to -p option
|
|
|
Description
|
The -p option to the workstation listener controls the minimum TCP port number which a workstation handler will attempt to listen. This port number must be numeric.
|
|
Action
|
Change the -p option to be numeric.
|
1217
|
ERROR: Expected numeric argument to -P option
|
|
|
Description
|
The -P option to the workstation listener controls the maximum TCP port number which a workstation handler will attempt to listen. This port number must be numeric.
|
|
Action
|
Change the -P option to be numeric.
|
1218
|
ERROR: The -p (minport) or -P (maxport) option is out of range
|
|
|
Description
|
minport must be less than or equal to maxport, and both must be less than or equal to 65535.
|
|
Action
|
Change the -p or -P option to comply with the restrictions.
|
1219
|
ERROR: Memory allocation failure
|
|
|
Description
|
While creating a data structure to keep track of TCP port numbers, the system ran out of memory.
|
|
Action
|
Make sure that 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.
|
1220
|
ERROR: Exhausted all available ports
|
|
|
Description
|
The workstation listener has tried all TCP ports within the range specified by the -p and -P options. It could not bind to any of the TCP ports in the range.
|
|
Action
|
If there are more workstation handlers than ports available in the range specified by -p and -P, then a new handler will not be able to bind to any of the TCP ports in the allowable range. Do not forget about the TCP port which is used by the workstation listener as well. Increase the range specified by the -p and -P options.
|
1221
|
ERROR: Could not establish listening address address
|
|
|
Description
|
The workstation listener has tried all TCP ports within the range specified by the -p and -P options. It could not bind to any of the TCP ports in the range. The workstation listener could not bind to the given address.
|
|
Action
|
If there are more workstation handlers than ports available in the range specified by -p and -P, then a new handler will not be able to bind to any of the TCP ports in the allowable range. Do not forget about the TCP port which is used by the workstation listener as well. Increase the range specified by the -p and -P options. Make sure that address is correct.
|
1222
|
ERROR: Expected numeric argument to -z option
|
|
|
Description
|
The -z option to the workstation listener controls the minimum allowable encryption strength. This number must be numeric.
|
|
Action
|
Change the -z option to be numeric.
|
1223
|
ERROR: Expected numeric argument to -Z option
|
|
|
Description
|
The -Z option to the workstation listener controls the maximum allowable encryption strength. This number must be numeric.
|
|
Action
|
Change the -Z option to be numeric.
|
1224
|
ERROR: Link Level Encryption add-on package is not installed
|
|
|
Description
|
The minimum number of encryption bits was greater than zero, but there is no link level encryption add-on package installed on this machine.
|
|
Action
|
Install the link level encryption package or change the minimum encryption bits (the -z option) to be zero.
|
1225
|
ERROR: Only 40 bit encryption is allowed
|
|
|
Description
|
The minimum number of encryption bits was greater than forty, but only the 40-bit link level encryption add-on package is installed on this machine.
|
|
Action
|
Install the 128-bit link level encryption package or change the minimum encryption bits (the -z option) to be zero or forty.
|
1226
|
ERROR: The -z (min) or -Z (max) must be 0, 40 or 128
|
|
|
Description
|
The only levels of encryption understood by the system are 0, 40 or 128.
|
|
Action
|
Ensure that both min and max are set only to 0, 40 or 128.
|
1229
|
WARN: A client failed encryption negotiation
|
|
|
Description
|
A workstation client attempted to log in to the system, but could not negotiate an acceptable encryption level.
|
|
Action
|
When workstation clients log into the system, they negotiate an encryption strength with the workstation listener. If the client and listener cannot agree on the level of encryption (for example, if the workstation listener demands 128-bit encryption and the client can only speak 40-bits encryption) then this message will appear. The administrator can either change the encryption policy of the workstation listener or workstation client.
|
1230
|
ERROR: Invalid security protocol
|
|
|
Description
|
An invalid opcode was attempted while the workstation listener was insecure.
|
|
Action
|
Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.
|
1231
|
ERROR: Memory allocation error
|
|
|
Description
|
While negotiating the Diffie-Hellman parameters, the workstation listener ran out of memory.
|
|
Action
|
Make sure that 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.
|
1232
|
ERROR: Encryption negotiation protocol error
|
|
|
Description
|
An invalid opcode was attempted while the workstation listener was insecure.
|
|
Action
|
Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.
|
1233
|
ERROR: Unable to get encryption handle
|
|
|
Description
|
While negotiating the Diffie-Hellman parameters, the workstation listener had an error while attempting to get an encryption handle.
|
|
Action
|
Make sure that 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.
|
1234
|
ERROR: Unable to establish negotiation parameters
|
|
|
Description
|
An invalid opcode was attempted while the workstation listener was insecure.
|
|
Action
|
Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.
|
1235
|
ERROR: Unable to send negotiation parameters
|
|
|
Description
|
While attempting to send the Diffie-Hellman parameters to the client, an error occurred.
|
|
Action
|
The network may have experienced an error, or the client waiting for the security packet may have been killed. If neither of these events has occurred, contact your BEA TUXEDO system Technical Support.
|
1236
|
ERROR: Unable to begin encryption
|
|
|
Description
|
After establishing the shared key, an error occurred while starting encryption.
|
|
Action
|
Monitor your network for malicious use. Contact your BEA TUXEDO system Technical Support.
|
1237
|
ERROR: tpnotify(TPACK) failed to reply, tperrno = tperrno
|
|
|
Description
|
The workstation handler sent an acknowledged unsolicited message to a client. However, that client never sent its acknowledgment.
|
|
Action
|
The network may have experienced an error, or the client waiting for the notification may have been killed. tperrno may provide clues as to the cause of this failure. If neither of these events has occurred, contact your BEA TUXEDO system Technical Support.
|
1238
|
ERROR: Invalid security parameters
|
|
|
Description
|
The encryption level of the workstation listener is greater than zero bits, but the link level encryption package is not installed on this machine.
|
|
Action
|
The MIB may have changed the minimum encryption bits for this workstation handler. If the new value of the minimum encryption bits is greater than zero and the link level encryption package is not installed, then no clients will be able to log into the workstation handler. Change the minimum encryption value via the -z option to the workstation listener, or through the MIB with the TA_MINENCRYPTBITS member of the T_WSL class.
|
1239
|
ERROR: Invalid security parameters
|
|
|
Description
|
The encryption level of the workstation listener is greater than forty bits, but only the 40-bit link level encryption package is installed on this machine.
|
|
Action
|
The MIB may have changed the minimum encryption bits for this workstation handler. If the new value of the minimum encryption bits is greater than forty, then no clients will be able to log into the workstation handler. Change the minimum encryption value via the -z option to the workstation listener, or through the MIB with the TA_MINENCRYPTBITS member of the T_WSL class.
|
1240
|
ERROR: Failed to read server table entry, tperrno = tperrno
|
|
|
Description
|
The workstation listener was rebooting after a failure and could not read the server table.
|
|
Action
|
The bulletin board may be corrupted. tperrno may provide clues as to the cause of this failure. Contact your BEA TUXEDO system Technical Support.
|
1241
|
ERROR: Sending of reply to tpbroadcast() or tpnotify() call to client failed
|
|
|
Description
|
The workstation handler received an acknowledgment from a workstation client but was unable to forward the acknowledgment to the sender of the tpnotify.
|
|
Action
|
The originator of the tpnotify may have been killed. If the originator of the notify has not been killed, contact your BEA TUXEDO system Technical Support.
|
1242
|
ERROR: Bad Internet type of listening address provided: address
|
|
|
Description
|
address is not a valid internet address.
|
|
Action
|
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Change address to comply with the known formats. If you believe that your address is in the proper format, contact your BEA TUXEDO system Technical Support.
|
1243
|
ERROR: -H hexadecimal value has to have an even length
|
|
|
Description
|
If an address starts with 0x, then that address must be an even length of characters.
|
|
Action
|
A hexadecimal character represents a nibble (4 bits). A byte is 8 bits. To fully specify a byte, two characters are needed. Change the address to have an even number of characters.
|
1244
|
ERROR: Memory allocation failure
|
|
|
Description
|
While creating a data structure for an address specified via the -H option, the system ran out of memory.
|
|
Action
|
Make sure that 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.
|
1245
|
ERROR: Bad hexadecimal number provided for external address: address
|
|
|
Description
|
The hexadecimal address address from the -H option is in an improper format.
|
|
Action
|
Any address which starts with 0x must be a valid hexadecimal address. Valid hexadecimal characters are 0 - 9, a-f and A-F. Change address to comply with the known formats.
|
1246
|
ERROR: Bad Internet type of external address provided: address
|
|
|
Description
|
The internet address address from the -H option is in an improper format.
|
|
Action
|
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Change address to comply with the known formats.
|
1247
|
ERROR: Memory allocation failure
|
|
|
Description
|
While allocating space for the binary representation of the -H option address, the system ran out of memory.
|
|
Action
|
Make sure that 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.
|
1248
|
ERROR: Memory allocation failure
|
|
|
Description
|
While allocating space for the binary representation of the -H option address, the system ran out of memory.
|
|
Action
|
Make sure that 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.
|
1249
|
ERROR: -H and -n have different length of network address
|
|
|
Description
|
If you are using an external address, then that address must have the same format as the -n option.
|
|
Action
|
Change the -H option to have the same format as the -n option.
|
1250
|
ERROR: External address can not be resolved val
|
|
|
Description
|
The Domain Name Service could not resolve the address given by the -H option.
|
|
Action
|
Make sure that the Domain Name Service knows the server represented by the address given in the -H option. If the name service does not know the server, reconfigure the name service properly. Change the address in the -H option to a name which is well known by the name service.
|
1251
|
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 be a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
|
1252
|
ERROR: Unable to determine license level
|
|
|
Description
|
While validating the value of the -c argument of the workstation listener, an error occurred while retrieving the current license attributes.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
1253
|
ERROR: Workstation compression configured, but no license for workstation compression was found
|
|
|
Description
|
You do not have a license to use workstation compression.
|
|
Action
|
Purchase a license for workstation compression. If you believe that you own and have installed the license for workstation compression, contact your BEA TUXEDO system Technical Support.
|
1254
|
ERROR: Bad conversational sequence number
|
|
|
Description
|
Conversations are sequenced in order to provide protection. One of the conversational messages arrived out of order. The conversation has been disconnected, and if a transaction was active, it has been set to the ABORTONLY state.
|
|
Action
|
Look at the userlog to determine whether or not the BRIDGE has given up sending any messages to the message queue for the workstation handler. If it has, the operating system may need to be tuned to properly handle a high volume of messages. This problem may also be alleviated by using compression. This error may also occur when the BRIDGE is failing over to a new network link or failing back to an high priority link.
|
1255
|
WARN: Couldn't change to client context num, continuing
|
|
|
Description
|
An internal error was encountered while attempting to switch client contexts.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
1256
|
WARN:.SysClientSecurity: User user on machine authentication failure
|
|
|
Description
|
This is the system event message which is posted when a user fails authentication.
|
|
Action
|
The action depends on the security policy of the user.
|
1257
|
ERROR: Couldn't create buffer for receiving messages
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system using malloc failed in the generic handler.
|
|
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.
|
1258
|
WARN: No client context space available in handler
|
|
|
Description
|
The maximum number of clients has been used up in the generic handler.
|
|
Action
|
Either increase the total number of clients allowable into the system, or do not attempt to connect to a loaded system.
|
1259
|
ERROR: Memory allocation failure
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system using malloc failed in the generic handler.
|
|
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.
|
1260
|
ERROR: Memory allocation failure
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system using malloc failed in the generic handler.
|
|
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.
|
1261
|
ERROR: tpinit() failed, tperrno = tperrno
|
|
|
Description
|
A client was unable to enter the system from the generic handler. The tperrno may give clues as to the cause of this failure.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
1262
|
ERROR: tpchkauth() failed, tperrno = tperrno
|
|
|
Description
|
tpchkauth failed from the generic handler. The tperrno may give clues as to the cause of this failure.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
1263
|
WARN: Forced shutdown of client; user name 'name'; client name 'client'
|
|
|
Description
|
A forced shutdown of the given user name and client name has been performed by the generic handler.
|
|
Action
|
None.
|
1264
|
WARN:.SysClientDied: User user on machine client died
|
|
|
Description
|
This is the event posted when a forced shutdown of the given user name on machine has been performed by the generic handler.
|
|
Action
|
None.
|
1265
|
ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV
|
|
|
Description
|
An operating system error occurred in the generic handler while reading a message queue.
|
|
Action
|
Ensure the sanity of the system. Contact your BEA TUXEDO system Technical Support.
|
1266
|
ERROR: Received message of type 'type' to tpinit() call
|
|
|
Description
|
The only message type which tpinit takes is TPINIT. The generic handler found a type of type was given to tpinit.
|
|
Action
|
Ensure all clients of the generic handler provide the proper buffer type during tpinit.
|
1267
|
ERROR: TPINIT information must be passed to tpinit() call in secure application
|
|
|
Description
|
Secure applications must provide the TPINIT buffer to tpinit. A client of the generic handler in a secure application did not provide the TPINIT buffer.
|
|
Action
|
Ensure all clients of the generic handler provide a TPINIT buffer during tpinit in a secure application.
|
1268
|
ERROR: Invalid client name given 'client'
|
|
|
Description
|
The given client is invalid in the application.
|
|
Action
|
Ensure that the TPINIT buffer passed to tpinit does not have the invalid client name.
|
1269
|
ERROR: Invalid length for TPINIT structure given
|
|
|
Description
|
An invalid TPINIT buffer has been processed by the generic handler.
|
|
Action
|
There may be a negative length in the TPINIT datalen field. Ensure no client passes a TPINIT buffer with a negative datalen field to the generic handler.
|
1270
|
ERROR: Failed to update registry table information
|
|
|
Description
|
The generic handler was not able to update the BEA TUXEDO system registry information.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
1271
|
Failed to send message to authentication server, tperrno = tperrno
|
|
|
Description
|
The generic handler was not able to send the TPINIT buffer to the server offering AUTHSVC.
|
|
Action
|
Ensure that the authentication server is up and running, and that the AUTHSVC is currently advertised. Contact your BEA TUXEDO system Technical Support.
|
1272
|
WARN: Invalid notification option given, reset to TPU_IGN.
|
|
|
Description
|
The generic handler does not handle the notification option from the client.
|
|
Action
|
Ensure that all clients change the notification options to one which the generic handler is able to accept.
|
1273
|
INFO:.SysClientState: User user on machine state change to state
|
|
|
Description
|
This event is posted by the generic handler whenever the user on machine changes state. The new state is given in state.
|
|
Action
|
None.
|
1274
|
INFO: Abortively disconnecting workstation client user[user], client[client]
|
|
|
Description
|
The generic handler is disconnecting a client which is believed to be dead.
|
|
Action
|
None.
|
1275
|
INFO: Userid: [userid], Clientid: [clientid] timed out due to inactivity
|
|
|
Description
|
The generic handler timed out the given userid and clientid.
|
|
Action
|
None.
|
1276
|
ERROR: Received message with unknown release number value
|
|
|
Description
|
The WSH received a packet with an unknown release number value. The network may be having difficulty. If link level encryption is in use, this error may be an indication that an attack is in progress.
|
|
Action
|
If this error happens consistently, then contact the BEA TUXEDO system Technical Support.
|
1277
|
ERROR: Memory allocation failure
|
|
|
Description
|
An attempt dynamically to allocate memory from the operating system using malloc failed while initializing the WSL or WSH.
|
|
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.
|
1278
|
ERROR: Address conversion error
|
|
|
Description
|
The WSH had a problem converting an address from a binary format to a text format.
|
|
Action
|
If this error happens consistently, then contact the BEA TUXEDO system Technical Support.
|
1279
|
ERROR: descriptor allocation error
|
|
|
Description
|
The WSH was unable to allocate a network resource for the listening endpoint.
|
|
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.
|
1280
|
ERROR: Could not initialize network (error)
|
|
|
Description
|
The WSH or WSL could not initialize its network.
|
|
Action
|
Ensure that the network is viable on the machine. If the network is viable, contact your BEA TUXEDO system Technical Support.
|
1281
|
ERROR: Could not initialize global information (error)
|
|
|
Description
|
The WSH or WSL could not initialize its network.
|
|
Action
|
Ensure that the network is viable on the machine. If the network is viable, contact your BEA TUXEDO system Technical Support.
|
1282
|
ERROR: Failed to initialize network protocol information (error)
|
|
|
Description
|
The WSH or WSL could not initialize its network.
|
|
Action
|
Ensure that the network is viable on the machine. If the network is viable, contact your BEA TUXEDO system Technical Support.
|
1283
|
ERROR: Network error (error) servicing network event
|
|
|
Description
|
The WSL encountered a severe error while handling network events.
|
|
Action
|
Ensure that the network is viable on the machine. If the network is viable, contact your BEA TUXEDO system Technical Support.
|
1284
|
ERROR: Failed to allocate a network resource (error)
|
|
|
Description
|
The WSH or WSL could not allocate a network descriptor for a remote connection.
|
|
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.
|
1285
|
ERROR: Expected numeric argument to -N option
|
|
|
Description
|
The -N option to the WSL requires a numeric argument greater than or equal to zero.
|
|
Action
|
Modify the -N option of the WSL to have a numeric argument in the proper range.
|
1286
|
ERROR: -K argument must be client, handler, both, or none
|
|
|
Description
|
The -K option for the WSL requires an argument of client, handler, both or none.
|
|
Action
|
Ensure that the -K option of the WSL is client, handler, both or none. Check your spelling.
|
1287
|
WARN: Forced shutdown of client; user name 'name'; client name 'name' workstation address 'xxx.xxx.xxx.xxx' did not call tpterm()
|
|
|
Description
|
This may result from shutting down a WSH when clients are connected, a client connection has timed out, the WSH was unable to send a network message to the client or an incorrect APP_PW (application password) was rejected during tpinit.
|
|
Action
|
If APP_PW is turned on (refer to your ubbconfig file and ubbconfig(5)), then check with your system administrator to verify that you are using the correct application password for your TUXEDO application.
|
1288
|
WARN: setsockopt() for SO_KEEPALIVE failed
|
|
|
Description
|
The KEEPALIVE handler-side networking option was configured for a WSL/WSH pair, but could not be enabled.
|
|
Action
|
This error is ignored and WSH processing continues normally. However, network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client timeout (WSL -T option) to reclaim resources associated with dead network connections.
|
|
See Also
|
WSL(5)
|
1289
|
WARN: KEEPALIVE option requested but not available on this platform
|
|
|
Description
|
The KEEPALIVE handler-side networking option was configured for a WSL/WSH pair, but could not be enabled because it is not available on this platform.
|
|
Action
|
This error is ignored and WSH processing continues normally. However network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client timeout (WSL -T option) to reclaim resources associated with dead network connections.
|
|
See Also
|
WSL(5)
|
1290
|
ERROR: Can't parse the address address
|
|
|
Description
|
While attempting to resolve address, an error occurred.
|
|
Action
|
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name and port number portion of address can be located by your server.
|
1291
|
ERROR: Can't resolve host name in address address
|
|
|
Description
|
While attempting to resolve the host name portion of address, an error occurred.
|
|
Action
|
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name portion of address can be located by your DNS server.
|
1292
|
ERROR: Unknown address type: address
|
|
|
Description
|
The given address does not correspond to a type known by the system.
|
|
Action
|
The BEA TUXEDO System understands several types of address format. Addresses which start with // must be internet addresses. Addresses which start with 0x are hexadecimal representations of the address. Other formats may or may not be understood by the BEA TUXEDO system.
|
1293
|
ERROR: Can't resolve port number in address address
|
|
|
Description
|
While attempting to resolve the port number portion of address, an error occurred.
|
|
Action
|
Any address which starts with // must be a valid internet address. The following formats are recognized by the system: //host.name:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the port number portion of address can be located by your server.
|
1294
|
ERROR: Can't convert the address address to binary format
|
|
|
Description
|
An error occurred while converting address to an internal binary representation.
|
|
Action
|
Contact your BEA TUXEDO system Technical Support.
|
1295
|
ERROR: Illegal character in the address address
|
|
|
Description
|
There is an illegal character in the port portion of address. Ports may only have alphanumeric characters.
|
|
Action
|
Remove the illegal character from the port portion of the address.
|
1296
|
ERROR: Missing port number in the address address
|
|
|
Description
|
address must have a port number portion.
|
|
Action
|
Supply a port number portion in the given address. Otherwise, the WSL or WSH cannot determine its listening endpoint properly.
|
1297
|
ERROR: Port number cant be bigger than value in the address address
|
|
|
Description
|
The port number portion of address is larger than the largest allowable port number of value.
|
|
Action
|
Change the port number to be within the specified range.
|