From fa858ac5cf2c555d746b5bdf4a0a7ea2adfec3e4 Mon Sep 17 00:00:00 2001 From: guyben Date: Fri, 28 Jul 2017 10:24:00 -0700 Subject: [PATCH] Remove unneeded "requester" from publishDnsUpdates locking This is a quick fix we can hopefully get out fast before fixing the underlying problem. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=163485468 --- java/google/registry/dns/PublishDnsUpdatesAction.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/java/google/registry/dns/PublishDnsUpdatesAction.java b/java/google/registry/dns/PublishDnsUpdatesAction.java index bb0736ff8..83fda2c24 100644 --- a/java/google/registry/dns/PublishDnsUpdatesAction.java +++ b/java/google/registry/dns/PublishDnsUpdatesAction.java @@ -81,7 +81,7 @@ public final class PublishDnsUpdatesAction implements Runnable, Callable { // false. We need to make sure to take note of this error; otherwise, a failed lock might result // in the update task being dequeued and dropped. A message will already have been logged // to indicate the problem. - if (!executeWithLocks(this, getClass(), tld, timeout, lockName)) { + if (!executeWithLocks(this, null, tld, timeout, lockName)) { throw new ServiceUnavailableException("Lock failure"); } }