Do those exceptions have stack traces? Look for the first occurrence following a broker restart, since the Oracle HotSpot JRE will optimize away the printing of the stack trace after some number of times in a row where the same exception is thrown so you're looking for the first few occurrences before that happens.
Tim On Nov 2, 2016 6:51 AM, "Ajay Jindal" <ajay.ku...@adeptia.com> wrote: > Hi Tim, > > Thanks for your reply. > > We are reading this message in our Java application as a listener, and > after > reading saving it into a file. > Below is the code, how we are reading message: > String msgText = ((TextMessage) msg).getText(); > > Also we are getting bellow WARN in ActiveMQ logs and console > 2016-11-02 14:18:48,953 | WARN | > org.eclipse.jetty.util.Utf8Appendable$NotUtf8Exception: Not valid UTF8! > byte > F8 in state 0 | org.eclipse.jetty.util.UrlEncoded | qtp594322390-35 > 2016-11-02 14:18:48,953 | WARN | > org.eclipse.jetty.util.Utf8Appendable$NotUtf8Exception: Not valid UTF8! > byte > 73 in state 3 | org.eclipse.jetty.util.UrlEncoded | qtp594322390-35 > 2016-11-02 14:18:48,953 | WARN | > org.eclipse.jetty.util.Utf8Appendable$NotUtf8Exception: Not valid UTF8! > byte > 62 in state 3 | org.eclipse.jetty.util.UrlEncoded | qtp594322390-35 > 2016-11-02 14:18:48,953 | WARN | > org.eclipse.jetty.util.Utf8Appendable$NotUtf8Exception: Not valid UTF8! > byte > F8 in state 0 | org.eclipse.jetty.util.UrlEncoded | qtp594322390-35 > 2016-11-02 14:18:48,953 | WARN | > org.eclipse.jetty.util.Utf8Appendable$NotUtf8Exception: Not valid UTF8! > byte > 67 in state 3 | org.eclipse.jetty.util.UrlEncoded | qtp594322390-35 > 2016-11-02 14:18:48,953 | WARN | > org.eclipse.jetty.util.Utf8Appendable$NotUtf8Exception: Not valid UTF8! > byte > 73 in state 3 | org.eclipse.jetty.util.UrlEncoded | qtp594322390-35 > > Ajay > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Problem-with-UTF-8-encoded-characters-tp4718607p4718792.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
