LIBGWT Messages 1500-1599
1500
INFO: Retrying domain (domainid=<domainid>) every val seconds
Description
The connection attempt has failed and the gateway is configured for periodic retries (RETRY_INTERVAL
and MAXRETRY
parameters in the DM_LOCAL_DOMAINS
entry).
Action
No action is required. To disable the periodic retry, use the dmadmin 'disconnect' command.
1501
WARN: Message with TPNOREPLY to service val dropped - network down
Description
A message with the TPNOREPLY flag cannot be sent because the gateway is unable to establish connectivity with the remote domain. Since the application cannot be notified, a message is written to the ULOG.
Action
No action is required.
1502
WARN: Message with TPNOREPLY to service val dropped - network down
Description
A message with the TPNOREPLY flag cannot be sent because the gateway is unable to establish connectivity with the remote domain. Since the application cannot be notified, a message is written to the ULOG.
Action
No action is required.
1503
WARN: Message with TPNOREPLY to service val dropped - network down
Description
A message with the TPNOREPLY flag cannot be sent because the gateway is unable to establish connectivity with the remote domain. Since the application cannot be notified, a message is written to the ULOG.
Action
No action is required.
1504
ERROR: Minimum encryption (val) is larger than 56, but only the 56-bit package is installed
Description
The minimum encryption level specified in the DM_TDOMAIN
section of the DMCONFIG
file is greater than 56-bit. Since the license installed allows only 56-bit encryption, the gateway cannot support the specified minimum encryption level.
Action
Either set the minimum encryption level to 56, 40, or 0 bits, or obtain a license for stronger encryption. The link-level encryption value of 40 bits is provided for backward compatibility. If you believe you are licensed for stronger encryption, contact BEA Customer Support.
See Also
DMCONFIG
(5)
1505
ERROR: Minimum encryption (val) is larger than 56, but only the 56-bit package is installed
Description
The minimum encryption level specified in the DM_TDOMAIN
section of the DMCONFIG
file is greater than 56-bit. Since the license installed allows only 56-bit encryption, the gateway cannot support the specified minimum encryption level.
Action
Either set the minimum encryption level to 56, 40, or 0 bits, or obtain a license for stronger encryption. The link-level encryption value of 40 bits is provided for backward compatibility. If you believe you are licensed for stronger encryption, contact BEA Customer Support.
See Also
DMCONFIG
(5)
1506
ERROR: Error occurred during security negotiation - closing connection
Description
An error occurred during the security negotiation between gateways.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support with the exact error message.
1507
ERROR: Error occurred during security negotiation - closing connection
Description
An error occurred during the security negotiation between gateways.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support.
1508
ERROR: Error occurred during security negotiation - closing connection
Description
An error occurred during the security negotiation between gateways.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support.
1509
ERROR: Error occurred during security negotiation - closing connection
Description
An error occurred during the security negotiation between gateways.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support.
1510
ERROR: Unable to decode link level user data
Description
The Diffie-Hellman packet flows as a CARRAY during the initial establishment of a key. The system was unable to decode this packet.
Action
Contact BEA Customer Support.
See Also
GWTDOMAIN
1511
ERROR: Unable to decode link level user data
Description
The Diffie-Hellman packet flows as a CARRAY during the initial establishment of a key. The system was unable to decode this packet.
Action
Contact BEA Customer Support.
See Also
GWTDOMAIN
1512
ERROR: Unable to connect to remote domain domain_name
Description
The attempt to establish a connection to the remote domain domain_name failed.
Action
More details can be found from the definition of the error code for your particular network or contact BEA Customer Support.
1514
ERROR: Could not allocate a domain header
Description
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the gateway's message send routine, while trying to add the domains header.
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.
1515
ERROR: Unable to initialize encryption key
Description
The gateway is encountering an error initializing the APP_PW
encryption key during the initial protocol exchange.
Action
Check the preceding ULOG message(s) for information on why the APP_PW
encryption calls are failing.
1516
ERROR: Unable to encrypt challenge value
Description
The gateway, when attemping to encrypt the APP_PW
challenge value during initial protocol exchange, is encountering an error.
Action
Check the preceding ULOG message(s) for information on why the APP_PW
encryption calls are failing.
1517
ERROR: Unable to initialize encryption key
Description
The gateway, when attempting to initialize the encryption key during initial protocol exchange when security is DM_PW
, is encountering an error.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support with the exact error message.
1519
ERROR: Unable to intialize administration key for domain val
Description
The gateway is encountering an error initializing the DM_PW
encryption key during the initial protocol exchange.
Action
Check the preceding ULOG message(s) for information on why the DM_PW
encryption calls are failing.
1520
ERROR: Unable to decrypt challange from val
Description
The gateway failed to decrypt the challenge value during initial protocol exchange for APP_PW security.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support with the exact error message.
1521
ERROR: Unable to intialize administration key for domain val
Description
The gateway is encountering an error initializing the DM_PW
encryption key during the initial protocol exchange.
Action
Check the preceding ULOG message(s) for information on why the DM_PW
encryption calls are failing.
1523
ERROR: System encryption failed for domain val
Description
During initial protocol exchange between gateways, the gateway fails to encrypt the security ticket.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support with the exact error message.
1524
ERROR: System encryption failed for domain val
Description
During initial protocol exchange between gateways, the gateway fails to encrypt the security ticket.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support with the exact error message.
1525
ERROR: Unable to intialize administration key for domain val
Description
The gateway is encountering an error initializing the DM_PW
encryption key during the initial protocol exchange.
Action
Check the preceding ULOG message(s) for information on why the DM_PW
encryption calls are failing.
1526
ERROR: Unable to decrypt challange from val
Description
The gateway failed to decrypt the challenge value during initial protocol exchange for APP_PW security.
Action
This is an internal error with no associated user action. If the error persists, contact BEA Customer Support with the exact error message.
1527
ERROR: Unable to intialize administration key for domain val
Description
The gateway is encountering an error initializing the DM_PW
encryption key during the initial protocol exchange.
Action
Check the preceding ULOG message(s) for information on why the DM_PW
encryption calls are failing.
1529
ERROR: System encryption failed
Description
Getting the session key or initialization of encryption with the session key for the security exchange when a connection is being set up from a remote domain failed.
Action
Contact BEA Customer Support.
1530
ERROR: System encryption failed
Description
Encryption of ticket for the security exchange when a connection is being set up from a remote domain failed.
Action
Contact BEA Customer Support.
1531
ERROR: System encryption failed
Description
Encryption of ticket for the security exchange when a connection is being set up from a remote domain failed.
Action
Contact BEA Customer Support.
1532
ERROR: System encryption failed
Description
Encryption of ticket for the security exchange when a connection is being set up from a remote domain failed.
Action
Contact BEA Customer Support.
1534
ERROR: Validation of ticket failed
Description
The ticket sent from the remote domain was found to be invalid.
Action
Contact BEA Customer Support.
1535
ERROR: Channel binding security failure
Description
The channel binding information for the remote domain was not valid.
Action
Contact BEA Customer Support.
1536
ERROR: Attempt to send encrypted buffer to interoperating site
Description
Buffers encrypted with an explicit call to tpseal
or with
an auto-encrypt key cannot be sent to a site older than the TUXEDO
Emperor release.
Action
Do not configure services in older domains that might have encrypted buffer sent to them.
See Also
GWTDOMAIN
, dmconfig
, tpseal
,
tpkey_open
1537
ERROR: Attempt to send encrypted buffer to interoperating site
Description
Buffers encrypted with an explicit call to tpseal
or with
an auto-encrypt key cannot be sent to a site older than the TUXEDO
Emperor release.
Action
Do not configure services in older domains that might have encrypted buffer sent to them.
See Also
GWTDOMAIN
, dmconfig
, tpseal
,
tpkey_open
1538
ERROR: Signature verification fails to interoperating site
Description
Buffers signed with an explicit call to tpsign
or with
an auto-sign key are verified by the GWTDOMAIN
gateway
before being sent to older sites. However, a message failed its signature
verification.
Action
The signature may have expired, or it may be tampered. Check the security of the system, and investigate any failure audit points.
See Also
GWTDOMAIN
, dmconfig
, tpsign
,
tpkey_open
1539
ERROR: opcode (msg_hdr_opcode) received in invalid link state (state)
Description
The opcode for the received data cannot be determined. No further processing wil l occur on the action. See any surrounding messages for more information.
Action
Contact your BEA TUXEDO system Technical Support.
1540
ERROR: security plug-in returns EE_SEC_NOSPACE but has not requested more space
Description
An internal error occurred in the Domain gateway, while processing the security token related to the message it was handling.
Action
Contact your BEA TUXEDO system Technical Support.
1541
ERROR: security plug-in returns EE_SEC_NOSPACE but has not requested more space
Description
An internal error occurred in the Domain gateway, while processing the security token related to the message it was handling.
Action
Contact your BEA TUXEDO system Technical Support.
1542
ERROR: Unable to allocate space for domains header
Description
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the gateway's message receive routine, while trying to add the domains header.
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.
1543
ERROR: unable to allocate space for received token
Description
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the gateway's message receive routine, while trying to process the messages security token.
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.
1544
ERROR: Unable to decode received token
Description
The Domain Gateway library software detected an error while trying to receive a message. An internal function call to decode a security token returned a failure.
Action
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message.
1545
ERROR: Unable to decode received token
Description
The Domain Gateway library software detected an error while trying to receive a message. An internal function call to decode a security token returned a failure.
Action
This is an internal error with no associated user action. If the error persists, contact your BEA Customer Support with the exact error message.
1546
ERROR: unable to allocate space for received token
Description
An attempt to dynamically allocate memory from the operating system failed. This is occurring in the gateway's message receive routine, while trying to process the messages security token.
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.
1547
ERROR: Use -t server option to interoperate with sites older than 7.1
Description
A request from a site older than 7.1 arrived at a server. However, the
-t
servopts
option was not specified. In order to clo
se a possible security hole, the administrator must explicitly tell
the server that it is allowed to accept requests from older sites.
Action
If you wish to allow the server to interoperate with sites older than 7.1
then the CLOPT
for the server must contain -t
before t
he --
option.
See Also
servopts
1548
ERROR: Use -t server option to interoperate with sites older than 7.1
Description
A request from a site older than 7.1 arrived at a server. However, the
-t
servopts
option was not specified. In order to clo
se a possible security hole, the administrator must explicitly tell
the server that it is allowed to accept requests from older sites.
Action
If you wish to allow the server to interoperate with sites older than 7.1
then the CLOPT
for the server must contain -t
before t
he --
option.
See Also
servopts
1549
ERROR: Failed security validation with remote domain (domainid=domainid)
Description
A security exchange with the remote domain domainid did not succeed.
Action
Contact your BEA TUXEDO system Technical Support.
1550
ERROR: Failed security validation with remote domain (domainid=domainid)
Description
A security exchange with the remote domain domainid did not succeed.
Action
Contact your BEA TUXEDO system Technical Support.
1551
ERROR: Invalid message format
Description
The GWTDOMAIN
was unable to resize an internal message that
was being processed.
Action
Contact BEA Customer Support.
See Also
GWTDOMAIN
1552
ERROR: Invalid message format
Description
The GWTDOMAIN
was unable to resize an internal message that
was being processed.
Action
Contact BEA Customer Support.
See Also
GWTDOMAIN
1553
INFO: New connection from domain <domainid> accepted, drop old connection!
Description
The remote domain already connected to this local domain gateway. But local domain gateway still received a new connection request from remote domain. Domain gateway only allow one connection per remote domain, so drop the old connection.
Action
If this is expected, then no action is required. If this is not expected, then should check where the old connection and the new connection really came from.
1554
INFO: New connection to domain <domainid> established, drop old connection!
Description
The remote domain already connected to this local domain gateway. But local domain gateway still try to create a new connection request to remote domain and the request was successful. Domain gateway only allow one connection per remote domain, so drop the old connection.
Action
No action is required.
1556
WARN: Connection with remote domain <domainid> already exists, drop new connection request!
Description
Event though the remote domain already connected to this local domain gateway, a new connection request came from a remote domain using the same id. For various reasons, such as security, the connection negotiation failed, so the local domain gateway drop the new connection request.
Action
Potentially an unauthorized remote domain trying to gain access to local service or to disrupt normal service. If this is not expected, check where the request came from.
1558
WARN: Network error, drop reply message!
Description
The GWTDOMAIN
was unable to send an outbound message reply to a remote domain due to network connection failure.
Action
Check network connectivity. Contact BEA Customer Support.
1559
ERROR: MAX Network Context already reached, SHUTDOWN!
Description
The GWTDOMAIN
encountered and internal error.
Action
Contact BEA Customer Support.
1560
ERROR: Network Context Hanging on FD, SHUTDOWN!
Description
The GWTDOMAIN
encountered and internal error.
Action
Contact BEA Customer Support.
1561
ERROR: Network send error, drop message!
Description
The GWTDOMAIN
was unable to send a message to a remote domain due to network-related failure.
Action
Check network connectivity. Check domain configuration file. Contact BEA Customer Support.
1562
INFO: Stopped retrying domain (domainid=domainid)
Description
The connection has failed. Stopped retrying due to security negotiation failure or maximum retries are already attempted.
Action
Check the password entries configured on both the local and remote domains in the binary domains configuration file. Check MAXRETRY
parameter in the DM_LOCAL_DOMAINS
entry.
See Also
DMCONFIG
(5)
1570
WARN: Looping event(val) detected!
Description
The GWTDOMAIN
encountered an unexpected internal error.
Action
Contact BEA Customer Support.
1571
WARN: setsockopt() for SO_KEEPALIVE failed!
Description
The GWTDOMAIN
failed to set KEEPALIVE option for the listening endpoint.
Action
Contact BEA Customer Support.
1572
INFO: Duplicated connection to remote domain <domainname>, drop new connection!
Description
The GWTDOMAIN
got duplicated connection to remote domain.
Action
Contact BEA Customer Support.
1574
WARN: DMKEEPALIVE is ignored because remote domain <name> does not support it.
Description
The remote TDOMAIN gateway is of older releases that does not support application level keepalive. There will be no KEEPALIVE
messages exchanged between local TDOMAIN and the remote TDOMAIN.
Action
Update the remote TDOMAIN to latest Tuxedo release, or remove DMKEEPALIVE from the configuration.
See Also
dmconfig
(5)
1575
WARN: Not receiving DMQUERY acknowledgement from RDOM name for the specified wait period, close connection
Description
The DMKEEPALIVE is configured for the session from local TDOMAIN to remote TDOMAIN name. The remote TDOMAIN name is not responding to the query in a timely fashion. The remote TDOMAIN is treated as went down.
Action
Check the health of the remote TDOMAIN and the network. If the remote TDOMAIN went down abnormally then reboot it. If it is because the network problem then fix the network to make remote TDOMAIN reachable.
See Also
dmconfig
(5)
1576
ERROR: Memory allocation failure during DMQUERY with RDOM name!
Description
Memory allocation failure while trying to send DMQUERY
to remote TDOMAIN name.
Action
Check the system memory usage. If the problem persist contact your BEA Customer Support.
See Also
dmconfig
(5)
1577
ERROR: Memory allocation failure during DMQUERY with RDOM name!
Description
Memory allocation failure while trying to send DMQUERY
to remote TDOMAIN name.
Action
Check the system memory usage. If the problem persist contact your BEA Customer Support.
See Also
dmconfig
(5)
1578
ERROR: Unable to presend DMQUERY
Description
Unable to allocate enough memory to store the network encoded DMQUERY
message.
Action
Check the system memory usage. If the problem persist contact your BEA Customer Support.
See Also
dmconfig
(5)
1579
ERROR: Encoding DMQUERY header failed
Description
Unable to allocate enough memory to store the network encoded DMQUERY
message.
Action
Check the system memory usage. If the problem persist contact your BEA Customer Support.
See Also
dmconfig
(5)
1580
ERROR: Memory allocation failure for encryption
Description
Unable to allocate enough memory to store the encrypted DMQUERY
message.
Action
Check the system memory usage. If the problem persist contact your BEA Customer Support.
See Also
dmconfig
(5)
1581
ERROR: Memory allocation failure for encryption
Description
Unable to allocate enough memory to store the encrypted DMQUERY
message.
Action
Check the system memory usage. If the problem persist contact your BEA Customer Support.
See Also
dmconfig
(5)
1582
ERROR: Network error on send of DMQUERY
Description
Encountered network error while sending the DMQUERY
message.
Action
Check the network and fix the problem.
See Also
dmconfig
(5)
1583
WARN: ABORT THRESHOLD is required but the OS does not support it!
Description
The ABORT_THRESHOLD is configured but the underline OS does not support it.
Action
Remove ABORT_THRESHOLD from the configuration.
See Also
dmconfig
(5)
1584
ERROR: Setting ABORT THRESHOLD failed (rc=code)
Description
The sockets call to set ABORT_THRESHOLD failed with return code code.
Action
Check with system administrator with the allowed value you can set, and correct the DMCONFIG
file.
See Also
dmconfig
(5)
1585
WARN: Network send error, internal TDOMAIN hand shake terminated
Description
The GWTDOMAIN
was unable to complete initial hand shake with a remote domain due to network-related failure.
Action
Check network connectivity. Check domain configuration file. Contact BEA Customer Support.
See Also
dmconfig
(5)
1586
ERROR: Missing network configuration information for remote domain <rdom>.
Description
The network information for remote domain rdom is missing from DM_TDOMAIN
section in the DMCONFIG
configuration file. No OPEN CONNECTION
will be done for this remote domain.
Action
Correct the error in the configuration file.
See Also
dmconfig
(5)
1587
ERROR: Remote domain<rdom> accesses local domain<ldom> from illegal host <nwaddr>, connection refused!
Description
The remote domain rdom trying to access local domain ldom from a host that is not configured in the DMCONFIG
. The address is the illegal host is nwaddr.
Action
Check whether the DMCONFIG
configuration file for error. If there is no configuration error then check out the possible intruder.
See Also
dmconfig
(5)
1588
INFO: Stop retrying domain <domainid=domid>
Description
No more retrying connect to remote domain domid.
Action
Check the configuration file, DMCONFIG
, for possible mismatched configuration. If the configuration is correct then check the remote domain status, if necessary reboot the remote domain. Also looking for other message that might give hints on why the connect failed. When everything is in good order issue "co
" command using dmadmin
.
See Also
dmconfig
(5), dmadmin
1589
WARN: Remote domain<rdom> from illegal host <nwaddr> access local domain<ldom>, connection refused!
Description
The remote domain rdom trying to access local domain ldom from a host that is not configured in the DMCONFIG
. The address is the illegal host is nwaddr.
Action
Check whether the DMCONFIG
configuration file for error. If there is no configuration error then check out the possible intruder.
See Also
dmconfig
(5)
1590
WARN: Potential configuration error for remote domain<rdom> from host<nwaddr1> and host<nwaddr1>.
Description
Most likely there is a configuration error. There two remote GWTDOMAIN
gateways trying to access local domain, and they both are configured to be legal host to use that domain id. One of the host network address is <nwaddr1>, the other one is <nwaddr2>. Usually this is link level failover, at least the backup remote GWTDOMAIN
gateway is configured with CONNECTION_POLICY
equals to ON_STARTUP
.
Action
Correct the error in the configuration file.
See Also
dmconfig
(5)
1591
ERROR: Remote domain<rdom> from illegal host <nwaddr> access local domain<ldom>, connection refused!
Description
The remote domain rdom trying to access local domain ldom from a host that is not configured in the DMCONFIG
. The address is the illegal host is nwaddr.
Action
Check whether the DMCONFIG
configuration file for error. If there is no configuration error then check out the possible intruder.
See Also
dmconfig
(5)