mirror of
https://github.com/google/nomulus.git
synced 2025-05-01 12:37:52 +02:00
a45d3d3bc7
Having a log at the very begining of "our" code helped us find issues with App-Engine's dispatcher, where we could clearly see in the logs that "our" code started many seconds after the request came in. We now suspect there is something similar going on after the end of "our" code - where the reply is sent back many seconds after our code finished running. To make sure - we add a log statement at the very last line of "our" code, so we know exactly when it ended. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=219309962
78 lines
3.2 KiB
Java
78 lines
3.2 KiB
Java
// Copyright 2017 The Nomulus Authors. All Rights Reserved.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
// you may not use this file except in compliance with the License.
|
|
// You may obtain a copy of the License at
|
|
//
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
//
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
// See the License for the specific language governing permissions and
|
|
// limitations under the License.
|
|
|
|
package google.registry.module.frontend;
|
|
|
|
import com.google.appengine.api.LifecycleManager;
|
|
import com.google.common.flogger.FluentLogger;
|
|
import com.google.monitoring.metrics.MetricReporter;
|
|
import dagger.Lazy;
|
|
import google.registry.util.SystemClock;
|
|
import java.io.IOException;
|
|
import java.security.Security;
|
|
import java.util.concurrent.TimeUnit;
|
|
import java.util.concurrent.TimeoutException;
|
|
import javax.servlet.http.HttpServlet;
|
|
import javax.servlet.http.HttpServletRequest;
|
|
import javax.servlet.http.HttpServletResponse;
|
|
import org.bouncycastle.jce.provider.BouncyCastleProvider;
|
|
import org.joda.time.DateTime;
|
|
|
|
/** Servlet that should handle all requests to our "default" App Engine module. */
|
|
public final class FrontendServlet extends HttpServlet {
|
|
|
|
private static final FrontendComponent component = DaggerFrontendComponent.create();
|
|
private static final FrontendRequestHandler requestHandler = component.requestHandler();
|
|
private static final Lazy<MetricReporter> metricReporter = component.metricReporter();
|
|
private static final FluentLogger logger = FluentLogger.forEnclosingClass();
|
|
private static final SystemClock clock = new SystemClock();
|
|
|
|
@Override
|
|
public void init() {
|
|
Security.addProvider(new BouncyCastleProvider());
|
|
|
|
// If metric reporter failed to instantiate for any reason (bad keyring, bad json credential,
|
|
// etc), we log the error but keep the main thread running. Also the shutdown hook will only be
|
|
// registered if metric reporter starts up correctly.
|
|
try {
|
|
metricReporter.get().startAsync().awaitRunning(10, TimeUnit.SECONDS);
|
|
logger.atInfo().log("Started up MetricReporter");
|
|
LifecycleManager.getInstance()
|
|
.setShutdownHook(
|
|
() -> {
|
|
try {
|
|
metricReporter.get().stopAsync().awaitTerminated(10, TimeUnit.SECONDS);
|
|
logger.atInfo().log("Shut down MetricReporter");
|
|
} catch (TimeoutException e) {
|
|
logger.atSevere().withCause(e).log("Failed to stop MetricReporter.");
|
|
}
|
|
});
|
|
} catch (Exception e) {
|
|
logger.atSevere().withCause(e).log("Failed to initialize MetricReporter.");
|
|
}
|
|
}
|
|
|
|
@Override
|
|
public void service(HttpServletRequest req, HttpServletResponse rsp) throws IOException {
|
|
logger.atInfo().log("Received frontend request");
|
|
DateTime startTime = clock.nowUtc();
|
|
try {
|
|
requestHandler.handleRequest(req, rsp);
|
|
} finally {
|
|
logger.atInfo().log(
|
|
"Finished frontend request. Latency: %.3fs",
|
|
(clock.nowUtc().getMillis() - startTime.getMillis()) / 1000d);
|
|
}
|
|
}
|
|
}
|