Closed Bug 1152531 Opened 6 years ago Closed 6 years ago

MMS data connection is never deactivated if MMS fails to send

Categories

(Firefox OS Graveyard :: RIL, defect)

x86
Linux
defect
Not set
normal

Tracking

(blocking-b2g:2.2+, firefox38 wontfix, firefox39 wontfix, firefox40 fixed, b2g-v1.4 unaffected, b2g-v2.0 affected, b2g-v2.0M affected, b2g-v2.1 affected, b2g-v2.1S affected, b2g-v2.2 fixed, b2g-master fixed)

RESOLVED FIXED
2.2 S10 (17apr)
blocking-b2g 2.2+
Tracking Status
firefox38 --- wontfix
firefox39 --- wontfix
firefox40 --- fixed
b2g-v1.4 --- unaffected
b2g-v2.0 --- affected
b2g-v2.0M --- affected
b2g-v2.1 --- affected
b2g-v2.1S --- affected
b2g-v2.2 --- fixed
b2g-master --- fixed

People

(Reporter: pgravel, Assigned: edgar)

References

Details

(Whiteboard: [caf priority: p2][CR 820234])

Attachments

(3 files, 1 obsolete file)

MmsService never tries to deactivates the MMS data call in some error cases, which results in the MMS data call remaining up forever.

The case that I was able to reproduce consistently is due to an error with ensureRouting (separate bug), in which case the MMS data call remain up forever because MmsService doesn't seem to do proper cleanup in some cases.

Snippet of log from when the failure occurs:
> I Gecko   : -@- MmsService: Got the MMS network connected! Resend the buffered MMS requests: number: 1
> I Gecko   : -@- MmsService: flushPendingCallbacks: 1 pending callbacks with status: 0
> I Gecko   : -@- MmsService: Failed to ensureRouting: Error: Failed to resolve 'proxy.mobile.att.net', with status: 2152398878
> I Gecko   : -@- MmsService: The sending status of sendTransaction.run(): -8
> I Gecko   : -@- MmsService: The returned status of sending transaction: aErrorCode: 4 aEnvelopeId: null
> I Gecko   : -@- MmsService: Marking the delivery state/staus is done. Notify sent or failed.
> I Gecko   : -@- MmsService: Sending MMS failed.
blocking-b2g: --- → 2.2?
Edgar, can you please check this bug?
blocking-b2g: 2.2? → 2.2+
Flags: needinfo?(echen)
(In reply to Ken Chang[:ken] from comment #1)
> Edgar, can you please check this bug?

Sure.
Assignee: nobody → echen
Flags: needinfo?(echen)
Hi pgravel, is it possible to share full log to us for investigating? Thank you.
Flags: needinfo?(pgravel)
Whiteboard: [CR 820234]
Whiteboard: [CR 820234] → [caf priority: p2][CR 820234]
Hi Edgar

The log I attached to bug 1152568 would serve as a valid log for this bug. But I don't think they would help much. The relevant point of failure is included in the description.

Basic scenario is:
1. data is down
2. try to send mms
3. mmsService call SetupDataCallByType('mms')
4. data is brought up
5. mms service is notified data is available, tries resolve mms proxy
6. proxy fails to resolve for some reason (in this case it's due to the problem you mentioned in bug 1152568)
7. due to failure, MmsService never calls DeactivateDataCallByType('mms')
Flags: needinfo?(pgravel)
Attached file mms_fail.log
This log is from bug 1152568.
Blocks: 1032097
Attached patch Patch, v1 (obsolete) — Splinter Review
Comment on attachment 8590668 [details] [diff] [review]
Patch, v1

Review of attachment 8590668 [details] [diff] [review]:
-----------------------------------------------------------------

Hi Bevis, may I have your review for this patch? Thank you.
Attachment #8590668 - Flags: review?(btseng)
Comment on attachment 8590668 [details] [diff] [review]
Patch, v1

Review of attachment 8590668 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good to me.
Thanks for having this quick fix.
Attachment #8590668 - Flags: review?(btseng) → review+
Rebase only.
Attachment #8590668 - Attachment is obsolete: true
Attachment #8591456 - Flags: review+
https://hg.mozilla.org/mozilla-central/rev/fac9c1f3729b
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.2 S10 (17apr)
Comment on attachment 8591456 [details] [diff] [review]
Patch,v2, r=bevis

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): 
User impact if declined: 
Testing completed: 
Risk to taking this patch (and alternatives if risky): 
String or UUID changes made by this patch:
Flags: needinfo?(bbajaj)
Attachment #8591456 - Flags: approval-mozilla-b2g37?
Comment on attachment 8591456 [details] [diff] [review]
Patch,v2, r=bevis

(In reply to Anshul from comment #13)
> Comment on attachment 8591456 [details] [diff] [review]
> Patch,v2, r=bevis
> 
> NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to
> better understand the B2G approval process and landings.
> 
> [Approval Request Comment]
> Bug caused by (feature/regressing bug #): 
> User impact if declined: 
> Testing completed: 
> Risk to taking this patch (and alternatives if risky): 
> String or UUID changes made by this patch:

v2.2 needs a rebased patch, I will attach it soon, and ask approval then.
Thank you, Anshul.
Attachment #8591456 - Flags: approval-mozilla-b2g37?
Patch for b2g37_v2_2.
Comment on attachment 8592070 [details] [diff] [review]
[b2g37_v2_2]  Patch, r=bevis

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
Bug caused by (feature/regressing bug #): bug 1032097.
User impact if declined: MMS connection is never deactivated if MMS fails to send due to ensureRouting error.
Testing completed: Manually test.
Risk to taking this patch (and alternatives if risky): Low
String or UUID changes made by this patch: None.
Attachment #8592070 - Flags: approval-mozilla-b2g37?
Flags: needinfo?(bbajaj)
Attachment #8592070 - Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
You need to log in before you can comment on or make changes to this bug.