System Messages: LIBGWT Catalog 1300-1399
|
![]() |
![]() |
1300 |
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 your Oracle TUXEDO System technical support with the exact error message. | |
1301 |
ERROR: Unable to intialize administration key for domain val | |
|
Description |
The gateway is encountering an error initializing the |
Action |
Check the preceding ULOG message(s) for information on why the | |
1302 |
ERROR: Unable to decrypt challange from val | |
|
Description |
The gateway is encountering an error decrypting the |
Action |
This is an internal error with no associated user action. If the error persists, contact your Oracle TUXEDO System technical support with the exact error message. | |
1303 |
ERROR: Network error occurred during connection establishment | |
|
Description |
The gateway failed to connect to a remote domain. |
Action |
Check the | |
1304 |
WARN: No more remote domain address for remote domain name | |
|
Description |
The gateway was unable to establish a connection to the remote domain using the |
Action |
Check the | |
1305 |
INFO: A connection attempt has failed for val, trying new address val | |
|
Description |
The gateway was unable to establish a connection using the indicated entry in the |
Action |
To check why the first entry was unsuccessful, check the corresponding | |
1306 |
ERROR: Can not allocate network descriptor | |
|
Description |
The gateway has been notified that the network connection attempt has failed. While processing the failure, it detects that there are multiple |
Action |
Make sure the operating system parameters are set correctly for the amount of memoryon 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. | |
1307 |
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 your Oracle TUXEDO system Technical Support with the exact error message. | |
1308 |
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 your Oracle TUXEDO system Technical Support with the exact error message. | |
1309 |
ERROR: Memory allocation failure for encryption | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed while encrypting an outbound message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memoryon 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. | |
1310 |
ERROR: Memory allocation failure for encryption | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed while encrypting an outbound transactional message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memoryon 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. | |
1311 |
ERROR: Could not allocate a domain header | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed while trying to add the domains transaction header to an outbound message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memoryon 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. | |
1312 |
ERROR: Unable to remove domains header | |
|
Description |
The gateway is unable to strip the domains transaction header from an incoming mesages. |
Action |
This is an internal error with no associated user action. If the error persists, contact your Oracle TUXEDO system Technical Support with the exact error message. | |
1313 |
ERROR: Bad message from val. Closing file descriptor | |
|
Description |
The gateway received a poorly formatted message from the specified remote domain and is unable to recognize it. |
Action |
Check the ULOG of the remote domain for further diagnosis. | |
1314 |
ERROR: Unable to create initial action for remote domain | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed during the initial gateway protocol exchange. |
Action |
Make sure the operating system parameters are set correctly for the amount of memoryon 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. | |
1316 |
ERROR: Memory allocation failure for encryption | |
|
Description |
An attempt to dynamically allocate memory from the operating system failed while encrypting an outbound message. |
Action |
Make sure the operating system parameters are set correctly for the amount of memoryon 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. | |
1317 |
ERROR: Network error occurred during connection establishment | |
|
Description |
The gateway is using one of the alternate |
Action |
Check the | |
1318 |
ERROR: Local security type (val) does not match security type (val) of remote domain (domainid=val) | |
|
Description |
In order for two domains to communicate they must both have the same |
Action |
Change the | |
1354 |
INFO: Retrying domain (domainid=<domainid>) every retry_interval seconds | |
|
Description |
The initial connection attempt to the remote domain has failed. The gateway is now retrying the connection to the remote domain periodically, as specified by The retry interval is rounded up to be a multiple of |
Action |
No action required. | |
1360 |
ERROR: Cannot allocate nbytes bytes for maxpendingbytes information | |
|
Description |
An attempt to dynamically allocate memory from the operating system using
|
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. If necessary, shutdown and restart the GWTDOMAIN process that reported this error. | |
1361 |
INFO: Total pending bytes for all domains has dropped to nbytes, under half of request limit of limit; ndropped messages dropped | |
|
Description |
The number of bytes waiting to be sent to other domains has dropped to well below the system limit. Messages to other domains are no longer being dropped and are no longer close to being dropped. |
Action |
No action required. | |
1362 |
INFO: Total pending bytes for all domains has dropped to nbytes, under half of reply limit of limit; ndropped messages dropped | |
|
Description |
The number of bytes waiting to be sent to other domains for reply and TMS messages has dropped to well below the system limit on such bytes. Messages to other domains are no longer being dropped and are no longer close to being dropped. |
Action |
No action required. | |
1363 |
INFO: Total pending bytes for all domains has dropped to nbytes, under half of TMS limit of limit; ndropped messages dropped | |
|
Description |
The number of bytes waiting to be sent to other domains for TMS messages has dropped to well below the system limit on such bytes. Messages to other domains are no longer being dropped and are no longer close to being dropped. |
Action |
No action required. | |
1364 |
INFO: Total pending bytes for domain domname has dropped to nbytes, under half of request limit of limit; ndropped messages dropped | |
|
Description |
The number of bytes waiting to be sent to domain domname has dropped to well below the system limit on such bytes. Messages to other domains are no longer being dropped and are no longer close to being dropped. |
Action |
No action required. | |
1365 |
INFO: Total pending bytes for domain domname has dropped to nbytes, under half of reply limit of limit; ndropped messages dropped | |
|
Description |
The number of bytes waiting to be sent to domain domname for reply and TMS messages has dropped to well below the system limit on such bytes. Messages to other domains are no longer being dropped and are no longer close to being dropped. |
Action |
No action required. | |
1366 |
INFO: Total pending bytes for domain domname has dropped to nbytes, under half of TMS limit of limit; ndropped messages dropped | |
|
Description |
The number of bytes waiting to be sent to domain domname for TMS messages has dropped to well below the system limit on such bytes. Messages to other domains are no longer being dropped and are no longer close to being dropped. |
Action |
No action required. | |
1367 |
ERROR: Cannot open GW_MAXPENDINGBYTES_FILE "filename" (errno=errno) | |
|
Description |
The GWTDOMAIN process cannot open file filename indicated by the GW_MAXPENDINGBYTES_FILE environment variable. As a result, no restrictions on the number of outstanding bytes waiting to be sent will be enforced in the GWTDOMAIN process. |
Action |
The domain gateway will continue to operate normally, but its process size may grow if a large volume of pending messages accumulates in process memory. If it is important to avoid possible GWTDOMAIN process size growth, then shut down the GWTDOMAIN process, and either fix the problem with filename or fix the value of the GW_MAXPENDINGBYTES_FILE environment variable. Once this is done, reboot the GWTDOMAIN process. | |
1368 |
ERROR: Cannot allocate nbytes bytes for maxpendingbytes information | |
|
Description |
An attempt to dynamically allocate memory from the operating system using
|
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. If necessary, shutdown and restart the GWTDOMAIN process that reported this error. | |
1369 |
WARN: Remote domain name in line linenum of filename is longer than nchar characters | |
|
Description |
The GWTDOMAIN process encountered an excessively long remote domain name while parsing the GW_MAXPENDINGBYTES_FILE file filename. This line will be ignored. |
Action |
The domain gateway will continue to operate normally. No action is required unless the administrator determines that the name in line linenum was misspelled and also determines that it is critical that the maximum pending bytes feature be enabled for that domain. If this is the case, then shut down the GWTDOMAIN process, fix the problem in line linenum, and reboot the GWTDOMAIN process. | |
1370 |
WARN: Remote domain domname in line linenum of filename is not a configured remote domain name. Default values will be used for any domain dynamically configured with this name. | |
|
Description |
The GWTDOMAIN process encountered an unknown remote domain name while parsing the GW_MAXPENDINGBYTES_FILE file filename. This line will be ignored. |
Action |
The domain gateway will continue to operate normally. No action is required unless the administrator determines that the name in line linenum was misspelled and also determines that it is critical that the maximum pending bytes feature be enabled for that domain using non-default values. If this is the case, then shut down the GWTDOMAIN process, fix the problem in line linenum, and reboot the GWTDOMAIN process. | |
1371 |
WARN: Value for pending request bytes in line linenum of filename is outside of allowed range of minpending to maxpending or is non-numeric; ignoring this line | |
|
Description |
The GWTDOMAIN process encountered an invalid pending request bytes limit while parsing the GW_MAXPENDINGBYTES_FILE file filename. This line will be ignored. |
Action |
The domain gateway will continue to operate normally. No action is required unless the administrator determines that it is critical to fix the incorrect value in line linenum. If this is the case, then shut down the GWTDOMAIN process, fix the problem in line linenum, and reboot the GWTDOMAIN process. | |
1372 |
WARN: Value for pending request+reply bytes in line linenum of filename is outside of allowed range of minpending to maxpending or is non-numeric; ignoring this line | |
|
Description |
The GWTDOMAIN process encountered an invalid pending request+reply bytes limit while parsing the GW_MAXPENDINGBYTES_FILE file filename. This line will be ignored. |
Action |
The domain gateway will continue to operate normally. No action is required unless the administrator determines that it is critical to fix the incorrect value in line linenum. If this is the case, then shut down the GWTDOMAIN process, fix the problem in line linenum, and reboot the GWTDOMAIN process. | |
1373 |
WARN: Value npending for pending request+reply bytes in line linenum of filename is less than value for pending request bytes; resetting to minnpending | |
|
Description |
The GWTDOMAIN process encountered a request+reply bytes limit less than the corresponding request bytes limit while parsing the GW_MAXPENDINGBYTES_FILE file filename. This value has been reset as indicated. |
Action |
The domain gateway will continue to operate normally. No action is required unless the administrator determines that it is critical to fix the incorrect value in line linenum. If this is the case, then shut down the GWTDOMAIN process, fix the problem in line linenum, and reboot the GWTDOMAIN process. | |
1374 |
WARN: Value for pending request+reply+tms bytes in line linenum of filename is outside of allowed range of minrange to maxrange or is non-numeric; ignoring this line | |
|
Description |
The GWTDOMAIN process encountered an invalid pending request+reply+tms bytes limit while parsing the GW_MAXPENDINGBYTES_FILE file filename. This line will be ignored. |
Action |
The domain gateway will continue to operate normally. No action is required unless the administrator determines that it is critical to fix the incorrect value in line linenum. If this is the case, then shut down the GWTDOMAIN process, fix the problem in line linenum, and reboot the GWTDOMAIN process. | |
1375 |
WARN: Value npending for pending request+reply+tms bytes in line linenum of filename is less than 100000 + pending request+reply bytes; resetting to min_npending | |
|
Description |
The GWTDOMAIN process encountered a request+reply+tms bytes limit less than the corresponding 100000+request+reply bytes limit while parsing the GW_MAXPENDINGBYTES_FILE file filename. This value has been reset as indicated. |
Action |
The domain gateway will continue to operate normally. No action is required unless the administrator determines that it is critical to fix the incorrect value in line linenum. If this is the case, then shut down the GWTDOMAIN process, fix the problem in line linenum, and reboot the GWTDOMAIN process. | |
1377 |
WARN: Dropping message to domain domname; nbytes total pending bytes exceeds total request limit of limit | |
|
Description |
The domain gateway has dropped a message to domain domname because the corresponding limit has been exceeded. |
Action |
Monitor the system to determine if there is a network problem or if network traffic is much higher than usual, and take any corrective measures required. | |
1378 |
WARN: Dropping message to domain domname; nbytes total pending bytes exceeds total reply limit of limit | |
|
Description |
The domain gateway has dropped a message to domain domname because the corresponding limit has been exceeded. |
Action |
Monitor the system to determine if there is a network problem or if network traffic is much higher than usual, and take any corrective measures required. | |
1379 |
WARN: Dropping message to domain domname; nbytes total pending bytes exceeds total TMS limit of limit | |
|
Description |
The domain gateway has dropped a message to domain domname because the corresponding limit has been exceeded. |
Action |
Monitor the system to determine if there is a network problem or if network traffic is much higher than usual, and take any corrective measures required. | |
1380 |
WARN: Dropping message to domain domname; nbytes pending bytes exceeds request limit of limit | |
|
Description |
The domain gateway has dropped a message to domain domname because the corresponding limit has been exceeded. |
Action |
Monitor the system to determine if there is a network problem or if network traffic is much higher than usual, and take any corrective measures required. | |
1381 |
WARN: Dropping message to domain domname; nbytes pending bytes exceeds reply limit of limit | |
|
Description |
The domain gateway has dropped a message to domain domname because the corresponding limit has been exceeded. |
Action |
Monitor the system to determine if there is a network problem or if network traffic is much higher than usual, and take any corrective measures required. | |
1382 |
WARN: Dropping message to domain domname; nbytes pending bytes exceeds TMS limit of limit | |
|
Description |
The domain gateway has dropped a message to domain domname because the corresponding limit has been exceeded. |
Action |
Monitor the system to determine if there is a network problem or if network traffic is much higher than usual, and take any corrective measures required. |
![]() |
![]() |
![]() |