So good news, it turns out if you enable debug logging there is already a check in place to log the full stack trace. Take a look at this page: http://activemq.apache.org/how-do-i-enable-debug-logging.html for instructions on how to enable debug and then you should get the full print out of the ArrayIndexOutOfBoundsException that you are getting.
On Tue, Jul 14, 2015 at 9:42 AM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > It's difficult to track down the cause based on what you have provided > because unfortunately the full stack trace is missing for the > ArrayIndexOutOfBoundsException. The broker needs to be updated to log the > full stack trace which I can update. I can let you know when the latest > snapshot has that change so you can try it again and hopefully have some > more information to help debug the issue. > > Also, I doubt many people here are familiar with using that PHP client. > Would it be possible to try your example with a different kind of client to > see if the issue still exists? The easiest to debug is if it is a Java test > case. > > On Tue, Jul 14, 2015 at 7:08 AM, roox_4000 <reza.mazar...@gmail.com> > wrote: > >> My project is very important and because of this problem it has been >> down. I >> asked many times from supporters, the answered once but it didn't help >> me. I >> really need to know how to solve the problem. >> I appreciate it if anybody can help. >> >> >> >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/ActiveMQ-MQTT-crash-when-subscribe-tp4698367p4699230.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > >
