[AMQ-3547] Calling Connection.close() on interrupted thread generates InterruptedIOException and leaks Connection

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 5.5.0
• Fix Version/s: 5.6.0, 5.13.0
• Component/s: JMS client
• Assignee: Timothy A. Bish
• Reporter: Martin Beránek
• Created: 18/Oct/11 08:13
• Updated: 27/Nov/15 14:13
• Resolved: 29/Oct/11 21:44

Description

Similar to https://issues.apache.org/jira/browse/AMQ-3529

call close() method on connection raise JMSException with InterruptedIOException as cause

Sample program:

public static void main(String[] args) throws Exception {
ConnectionFactory connectionFactory = new ActiveMQConnectionFactory("tcp://localhost:61616");
Connection connection = connectionFactory.createConnection();
Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
final Thread mainThread = Thread.currentThread();
new Thread() {

public void run() {
// this thread interrupt main thread after 1s
try

{ Thread.sleep(1000); }

catch (InterruptedException e) {
}
mainThread.interrupt();
};
}.start();

try

{ //wait for interrupt Thread.sleep(10000); }

catch (InterruptedException e)

{ Thread.currentThread().interrupt(); }

try

{ // this generate exception - bug??? connection.close(); }

catch (JMSException e)

{ e.printStackTrace(); }

// non-daemon thread responsible for connection still running, program
// will not terminate
}

when I remove line with Session obtain, everything works OK

Issue Links

• duplicates: AMQ-3529 Calling Thread.interrupt while in MessageConsumer#receive(timeout) generates java.io.InterruptedIOException and leaks Connection
• relates to: AMQ-2191 Incorrect handling of interruptions during commit or rollback of a transaction