I also see exceptions logged at info level in activemq.log which keep repeating as if kahadb is continuously trying to persist this message but unable to write due to the UTF restriction...Below is the log for the same
activemq.broker.TransportConnection.Transport | Async Exception Handler 2013-03-19 21:12:15,863 | WARN | Transport Connection to: tcp://192.168.100.37:52603 failed: java.io.UTFDataFormatException: encoded string too long: 150073 bytes | org.apache.activemq.broker.TransportConnection.Transport | Async Exception Handler 2013-03-19 21:12:20,902 | WARN | Transport Connection to: tcp://192.168.100.37:52604 failed: java.io.UTFDataFormatException: encoded string too long: 150073 bytes | org.apache.activemq.broker.TransportConnection.Transport | Async Exception Handler 2013-03-19 21:12:25,950 | WARN | Transport Connection to: tcp://192.168.100.37:52605 failed: java.io.UTFDataFormatException: encoded string too long: 150073 bytes | org.apache.activemq.broker.TransportConnection.Transport | Async Exception Handler 2013-03-19 21:12:30,994 | WARN | Transport Connection to: tcp://192.168.100.37:52606 failed: java.io.UTFDataFormatException: encoded string too long: 150073 bytes | org.apache.activemq.broker.TransportConnection.Transport | Async Exception Handler 2013-03-19 21:12:36,032 | WARN | Transport Connection to: tcp://192.168.100.37:52607 failed: java.io.UTFDataFormatException: encoded string too long: 150073 bytes | org.apache.activemq.broker.TransportConnection.Transport | Async Exception Handler 2013-03-19 21:12:41,085 | WARN | Transport Connection to: tcp://192.168.100.37:52608 failed: java.io.UTFDataFormatException: encoded string too long: 150073 bytes | org.apache.activemq.broker.TransportConnection.Transport | Async Exception Handler 2013-03-19 21:12:46,154 | WARN | Transport Connection to: tcp://192.168.100.37:52609 failed: java.io.UTFDataFormatException: encoded string too long: 150073 bytes | org.apache.activemq.broker.TransportConnection.Transport | Async Exception Handler Regards, -Yogesh -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-8-0-Issue-with-HTTP-Connector-tp4664876p4664877.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.