GTalkSMS is unable to reconnect - "No response from Server" Exception

[GoogleCodeExporter]

What steps will reproduce the problem?
1. receive a call 
2. gtalksms tries to reconnect
3. gtalksms never reconnect

What is the expected output?
gtalksms reconnect.

What do you see instead?
gtalksms never reconnect, forcing kill the process and restart it to reconnect.

Additional informations:
GTalkSMS version = 2.1.1
Android OS version = 2.2
Phone model = HTC Desire

Paste GTalkSMS logs if they are relevant
(http://code.google.com/p/gtalksms/wiki/GenerateAppLog)

Original issue reported on code.google.com by e.po...@gmail.com on 28 Mar 2011 at 11:30

[GoogleCodeExporter]

Please enable debugLog and submit the log. Thank you.

Original comment by fschm...@gmail.com on 28 Mar 2011 at 1:04

• Changed title: Not reconnect after an call

[GoogleCodeExporter]

DebugLog enabled. For now no more worries reconnection.
I will send the log if the bug is reproduced ...

Original comment by e.po...@gmail.com on 29 Mar 2011 at 10:19

[GoogleCodeExporter]

Perfect. 
I bet that "No response from server" will show up in the logs. This is an 
asmack bug, that I lately run into, which prevented GTalkSMS from reconnecting. 
I am currently in the process of implementing and testing an workaround. Let's 
see if you have the same issue.

Original comment by fschm...@gmail.com on 29 Mar 2011 at 12:11

[GoogleCodeExporter]

Yes, "No response from server" show up in the logs. 

When this message appears in the log, the reconnection is impossible. Forcing 
stop gtalksms. Then kill the process (background process) so that the 
connection works again.

Original comment by e.po...@gmail.com on 30 Mar 2011 at 1:54

[GoogleCodeExporter]

Thanks for your feedback.

There is a bug in asmack that prevents us from reconnecting. It seems like the 
packet writer buffers are not properly cleared after an disconnect, which leads 
to a flush of old stream information to the server, violating RFC 3920.
Until this bug is fixed, we throw away the connection and create a new one when 
we hit this.

Original comment by fschm...@gmail.com on 30 Mar 2011 at 3:50

• Changed state: WaitingForRelease

[GoogleCodeExporter]

Original comment by fschm...@gmail.com on 30 Mar 2011 at 5:09

• Changed title: GTalkSMS is unable to reconnect - "No response from Server" Exception

[GoogleCodeExporter]

Fixed in v2.1.2

Original comment by Florent....@gmail.com on 3 Apr 2011 at 8:48

• Changed state: Fixed

[GoogleCodeExporter]

I think I'm still experiencing this (or a similar) bug. Using the Wifi-Network, 
then disabling it (the phone changes to mobile data), GtalkSMS has problems to 
reconnect.

I do not always need to kill the app, most of the time it reconnects after some 
unsuccessful attempts. The same issue happens when transitioning from 
mobile-data to Wifi-network.

I noticed, that there are not catched exceptions.

(Samsung Galaxy S Froyo/2.2, GTalkSMS v2.1.2)

Original comment by tommy.sp...@gmail.com on 5 Apr 2011 at 11:04

Attachments:

• data_to_wifi.txt
• wifi_to_data.txt

[GoogleCodeExporter]

All 3 exceptions are handled, they are just saved in the log. Notice the "xmpp 
disconnected due to error:" message before the stack trace.
It's normal that the first reconnect that results in a "No response from 
server" XmppExceptions fails. After that, you should see that GTalkSMS succeeds 
in creating the following connection(s). Please post debug logs if this is not 
the case.

Original comment by fschm...@gmail.com on 6 Apr 2011 at 6:31

[GoogleCodeExporter]

Original comment by fschm...@gmail.com on 25 Aug 2011 at 7:50

• Changed state: Deployed