Jeffrey, In an earlier email, you wrote, "I'm not sure if the Java application ever gets the exception, but if it is, then it's reconnecting quickly." That sounds to me like the problem is *not* happening for Java clients, yet your latest email says "Also, I beleive this happens for both C++ and for Java clients." Can you help reconcile those statements? If it is happening for Java clients, please describe what happens, give stack traces, etc.
If it's happening for Java clients too, that may make debugging this easier, since more people on this list use the Java clients and so more people might be able to offer insight or try to reproduce it. So that would be good to know. Tim On Wed, Jul 15, 2015 at 8:06 AM, jeffrey <jeffreyhasm...@hotmail.com> wrote: > The keystore and truststore are set in my init method right after the > activemq::library::ActiveMQCPP::initializeLibrary(); > > This works, sending and receiving for days or weeks before any issue. > > Where there is an issue, I recreate the ConnectionFactory, Connection, > Session, Consumer, Producer, and then Connection->start() immediately > throws > the same issue. > > Also, I beleive this happens for both C++ and for Java clients, but not > necessarilly at the same time. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/unable-to-reconnect-after-exception-Channel-was-inactive-for-too-long-tp4697843p4699338.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
