Sep 6, 2008 7:46 PM
Dedlock during Smack disconnect
-
Like (0)
5078 Views
18 Replies
Latest reply:
Nov 7, 2011 1:30 AM by
Flow 
-
-
Do you think this is related to
SMACK-230and or should I create another issue?-
-
-
-
Thanks for your patch Kare. I needed to put the close() in a extra try-catch block, otherwise if there is an Exception in shutdownInput() it won't get called:
try {
socket.shutdownInput();
} catch (Exception e) {
// Ignore
}
try {
reader.close();
} catch (Exception e) {
e.printStackTrace();
}
This does fix the stalled threads and the memory leak when reconnecting the XMPPConnection, which is very helpfull for mobile (android) development. But the unexpected close() of the socket will throw exceptions in the PacketWriter and PacketReader class, which results in a unclean shutdown. I am not sure how big the impact is, but just doesn't seem to be a proper long-term solution.
I have an android app that uses (a)smack in an long running service. The deadlock prevents some threads from terminating, therefore they don't get garbage collected causing my service getting restarted by Androids ActivtyManager to reclaim memory. I am certainly looking for a solution of
SMACK-278, that's why I asked this also on stackoverflow. I will start an bounty for the answer as soon as possbile. Maybe will get some other ideas/input on how to solve this.You can find the the so.sx question here: http://stackoverflow.com/questions/7901303/how-to-solve-deadlock-in-smack-with-b ufferedreader-on-xmppconnection-shutdown
Flow
-
-
-
-
Yes, you're right. I created 
