java.io.IOException: HTTP error: Service Temporarily Unavailable

JIRA | Robert Nguyen | 3 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0
  2. 0
  3. 0

    Mms Does Not Work With Saunalahti / Elisa (Finland) - Samsung Galaxy S4 Active Development - CyanogenMod Forum

    cyanogenmod.org | 11 months ago
    java.io.IOException: Cannot establish route to proxy /10.10.10.20
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Cyanogenmod's MMS application creates too large messages for my carrier (PL/PLAY, mnc/mcc:260/06), which in result are rejected. Carrier supports messages of size 300KB max, and CM has erroneous limit of 600KB. {code} D/Mms:app (16385): CarrierContentRestriction.checkMessageSize messageSize: 0 increaseSize: 0 MmsConfig.getMaxMessageSize: 614400 {code} which results in: {code} E/Mms:transaction(16385): Url: http://10.10.28.164/mms/wapenc E/Mms:transaction(16385): HTTP error: Request Entity Too Large E/SendTransaction(16385): java.io.IOException: HTTP error: Request Entity Too Large E/SendTransaction(16385): at com.android.mms.transaction.HttpUtils.handleHttpConnectionException(HttpUtils.java:296) E/SendTransaction(16385): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:282) E/SendTransaction(16385): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:174) E/SendTransaction(16385): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:152) E/SendTransaction(16385): at com.android.mms.transaction.SendTransaction.run(SendTransaction.java:123) E/SendTransaction(16385): at java.lang.Thread.run(Thread.java:841) E/SendTransaction(16385): Caused by: java.io.IOException: HTTP error: Request Entity Too Large E/SendTransaction(16385): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:205) E/SendTransaction(16385): ... 4 more E/SendTransaction(16385): Delivery failed. {code} If message is smaller, than 300KB then there are no problems sending it. Also there have never been any problems on stock fw. According to CYAN-1312 there supposed to be a setting controlling max msg size, but it doesn't seem to exists in my message's app (see screenshot) and I wasn't able to find it anywhere else. This issue is present for me since I've started using CM, i.e. 11.0-M8. Factory wipes don't help.

    JIRA | 2 years ago | Krzysztof Kundzicz
    java.io.IOException: HTTP error: Request Entity Too Large
  6. 0

    Cyanogenmod's MMS application creates too large messages for my carrier (PL/PLAY, mnc/mcc:260/06), which in result are rejected. Carrier supports messages of size 300KB max, and CM has erroneous limit of 600KB. {code} D/Mms:app (16385): CarrierContentRestriction.checkMessageSize messageSize: 0 increaseSize: 0 MmsConfig.getMaxMessageSize: 614400 {code} which results in: {code} E/Mms:transaction(16385): Url: http://10.10.28.164/mms/wapenc E/Mms:transaction(16385): HTTP error: Request Entity Too Large E/SendTransaction(16385): java.io.IOException: HTTP error: Request Entity Too Large E/SendTransaction(16385): at com.android.mms.transaction.HttpUtils.handleHttpConnectionException(HttpUtils.java:296) E/SendTransaction(16385): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:282) E/SendTransaction(16385): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:174) E/SendTransaction(16385): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:152) E/SendTransaction(16385): at com.android.mms.transaction.SendTransaction.run(SendTransaction.java:123) E/SendTransaction(16385): at java.lang.Thread.run(Thread.java:841) E/SendTransaction(16385): Caused by: java.io.IOException: HTTP error: Request Entity Too Large E/SendTransaction(16385): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:205) E/SendTransaction(16385): ... 4 more E/SendTransaction(16385): Delivery failed. {code} If message is smaller, than 300KB then there are no problems sending it. Also there have never been any problems on stock fw. According to CYAN-1312 there supposed to be a setting controlling max msg size, but it doesn't seem to exists in my message's app (see screenshot) and I wasn't able to find it anywhere else. This issue is present for me since I've started using CM, i.e. 11.0-M8. Factory wipes don't help.

    JIRA | 2 years ago | Krzysztof Kundzicz
    java.io.IOException: HTTP error: Request Entity Too Large

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      HTTP error: Service Temporarily Unavailable

      at com.android.mms.transaction.HttpUtils.httpConnection()
    2. com.android.mms
      SendTransaction.run
      1. com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:205)
      2. com.android.mms.transaction.Transaction.sendPdu(Transaction.java:174)
      3. com.android.mms.transaction.Transaction.sendPdu(Transaction.java:152)
      4. com.android.mms.transaction.SendTransaction.run(SendTransaction.java:113)
      4 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:841)
      1 frame