SAS Digital Marketing includes functionality that enables you to pause the tracking servlet in order to perform maintenance of the underlying servers. You use the following commands to pause and resume the tracking servlet:

The servlet should cache any responses that are received during the paused period, and it should update the response files after the server activity is resumed. However, responses are not cached when they are received during a pause. Subsequently, the responses are lost because the response tables are not updated.

When this behavior occurs, the tracking-servlet (bess.war) log displays error messages similar to the following:

YYYY-MM-DD  ERROR [] [] [] CachedConnection  Bind unsuccessful.
java.rmi.RemoteException: Connection refused to host: xx.xx.xx.xx; nested exception is: 
	java.net.ConnectException: Connection timed out: connect

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Digital Marketing 6.3 is available at:

A fix for this issue for SAS Digital Marketing 6.1_M1 is available at: