Page History

...

GatewaySender Log Messages and Notifications of Interest

Startup

GatewaySender Cannot Connect to GatewayReceiver

Remote Locator Is Not Running

When the remote locator is not running, the local locator will log a message like below. This message will be logged for each remote locator configured the remote-locators property that is unreachableWhen a GatewaySender cannot connect to a remote GatewayReceiver, a message like below is logged.

[warning 2017/11/09 0911:2832:4448.977667 PST locator-ln-1 <Event<WAN ProcessorLocator for GatewaySender_ny_3>Discovery Thread> tid=0x4c0x54] ny: CouldLocator discovery task could not connect.

The attached AlertNotificationListener will log an alert like:

exchange locator information 10.118.20.102[10332] with localhost[10331] after 6 retry attempts. Retrying in 10,000 ms.

And the GatewaySender will log messages like below.

[warning 2017/11/09 11:39:44.314 PST ln-1 <EventAllNotificationListener received notification[source=DistributedSystem(2); type=system.alert; sequence number=9; time stamp=1510362355433; message=ny: Could not connect.; userData={AlertLevel=warning, Member=ln-1, Thread=Event Processor for GatewaySender_ny_30> tid=0x4c}]

Once the GatewaySender does connect to a remote GatewayReceiver, an info message like below is logged. This message contains the remote receiver's host and port as well as the number of failed attempts. Depending on what thread has been attempting to connect, it'll retry. For example, the AckReaderThread retries every second by default.

[info 2017/11/09 09:30:59.511 PST ln-1 <Event Processor for GatewaySender_ny_3> tid=0x4c] ny: Using Pooled Connection to 10.118.20.102:5382: Connection[10.118.20.102:5382]@439092143 after 1 failed connect attempts

or:

0x47] Remote locator host port information for remote site "1" is not available in local locator "localhost[10332]".

[severe[info 2017/11/09 11:1539:4544.931317 PST ln-1 <AckReaderThread for : Event<Event Processor for GatewaySender_ny_3>0> tid=0x820x47] GatewaySender "ny: Using Pooled Connection to 10.118.20.102:5470: Connection[10.118.20.102:5470]@1533322301 after 100 failed connect attempts

Remote Locator Is Not Running

When the remote locator is not running, the local locator will log a message like below. This message will be logged for each remote locator configured the remote-locators property that is unreachable.

[warning 2017/11/09 11:32:48.667 PST locator-ln <WAN Locator Discovery Thread> tid=0x54] Locator discovery task could not exchange locator information 10.118.20.102[10332] with localhost[10331] after 6 retry attempts. Retrying in 10,000 ms.

And the GatewaySender will log messages like below.

" could not get remote locator information for remote site "1".

The attached AlertNotificationListener will log alerts like:

AllNotificationListener received notification[source=DistributedSystem(2); type=system.alert; sequence number=17; time stamp=1510364889713; message=Remote locator host port information for remote site "1" is not available in local locator "localhost[10332]".; userData={AlertLevel=warning, Member=ln-1, Thread=Event[warning 2017/11/09 11:39:44.314 PST ln-1 <Event Processor for GatewaySender_ny_0>0 tid=0x47}]

AllNotificationListener Remote locator host port information for remote received notification[source=DistributedSystem(2); type=system.alert; sequence number=19; time stamp=1510364889715; message=GatewaySender "ny" could not get remote locator information for remote site "1".; userData={AlertLevel=severe, Member=ln-1, Thread=Event Processor for GatewaySender_ny_0 tid=0x47}]

GatewaySender Cannot Connect to GatewayReceiver

When a GatewaySender cannot connect to a remote GatewayReceiver, a message like below is logged.

[warning is not available in local locator "localhost[10332]".[severe 2017/11/09 1109:3928:44.317977 PST ln-1 <Event Processor for GatewaySender_ny_0>3> tid=0x470x4c] GatewaySender "ny": couldCould not get remote locator information for remote site "1"connect.

The attached attached AlertNotificationListener will will log alerts an alert like:

AllNotificationListener received notification[source=DistributedSystem(2); type=system.alert; sequence number=179; time stamp=15103648897131510362355433; message=Remoteny: locatorCould hostnot port information for remote site "1" is not available in local locator "localhost[10332]".; userData={AlertLevel=warning, Member=ln-1, Thread=Eventconnect.; userData={AlertLevel=warning, Member=ln-1, Thread=Event Processor for GatewaySender_ny_3 tid=0x4c}]

Once the GatewaySender does connect to a remote GatewayReceiver, an info message like below is logged. This message contains the remote receiver's host and port as well as the number of failed attempts. Depending on what thread has been attempting to connect, it'll retry. For example, the AckReaderThread retries every second by default.

[info 2017/11/09 09:30:59.511 PST ln-1 <Event Processor for GatewaySender_ny_03> tid=0x47}0x4c]AllNotificationListener received notificationny: Using Pooled Connection to 10.118.20.102:5382: Connection[10.118.20.102:5382]@439092143 after 1 failed connect attempts

or:

[info 2017/11/09 11:15:45.931 PST ln-1 <AckReaderThread for : [source=DistributedSystem(2); type=system.alert; sequence number=19; time stamp=1510364889715; message=GatewaySender "ny" could not get remote locator information for remote site "1".; userData={AlertLevel=severe, Member=ln-1, Thread=Event Processor for GatewaySender_ny_03> tid=0x47}]0x82] ny: Using Pooled Connection to 10.118.20.102:5470: Connection[10.118.20.102:5470]@1533322301 after 100 failed connect attempts

Ongoing

GatewaySender Loses Connection to GatewayReceiver

...