Databases
StackOverflow2013
Postsdbo
POHTTP Post completely exiting thread, no exception caught, or hangs forever
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHTTP Post completely exiting thread, no exception caught, or hangs forever
    primarykey
    data
    text
    <p>I knew my code was dying somehow because of the other symptoms, but even though I had try/catch around everything, there was never any message. I've now finally narrowed it down by use of successive output statements.</p> <pre><code> String line = null; try { final HttpParams httpParams = new BasicHttpParams(); HttpConnectionParams.setConnectionTimeout(httpParams, 30000); DefaultHttpClient httpClient = new DefaultHttpClient(httpParams); HttpPost httpPost = new HttpPost(url); postDebugMessage("GlobalApplication", "Info", "Executing httppost"); HttpResponse httpResponse = httpClient.execute(httpPost); postDebugMessage("GlobalApplication", "Info", "Getting entity"); HttpEntity entity = httpResponse.getEntity(); postDebugMessage("GlobalApplication", "Info", "Converting to line"); line = EntityUtils.toString(entity); //&lt;- the bad one postDebugMessage("GlobalApplication", "Info", "Conversion completed."); } catch (Exception ex) { // Any error occurring here we're going to state is // a network error. postDebugMessage("GlobalApplication", "Exception", ex.getStackTrace()[0].toString()); throw new NetworkNotAvailableException(ex.toString()); } </code></pre> <p>Based on my debug output statements, the line = EntityUtils.toString(entity) never completes, and no statement after that in the entire service thread executes...the whole thing just vanishes.</p> <p>I know that EntityUtils.toString() can throw 2 exceptions, an IOException and a ParseException, and I'm going to try and add those next, but shouldn't an overall Exception catch it?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRob
    1. USRob
    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
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COYes, the overall Exception catches it, so that is not the problem.
      singulars
      1. POHTTP Post completely exiting thread, no exception caught, or hangs forever
      1. USKaj
    2. COyep both extend java.lang.Exception and are catched by the try/catch block. Whats your url? and what should the response look like? can you ensure that the server responses what you expect?
      singulars
      1. POHTTP Post completely exiting thread, no exception caught, or hangs forever
      1. USStuck
    3. COI do actions on "line" further along. I now do an explicit check to see if line came out null from the EntityUtils.toString() call. I actually have those line operations surround by a try/catch (Exception), so I would think an NPE would also be caught later on.
      singulars
      1. POHTTP Post completely exiting thread, no exception caught, or hangs forever
      1. USRob
 

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