Databases
StackOverflow2013
Postsdbo
POAndroid - Volley RequestFuture Timeout
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid - Volley RequestFuture Timeout
    primarykey
    data
    text
    <p>I'm experiencing a problem when using the <strong>RequestFuture</strong> class of volley. Actually it just stops at <code>wait(0)</code>; inside the <code>doGet()</code> Function in the RequestFuture class below and is never getting woken up by <code>onResponse</code> or <code>onErrorResponse</code> as I think it should.</p> <pre><code>private synchronized T doGet(Long timeoutMs) throws InterruptedException, ExecutionException, TimeoutException { if (mException != null) { throw new ExecutionException(mException); } if (mResultReceived) { return mResult; } if (timeoutMs == null) { wait(0); } else if (timeoutMs &gt; 0) { wait(timeoutMs); } if (mException != null) { throw new ExecutionException(mException); } if (!mResultReceived) { throw new TimeoutException(); } return mResult; } @Override public boolean isCancelled() { if (mRequest == null) { return false; } return mRequest.isCanceled(); } @Override public synchronized boolean isDone() { return mResultReceived || mException != null || isCancelled(); } @Override public synchronized void onResponse(T response) { mResultReceived = true; mResult = response; notifyAll(); } @Override public synchronized void onErrorResponse(VolleyError error) { mException = error; notifyAll(); } </code></pre> <p>This is the way i try to call all this above.</p> <pre><code> RequestFuture&lt;JSONObject&gt; future = RequestFuture.newFuture(); JsonObjectRequest myReq = new JsonObjectRequest(Request.Method.POST, url, jsonObj, future, future); requestQueue.add(myReq); try { JSONObject response = future.get(); } catch (InterruptedException e) { // handle the error } catch (ExecutionException e) { // handle the error } </code></pre> <p>I also tried replacing the line </p> <p><code>requestQueue.add(myReq);</code> </p> <p>with </p> <p><code>future.setRequest(requestQueue.add(myReq));</code></p> <p>or</p> <p><code>future.setRequest(myReq);</code></p> <p>which didn't help either.</p> <p>I already tried a usual Volley Request which worked just fine using this parameters, so that shouldn't be the cause. I guess the problem is, that the request is never actually executed, which is why the response listeners are never reached. Also tried <code>requestQueue.start()</code>, but didn't change a thing.</p> <p>I hope I explained my problem well enough, Thanks in advance!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChintan Rathod
    1. USuser2700475
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid - Volley RequestFuture Timeout
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POAndroid - Volley RequestFuture Timeout
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy are you trying to use RequestFuture? Can you share your use cases?
      singulars
      1. POAndroid - Volley RequestFuture Timeout
      1. USbogdan
    2. COWell problem I was facing is that i have three requests and the last of these three relies on the response of the first two requests. I already tried using different RequestQueues, but it always built all requests before starting them actually. So I never got to store the values of the first two so I could use them in the last request. My workaround at the moment is using custom event listeners to react on the responses of each request and start a new one once the one before is finished.
      singulars
      1. POAndroid - Volley RequestFuture Timeout
      1. USuser2700475
    3. COBut you already have 2 listeners for your Volley requests: the success listener and the error listener. You can fetch you result(s) in the success listener (and maybe set some custom value in your error listeners - depending on your needs) and just launch your subsequent requests from there - the success and/or error listeners. This way, your requests are synchronous and you don't have to bother implementing RequestFuture.
      singulars
      1. POAndroid - Volley RequestFuture Timeout
      1. USbogdan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload