Hi, On my side. I was doing an integration test as I said earlier. As part of the integration test I was injecting a fault in the framework I am running the app within. Again my app is just reading from an MQTT topic, doing some processing and writing out in another topic. It turned out that as part of the recovery from the fault the MQTT client was not shut down properly so there were dangling threads left around. When the app was restarted it allocated new clients with the same ids as the ones that were still dangling and hence the constant retries and churning of threads. All on my side, nothing to do with ActiveMQ.
Thanks, M On Wed, May 24, 2017 at 7:27 AM, Tim Bain <tb...@alumni.duke.edu> wrote: > That feels to me like there might still be something wrong in your > configuration, and maybe it only works with those two older versions of > ActiveMQ and Paho because they don't include the code that would recognize > that something's not right. I'd like to see what if anything Martin can > tell us about how he figured out what was wrong in his code, in the hopes > that that might lead you to something that would be useful for you as well, > so hopefully he'll respond when he can. > > Tim > > On Tue, May 23, 2017 at 6:44 AM, aragoubi <aymen....@gmail.com> wrote: > > > Also I am connecting the client to the "ws://0.0.0.0:1883" port instead > of > > the "ws://0.0.0.0:61615" port. > > But even like this, with activemq 5.14.3 I still have the same problem > > "client disconnecting in one second". > > > > > > > > -- > > View this message in context: http://activemq.2283324.n4. > > nabble.com/Connection-to-activemq-broker-is-lost-within-one-second- > > tp4726204p4726442.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > >
