Hi HappyMan,
You're welcome!
That's good to know -- I figured the InactivityMonitor was enabled, good to
know that it was disabled. Enabling it will help I'm sure, you might need to
tweak some of the timeout values, etc, but, good luck and keep us posted!
-Justin
On 10/21/19, 3:30 PM,
Hi Justin,
Thank you ver much for your reply. It helps me to think in a right way (I
guess).
Not only I adjusted ActiveMQ broker. I checked broker file ActiveMQ.xml
again and find out that for mqtt transport connector was set parameter
"transport.useInactivityMonitor=false". It means that
Hi HappyMan,
So, architecturally speaking, this is really something that should be handled
at the client/application layer using your exception handling and
try/catch/finally logic. Your code should never be allowed to crash without
releasing the connection, even with a hard kill of the
Hi Jérôme,
Any help is welcome !
You can submit PR on https://github.com/apache/activemq-website.
Thanks,
Regards
JB
On 21/10/2019 09:22, Jérôme Barotin wrote:
> Hi,
>
> I'm currently reading a lot the Active MQ 5 documentation, I often see a
> brokens links or other small misprint.
>
> How
Hi,
Here the mirror of the ActiveMQ website on github:
https://github.com/apache/activemq-website
regards,
François
fpa...@apache.org
Le 21/10/2019 à 09:22, Jérôme Barotin a écrit :
> Hi,
>
> I'm currently reading a lot the Active MQ 5 documentation, I often see
> a brokens links or other
Hi,
I'm currently reading a lot the Active MQ 5 documentation, I often see a
brokens links or other small misprint.
How can I help you to update it ? I there a git repo with the
documentation source ?
Best,
--
*Jérome Barotin*
