stucks on symbian

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Making socket operations asynchronous is one of the thing that we've
been wanting to do, but haven't had time to do this since there's
always other area that needs attention to. For now let me just create
a known issue entry for this: http://trac.pjsip.org/repos/ticket/987

But whether this would cure the stuck, frankly I don't know. My
feeling is it'll probably get stuck somewhere else.

Cheers
 Benny

On Fri, Nov 6, 2009 at 3:00 PM, nir elkayam <nir.elkayam at gmail.com> wrote:
> anyone has any idea about that?
>
> On Tue, Nov 3, 2009 at 10:51 PM, nir elkayam <nir.elkayam at gmail.com> wrote:
>>
>> hi all,
>>
>> I have added print to the log on error during the socket send on symbian.
>> when the program frezed for a few second, i check the log and saw that the
>> send returned with error -5105 but after few second it came back and i was
>> able to exit gracfully.
>> it seems that the stuck is done just like described in the wiki page. and
>> maybe that sometimes, the device gets over the problem and keep on going and
>> sometime it does not and the app stuck.
>>
>> maybe re-implementing the send to use active object (SetActive) instade of
>> the WaitForRequest can solve the problem of program stuck.
>> i think the change in UDP socket should be trivial and the port should
>> ignore other packet that comes when the send hasn't finished.
>> for tcp the change should not be so trivial,
>> other thing that can be done is to notify the app when the error occur so
>> that we disconnect and reconnect,
>>
>> what do you think?
>>
>>
>> On Wed, Oct 28, 2009 at 8:27 AM, nir elkayam <nir.elkayam at gmail.com>
>> wrote:
>>>
>>> hi,
>>>
>>> yes I have implemented the connection monitor, and when disconnecting
>>> throw the connection meneger all works fine, the app doesn't stuck,
>>> I saw the bottom part and because of that i think that it might be that
>>> the connection monitor doesn't catch the disconnection in time and so the
>>> send get called again,
>>>
>>>
>>>
>>>
>>> On Wed, Oct 28, 2009 at 7:59 AM, Benny Prijono <bennylp at teluu.com> wrote:
>>>>
>>>> On Tue, Oct 27, 2009 at 7:16 PM, nir elkayam <nir.elkayam at gmail.com>
>>>> wrote:
>>>> > hi all,
>>>> >
>>>> > I am making a pass over the send_rtp code:
>>>> >
>>>> > 1. it seems that the send rtp is done in blocking mode.
>>>> > 2. there is no check of the error code returned from the send.
>>>> >
>>>> > 2 things might be:
>>>> > 1. it take the os several second to identify disconnection and during
>>>> > this
>>>> > time the send cannot be completed.
>>>> > 2. the send does complete with error and later on we retry send
>>>> > another rtp
>>>> > packet, maybe the second time it get stuck..?
>>>> >
>>>>
>>>> It might be, but I don't think that's the case. Please read
>>>> http://trac.pjsip.org/repos/wiki/Symbian_AP_Reconnection especially
>>>> the bottom part.
>>>>
>>>> > any ideas on how to test/modifications?
>>>> >
>>>>
>>>> Have you implemented connection monitor, as the wiki suggests?
>>>>
>>>> ?-benny
>>>>
>>>> _______________________________________________
>>>> Visit our blog: http://blog.pjsip.org
>>>>
>>>> pjsip mailing list
>>>> pjsip at lists.pjsip.org
>>>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>>>
>>>
>>>
>>> --
>>> ??? ??????
>>> ??: 050-3930056
>>> nir.elkayam at gmail.com
>>>
>>
>>
>>
>> --
>> ??? ??????
>> ??: 050-3930056
>> nir.elkayam at gmail.com
>>
>
>
>
> --
> ??? ??????
> ??: 050-3930056
> nir.elkayam at gmail.com
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
>
>



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux