Hi Christopher,
I'm working with Paul. I've created a small test to illustrate the issue.
The zip I have attached includes three classes in a zip of an Eclipse
project. Call the main method of RunTest to run the test. The activemq.xml
used is in the root directory of the project.
The test was run using an out of the box install of ActiveMQ 5.13.2 on
Windows.
The program will timeout after 51 messages and attempt to close the session.
It eventually locks in this line:
this.connection.syncSendPacket(info);
in the rollback method of the TransactionContext class.
We know we can get round this by making changes to the broker configuration
but we do not own this in our business scenario so we must be able to
terminate our producer independently of the broker.
We believe that by default the rollback should follow the same timeout as
the connection. MQCloseIssue.7z
<http://activemq.2283324.n4.nabble.com/file/n4710486/MQCloseIssue.7z>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Force-Producer-to-fail-when-blocked-by-slow-consumer-tp4710264p4710486.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
