Hi, The problem seems to be with the client API http://kenai.com/projects/jbosh , it could not send the update acknowledgement id, hence for the new response id is attached with old or first created acknowledgement id, on the server side Vesper performers check on dispatching the response to client by getting the response based on acknowledge id, if response is older than “1000” milliseconds then it raises the terminate response, so in this cases Vysper server raises the terminate response because the fetched response for acknowledgement id was older. On correction on client to send the acknowledge id equal to response id or less than one then it processing was proper, I am still test on it.
Summary: The response form Vysper seems to be solved based on client correction to send latest acknowledge id . Suggestion: Why can’t Vysper upcoming release get response on response id instead of acknowledge id, so client glitch does not affect the process of Vysper. Regards, Aruna On Fri, Sep 16, 2011 at 9:51 AM, aruna reddy <[email protected]> wrote: > Hi, > > I have attached the two logs vysper_server log and stanza log > > > On Thu, Sep 15, 2011 at 11:40 PM, Bernd Fondermann > <[email protected]> wrote: >> On Wed, Sep 14, 2011 at 09:15, aruna reddy <[email protected]> wrote: >>> Hi, >>> >>> When I use the TCP connection to Vysper 0.7 server the request and >>> response is like below >>> >>> >>> >>> Received packet : <iq id="Mo71Q-2" >>> to="[email protected]/9cb2f36e2d1841b28dfc51aee35a1da8" >>> type="result"><query xmlns="jabber:iq:roster"><item >>> jid="[email protected]" name="[email protected]" subscription="none" >>> ask="subscribe"></item></query></iq> >>> >>> Received packet : <presence id="Mo71Q-3" >>> to="[email protected]/9cb2f36e2d1841b28dfc51aee35a1da8" >>> from="[email protected]/9cb2f36e2d1841b28dfc51aee35a1da8"></presence> >>> >>> Waiting for packet id.Mo71Q-4 >>> >>> Received packet : <iq id="93c23199827545678835b21d31d5b114" >>> to="[email protected]/9cb2f36e2d1841b28dfc51aee35a1da8" type="set"><query >>> xmlns="jabber:iq:roster"><item jid="[email protected]" >>> name="[email protected]" subscription="none" >>> ask="subscribe"></item></query></iq> >>> >>> Received packet : <iq id="Mo71Q-4" >>> to="[email protected]/9cb2f36e2d1841b28dfc51aee35a1da8" >>> type="result"><query xmlns="jabber:iq:roster"><item >>> jid="[email protected]" name="[email protected]" subscription="none" >>> ask="subscribe"></item></query></iq> >>> >>> >>> >>> When I use the Bosh connection to Vysper 0.7 server the request and >>> response is like below >>> >>> >>> >>> Received packet : <iq id="084vQ-2" >>> to="[email protected]/f35d3c9eaff84f34ba5ac0b851ae75b5" >>> type="result"><query xmlns="jabber:iq:roster"><item >>> jid="[email protected]" name="[email protected]" subscription="none" >>> ask="subscribe"></item></query></iq> >>> >>> Waiting for packet id.084vQ-4 >>> >>> Received packet : <presence id="084vQ-3" >>> to="[email protected]/f35d3c9eaff84f34ba5ac0b851ae75b5" >>> from="[email protected]/f35d3c9eaff84f34ba5ac0b851ae75b5"></presence> >>> >>> Received packet : <iq id="1367aac10bcd476aa2a151a566e3dc28" >>> to="[email protected]/f35d3c9eaff84f34ba5ac0b851ae75b5" type="set"><query >>> xmlns="jabber:iq:roster"><item jid="[email protected]" >>> name="[email protected]" subscription="none" >>> ask="subscribe"></item></query></iq> >>> >>> No response from the server.: >>> >>> at com.infor.test.BoshTest.createEntry(BoshTest.java:130) >>> >>> at com.infor.test.BoshTest.main(BoshTest.java:75) >>> >>> >>> >>> Though I increased the time out huge I don’t see the response from >>> server when I used the bosh connection, tested it with other xmpp >>> (openfire) server, client works fine. >> >> Do you see anything in the server log? >> >> Bernd >> >
