Error messages

Error messages provide information about problems that have occurred during the operation of the gateway. You can use the information that they contain to resolve such problems.

The following table describes the error messages that the Socket Gateway generates.

Table 1. Error messages
Error	Description	Action
`Exhausted socket operations due to timeouts and NOT connection related errors. Discarding event data.`	The gateway cannot send or receive events because although it is connected to the target, the target is unresponsive.	This could be an indication that the target process is overloaded or unresponsive.
`IOException occurred, will wait for a new connection`	The gateway cannot send or receive events.	The gateway attempts to reconnect to the target using the reconnect function. If the gateway cannot reconnect check that the target is available. Ensure that the values specified for Gate.Socket.Host and Gate.Socket.Port are valid. Check if a firewall has blocked the gateway connection. To ensure that a firewall does not timeout TCP connections, set the Gate.Socket.KeepAlive property to TRUE.
`Platform : unable to find JRE lib dir on this platform`	The gateway does not run successfully if it does not have the minimum Java JRE library available.	Check the gateway dependencies in the description.txt file.
`Gate.Socket.BatchSize needs to be greater than 150.`	The gateway is running in batch mode and requires bigger batches to send events.	Increase the value specified for the Gate.Socket.Batchsize property.
`Gate.Socket.MaxBatchFiles needs to be greater then 1.`	The gateway cannot run in batch mode if the Gate.Socket.MaxBatchFiles property is set to 1 or less.	Set the Gate.Socket.MaxBatchFiles to a value greater than 1.
`Noticed a non batch file was in the directory. Do not alter this directory batch_file_name`	The file specified in the error message is not a batch file but appears in the batch file processing directory.	Remove the file from the batch directory and ensure no other processes are writing to that location. The following is the default location for the batch file. $OMNIHOME/log/G_SOCKET.log
`Received a timeout will attempt to retry the sending of the event data`	The gateway cannot send events because the connection to the target system is not available due to timeout.	Ensure that the target system is available. Ensure the correct hostname is specified in the Gate.Socket.Host property. Check if a firewall has blocked the gateway connection. To ensure that a firewall does not timeout TCP connections, set the Gate.Socket.KeepAlive property to TRUE.
`Rejected too many outstanding batch files need to be processed discarding batch events!!!!`	The gateway has received more events than it can handle during an IDUC flush. When this happens the gateway disregards events that occur after maximum storage has been reached.	To prevent this you can either increase the size of each batch or increase the number of batch files the gateway stores before sending to the socket. Check the values set for the following properties. Gate.Socket.BatchSize Gate.Socket.MaxBatch Files
`Re-run the gateway increasing the value for the property Gate.Socket.MaxBatchFiles`	The gateway puts an upper limit on the maximum batch files to prevent the disk quota from being exhausted.	If the maximum batch file limit is being exceeded because of a slow processing target socket server, you can use one of the following solutions. Delete the batch files in $OMNIHOME/var/`gateway_name`. (The default value is `G_SOCKET`.) Increase the value for the Gate.Socket.MaxBatchFiles property.
`Unable to remove log file`	The gateway cannot remove the log file.	Contact IBM software support.