When the remote process gets killed by the OS,then you get a DeadObjectException.
Any process might get killed by the OS depending on system requirements. On Thu, Oct 1, 2009 at 10:22 AM, yukinoba <[email protected]> wrote: > > to dear all Android developers and fans, > > Does anyone ever meet a "android.os.DeadObjectException" thrown by a > remote service in Android? The problem I met is, the transact method > in the service binder interface threw this exception to me. > > I wrote a remote service, and called it through the service binder. > However, in the line of the binder interface (which is generated > automatically AIDL interface) "mRemote.transact(Stub.TRANSACTION_open, > _data, _reply, 0);", it threw a "android.os.DeadObjectException" to > me. > > I have read the definition of DeadObjectException, it says this > exception means "The object you are calling has died, because its > hosting process no longer exists.". However, I checked this with my > DDMS, and it showed the process of the remote service still exists. > > So, is there any other possible reason to make this exception > happened? or could someone here tell me how to avoid this exception? > > Thanks for all your kind. > > Best regards, > Nicholas > > > -- Thanks and Regards Gurudutt P.S. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
