made EventActionUtil more robust and NPE-safe for Event objects removed

import java.util.Map.Entry;

import java.util.Set;

import java.util.UUID;

import com.google.gwt.core.shared.GwtIncompatible;

import com.sap.sailing.domain.base.Event;

*/

@GwtIncompatible

public final class EventActionUtil {

private EventActionUtil() {

}

public static <T extends DTO> ResultWithTTL<T> withLiveRaceOrDefaultScheduleWithReadPermissions(SailingDispatchContext context,

UUID eventId, CalculationWithEvent<T> callback, T defaultResult) {

Event event = context.getRacingEventService().getEvent(eventId);

context.getSecurityService().checkCurrentUserReadPermission(event);

EventState eventState = HomeServiceUtil.calculateEventState(event);

if (eventState == EventState.FINISHED) {

* Triggers an update for all {@link RefreshableWidget}s that will have a timeout in the next 5 seconds.

*/

private void update() {

for (final RefreshHolder<DTO, SailingAction<ResultWithTTL<DTO>>> refreshable : refreshables) {

// Everything that needs refresh within the next 5000ms will be refreshed now.

// This makes it possible to use batching resulting in less requests.

@Override

public void execute() {

scheduled = false;

if (refreshables.isEmpty()) {

LOG.log(Level.FINE, "No refreshables found -> skipping refresh");

return;

LOG.log(Level.FINE, "Refresh not allowed to execute -> skipping refresh");

return;

}

Long nextUpdate = null;

for (final RefreshHolder<DTO, SailingAction<ResultWithTTL<DTO>>> refreshable : refreshables) {

if (refreshable.callRunning || !refreshable.provider.isActive()) {

nextUpdate = Math.min(nextUpdate, refreshable.timeout);

}

}

LOG.log(Level.FINE, "Nothing to auto update");

} else {

int delayMillis = (int) (nextUpdate - System.currentTimeMillis());

LOG.log(Level.FINE, "Scheduling auto refresh in " + delayMillis + "ms");

timer.schedule(delayMillis);

}

}

}

});

static final Duration ONE_DAY = ONE_HOUR.times(24);

static final Duration ONE_WEEK = ONE_DAY.times(7);

static final Duration ONE_YEAR = ONE_DAY.times(365); // well, leap years have 366 days, but this should be close enough...

long asMillis();

On sap-p1-1 two SSH connections are maintained, with the following default port forwards, assuming sap-p1-1 is the local master:

* tokyo-ssh.sapsailing.com: 10203-->10203; 5763-->rabbit-ap-northeast-1.sapsailing.com:5762; 15763-->rabbit-ap-northeast-1.sapsailing.com:15672; 5675:rabbit.internal.sapsailing.com:5672; 15675:rabbit.internal.sapsailing.com:15672; 10201<--10201; 18122<--22; 443:security-service.sapsailing.com:443; 8888<--8888; 9443<--9443

On sap-p1-2, the following SSH connections are maintained, assuming sap-p1-2 is the local replica:

A useful set of entries in your personal ``~/.ssh/config`` file for "off-site" use may look like this:

On sap-p1-1, if the operating system still runs and the failure affects only the Java process running the SAP Sailing Analytics, two SSH connections are maintained, with the following default port forwards, assuming sap-p1-1 is not running an SAP Sailing Analytics process currently:

* tokyo-ssh.sapsailing.com: 10203-->10203; 5763-->rabbit-ap-northeast-1.sapsailing.com:5762; 15763-->rabbit-ap-northeast-1.sapsailing.com:15672; 5675:rabbit.internal.sapsailing.com:5672; 15675:rabbit.internal.sapsailing.com:15672; 10201<--10201; 18122<--22; 443:security-service.sapsailing.com:443

On sap-p1-2 two SSH connections are maintained, with the following default port forwards, assuming sap-p1-2 is the local master:

* tokyo-ssh.sapsailing.com: 10203-->10203; 5763-->rabbit-ap-northeast-1.sapsailing.com:5762; 15763-->rabbit-ap-northeast-1.sapsailing.com:15672; 5675:rabbit.internal.sapsailing.com:5672; 15675:rabbit.internal.sapsailing.com:15672; 10202<--10202; 18222<--22; 443:security-service.sapsailing.com:443; 8888<--8888

So the essential change is that the reverse forward from ``tokyo-ssh.sapsailing.com:8888`` now targets ``sap-p1-2:8888`` where we now assume the failover master to be running.

On ``sap-p1-1`` an SSH connection to ``sap-p1-2`` is maintained, with the following port forwards:

So the essential changes are that there are no more SSH connections into the cloud, and the port forward on each laptop's port 5673, which would point to ``rabbit-ap-northeast-1.sapsailing.com`` during regular operations, now points to ``sap-p1-2:5672`` where the RabbitMQ installation takes over from the cloud instance.