Cleanup of redundant code in XMPPConnection.shutdown()

Description

solved a deadlock situation in XMPPConnection.shutdown() basically by calling socket.close() prior calling (reader|writer).close().

We need to determine if calling reader.close() and writer.close() is still needed. And it's very likely that the last call to socket.close() is now redundant.

The code parts should be dropped in future versions of SMACK if possible, they just remained there after fixing to ensure that this core change doesn't cause any regressions.

Environment

None

is related to

Activity

Show:
Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created January 30, 2013 at 9:34 PM
Updated August 17, 2014 at 1:11 PM
Resolved June 22, 2013 at 5:05 PM