DEFECT DESCRIPTION: I think there have some errors in refCount(In MmsService.js), please help to confirm it. 1. Send the first mms A , the refCount is zero in function acquire, if another mms B is sent before A send successful, the refCount will up to 1, then after A send successful, the refCount will decrease to zero in the function release, and there will set a delay to release MMS network (onDisconnectTimerTimeout), but mms B still not send successful (I think it's an error). If the onDisconnectTimerTimeout is called before B send success, here will occur an error, the second MMS unable send successful. 2. Send a mms A successful, send another mms B before onDisconnectTimerTimeout is called, if onDisconnectTimerTimeout is called before the mms B send successfull, then will occur an error, the mms B unable send successful. (I think it's an error that in onDisconnectTimerTimeout not judge refCount) 3. Continuously send mms, if some error occur in XHR， in xhr.onerror will call releaseMmsConnectionAndCallback, and in xhr.onreadystatechange will also call releaseMmsConnectionAndCallback, then refCount will be reduce twice, it's an error. REPRODUCING PROCEDURES: EXPECTED BEHAVIOUR: ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:

Clone from brother

Clone from brother

Clone from brother

Clone from brother

Clone from brother

Clone from brother

Clone from brother

Thanks for catching this! Really appreciate. After some thoughts, I think I'll still use the original bug 917167 to fix this issue since it's indeed causing a kind of failure of sending MMS. Really sorry for letting you open this bug again. I'll close this one when bug 917167 is fixed. Thank you!