ActiveMQ fails to reconnect after "Could not accept connection" error

Issue: under unstable network conditions and/or network outages, ActiveMQ connection is not re-established following the error: Could not accept connection from tcp://hostname.domain.com:portNumber Any settings that could help with recovering from this error would be much appreciated. ActiveMQ

Re: ActiveMQ 5.13.3 Linux distro signature verification failed

I downloaded again today and it is fine now. Not sure what went wrong yesterday during the download - I had tried more than once then, too. Thanks very much for confirming that it was working outside of our environment. - Arkin On Thu, May 19, 2016 at 6:34 AM Timothy Bish

Re: ActiveMQ 5.13.3 Linux distro signature verification failed

On 05/18/2016 11:39 PM, Arkin Yetis wrote: Hi, After downloading the 5.13.3 Linux distribution, the MD5 and ASC verifications failed. I tried more than once. I used the following page to download: http://activemq.apache.org/activemq-5133-release.html Could someone confirm that the signature

Re: [Artemis, Qpid JMS] Connection limit

Robbie Gemmell wrote > Credentials in this case means a username and password. > > The logs suggest the server offered PLAIN and ANONYMOUS mechs, the > client couldnt do PLAIN because it had no user details to do it with, > and so it selected ANONYMOUS. Thanks, PLAIN with username and password

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

When checked using the Jolokia Rest APIs, I get same result ... enqueued message count on these topics show 0; so I guess the Jolokia Rest APIs also give only stats since the broker started last. -- View this message in context: