System Messages: LIBGWT Catalog 1700-1799


1700	ERROR: Memory allocation failure.
	Description	Failed to allocate memory while receiving SSL data.
	Action	Make sure the computer system has enough system memory installed, and has enough vitural memory configured.

1701	INFO: Connection closed by peer.
	Description	The SSL connection is closed by remote GWTDOMAIN gateway.
	Action	No action required.

1702	INFO: Connection closed by peer.
	Description	The SSL connection is closed by remote GWTDOMAIN gateway.
	Action	No action required.

1703	*ERROR: remote domain domain_name* in release release does not support remote service name remote_service_name longer than length characters.**
	Description	The domain domain_name running in release does not allow the remote service name length to exceed length
	Action	Correct the value of remote_service_name with name less than or equal length.
	See Also	`dmconfig`(5)
1704	ERROR: Received an SSL connection, but the SSL is not configured.
	Description	Received SSL connection request from remote access point but local TUXEDO does not configure SSL.
	Action	Check the local TUXEDO application's DMCONFIG with proper NWPROTOCOL attribute.

1705	*WARN: Access Control List check failed for local event event_name.*
	Description	The cross domain event failed to pass the `ACL` setting for the specific local event(`DM_EVT_IN` entry).
	Action	If you really want this event to pass the `ACL` check, change the `ACL` setting in the corresponding entry in `DM_EVT_IN` section in `Bdmconfig` file, then restart the application. Or use `dmadmin` to change it, then restarting the application is not required.
	See Also	`dmconfig`(5), `dmadmin`(1)
1706	*WARN: Event does not match local event event_name.*
	Description	The cross domain event's event name failed to pass the `EVT_EXPR` setting for the specific entry in `DM_EVT_IN` section in `Bdmconfig` file.
	Action	If you really want this event to pass the `EVT_EXPR` check, change the `EVT_EXPR` setting in the corresponding entry in `DM_EVT_IN` section in `Bdmconfig` file, then restart the application. Or use `dmadmin` to change it, then restarting the application is not required.
	See Also	`dmconfig`(5), `dmadmin`(1)
1707	ERROR: Unable to obtain remote event information from shared memory.
	Description	The GWTDOMAIN server failed to retrieve event information for the cross domain event.
	Action	Make sure that the remote cross domain event(incoming event) has corresponding configured entry in `DM_EVT_IN` section in `Bdmconfig` file and the entry's `REVTNAME` is equal to remote cross domain event's `REVTNAME`.(It is configured in remote domain's `Bdmconfig` file).
	See Also	`dmconfig`(5)
1708	*ERROR: failed to get cross domain event name for event_name.*
	Description	The GWTDOMAIN server failed to retrive event name in the cross domain message for the cross domain event.
	Action	Contact Oracle Tuxedo Technical Support.

1709	*ERROR: Connection to domain_name* address ip_addr failed, Network error(errno).**
	Description	`GWTDOMAIN` tries to connect to a remote domain domain_name using the port number and IP address as sp ecified by ip_address failed with network error code specified. This can be caused by network failure, wrong IP a ddress or port number in the configuration, or the remote `GWTDOMAIN` not yet up and running, or the r emote `GWTDOMAIN` has not yet able to open the listening end, or the remote `GWTDOMAIN` ope ned different end point then what specified in the local domain configuration file.
	Action	Check the `NWADDR` parameters in the local and remote dmconfig files. Also check that the remote machi ne is running and the remote gateway is running. Check network connectivity between the two machines.

1710	*ERROR: Connection to domain_name* address ip_addr failed, Network error(errno).**
	Description	`GWTDOMAIN` tries to connect to a remote domain domain_name using the port number and IP address as sp ecified by ip_address failed with network error code specified. This can be caused by network failure, wrong IP a ddress or port number in the configuration, or the remote `GWTDOMAIN` not yet up and running, or the r emote `GWTDOMAIN` has not yet able to open the listening end, or the remote `GWTDOMAIN` ope ned different end point then what specified in the local domain configuration file.
	Action	Check the `NWADDR` parameters in the local and remote dmconfig files. Also check that the remote machi ne is running and the remote gateway is running. Check network connectivity between the two machines.