You are right - that stack trace shows the client waiting for an acknowledgement from the server.
It could be caused by producer-flow-control kicking in on the server. If that's the case, the broker will log messages. Running out of memory on the broker could cause this too. Lost packets should not be an issue unless you have faulty network equipment and/or TCP/IP stack on your O/S (not likely at all). -- View this message in context: http://activemq.2283324.n4.nabble.com/producer-is-getting-stuck-tp4676567p4676606.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
