bug[ats_9NJGS]: Client arbitration hangs

Since this action is targed to only the arbitration case, the socket
timeout was only exposed on the acquire method call.  It may be worthwhile
analyzing timeouts for all http calls.

Change-Id: I91006c2d949d5a5590fc63e16efd699b5122bee3

1 files changed, 3 insertions, 1 deletions

diff --git a/plugins/org.eclipse.osee.framework.core.client/src/org/eclipse/osee/framework/core/client/internal/ArbitrationServer.java b/plugins/org.eclipse.osee.framework.core.client/src/org/eclipse/osee/framework/core/client/internal/ArbitrationServer.java
index e07c1bc15dc..2203c0127a3 100644
--- a/plugins/org.eclipse.osee.framework.core.client/src/org/eclipse/osee/framework/core/client/internal/ArbitrationServer.java
+++ b/plugins/org.eclipse.osee.framework.core.client/src/org/eclipse/osee/framework/core/client/internal/ArbitrationServer.java
@@ -29,6 +29,8 @@ import org.eclipse.osee.framework.logging.OseeLog;
 
 public class ArbitrationServer extends OseeServer {
 
+   private static final int ONE_SEC_TIMEOUT = 1000;
+
    public ArbitrationServer() {
       super("Arbitration Server");
    }
@@ -46,7 +48,7 @@ public class ArbitrationServer extends OseeServer {
                parameters);
 
          outputStream = new ByteArrayOutputStream();
-         result = HttpProcessor.acquire(new URL(url), outputStream);
+         result = HttpProcessor.acquire(new URL(url), outputStream, ONE_SEC_TIMEOUT);
          setAlive(true);
          set(Level.INFO, null, HttpUrlBuilderClient.getInstance().getArbitrationServerPrefix());
          if (result.getCode() == HttpURLConnection.HTTP_OK) {