Re: RE: ServerTransaction=null

Santosh,

Does this problem only happen at the beginning of the subscription? I 
recall something similar happening (this was quite a while back) if the 
1st NOTIFY was received before the 1st SUBSCRIBE response (from the 
presence server). I ended up sending the 200 OK for the NOTIFY 
statelessly - ((SipProvider) 
reqevent.getSource()).sendResponse(response) - which took care of it.

Becky

(... Neo-Ranga?...)
Santosh Kakde wrote:

>Hi,
>
>I tried by creating a new server transaction but in that case it is
>giving following exception:
>
>javax.sip.TransactionAlreadyExistsException: Transaction exists!
>        at
>gov.nist.javax.sip.SipProviderImpl.getNewServerTransaction(SipProvide
>rImpl.java:421)
>        at
>techmahindra.SeamlessAgent.processRequest(SeamlessAgent.java:505)
>        at
>gov.nist.javax.sip.EventScanner.deliverEvent(EventScanner.java:185)
>        at gov.nist.javax.sip.EventScanner.run(EventScanner.java:324)
>        at java.lang.Thread.run(Unknown Source)
>
>
>-----Original Message-----
>From: M. (Neo-Ranga) Ranganathan [mailto:[email protected]]
>Sent: Monday, September 18, 2006 7:57 PM
>To: Santosh Kakde
>Cc: [email protected]
>Subject: Re: ServerTransaction=null
>
>Hi
>
>You can create a new server transaction to handle your request by
>using the SipProvider. The SipProvider is the event source for your
>RequestEvent. You may want to look at examples/subsnotify
>
>Regards
>
>Ranga
>
>On 9/18/06, Santosh Kakde <[email protected]> wrote:
>  
>
>>Hi,
>>
>>
>>
>>I am getting Server Transaction = null some time in my application.
>>    
>>
>When
>  
>
>>application send the SUBSCRIBE message to presence server It sends
>>NOTIFY to my application. For sending 200 OK for NOTIFY message
>>application is trying to take server transaction from request event
>>    
>>
>i.e.
>  
>
>>requestEvent.getServerTransaction (), for this some time application
>>    
>>
>is
>  
>
>>getting server transaction =Null. Can u tell me the solution for this
>>    
>>
>&
>  
>
>>why server transaction is null.
>>
>>
>>
>>-santosh Kakde
>>
>>
>>
>>
>>    
>>
>========================================================================
>====================================================
>  
>
>>Tech Mahindra, formerly Mahindra-British Telecom.
>>
>>Disclaimer:
>>
>>This message and the information contained herein is proprietary and
>>confidential and subject to the Tech Mahindra policy statement, you
>>    
>>
>may
>  
>
>>review at <a
>>
>>    
>>
>href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahind
>ra.com/Disclaimer.html</a>
>  
>
>>externally and <a
>>
>>    
>>
>href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahind
>ra.com/Disclaimer.html</a>
>  
>
>>internally within Tech Mahindra.
>>
>>
>>    
>>
>========================================================================
>====================================================
>  
>
>
>
>--
>M. Ranganathan
>"There are two ways to write error-free programs; only the third one
>works." --  Alan Perlis
>
>============================================================================================================================
>
>Tech Mahindra, formerly Mahindra-British Telecom.
>
>Disclaimer:
>
>This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review at <a href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> externally and <a href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> internally within Tech Mahindra.
>
>============================================================================================================================
>
>_______________________________________________
>nist-sip mailing list
>[email protected]
>http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>
>  
>