Dear Pekka Pessi,

I am using nta api for handling stateless transactions from sofia sip stack
1.12.10 in my application.

In my application I am destroying the invite transaction (irq) after
receiving ack for 200 OK,
the ACK transaction (irq) immediately after receiving the ACK.
And that of BYE transaction (irq) after sending 200 OK.

I am using nta_incoming_destroy(irq) method to do the same.

1) But while i was running the load, Sofia stack is getting crashed with the
following assertion failure
    for a completely new request which may be invite or bye,
    (independent of the transaction for which i am destroying irq in the
application).

     sipng: nta.c:5438: incoming_queue: Assertion `*queue->q_tail == ((void
*)0)' failed.
     Aborted (core dumped)

     And from the GDB findings I observed that

     *queue->q_tail points to the irq which i was destroying in my
application.

2) From the api documentation it is clear that the destroyed irq should be
in disposable state up to the timer expires.
     Please tell me when exactly this timer expires. (i.e., the default
timer value )

3) Is there any way that i can put mutex locks in my application to avoid
this synchronization problem.

I am suspecting this behavior as bug in stack.
Kindly let me know if any other information is required to solve this
problem.

Thanks in advance,

With Love,
Kiran.
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel

Reply via email to