Load balancer health checks are another possible source of connections that
close without completing a protocol handshake.
Tim
On Wed, Oct 2, 2019, 1:27 AM Jean-Baptiste Onofré wrote:
> Hi,
>
> Don't you have a disconnect from clients ?
>
> Are you using failover or directly the transport ?
>
>
ssue: Redelivery counter is not getting incremented when LastDeliveredSeqID >
BrokerSequenceId
Version tested : ActiveMQ 5.14.4 and 5.15.10 versions
Description:
I have created the two queues, one for sending requests and other for
receiving its response.
The steps for these queues are given belo
It looks like the directory got moved during the migration to the new site
and those links didn't get updated. Take out the "/5.8.0" out of the
failing URLs and should fix it until the site is updated.
Sorry for the trouble!
Justin
On Wed, Oct 2, 2019 at 1:32 PM Luc Hebert wrote:
> Hi there,
Hi there,
I'm doing some research relating to the following topic located here:
https://activemq.apache.org/how-can-i-see-what-destinations-are-used
However most links on this page are broken. Any alternate URLs for these
sections available?
Thank you!
*---*
*Luc Hebert*
Software Developer - W
I'm pleased to announce the release of ActiveMQ Artemis 2.10.1
Downloads are now available at:
https://activemq.apache.org/components/artemis/download/
Release notes:
https://activemq.apache.org/components/artemis/download/release-notes-2.10.1
Commit report:
https://activemq.apache.org/component
I'm using a Windows machine trying to send secure messages over SSL with
ActiveMQ, using the Apache NMS API for .NET and I really have no idea what to
do.
In the broker.xml I tried adding "sslEnabled=true" to the default acceptor:
tcp://0.0.0.0:61616?sslEnabled=true;tcpSendBufferSize=104857
Hi,
Don't you have a disconnect from clients ?
Are you using failover or directly the transport ?
Regards
JB
On 30/09/2019 14:49, Jose Manuel Vega Monroy wrote:
> Hi there,
>
>
>
> I can see a lot of log traces like this, which *around 2 seconds as
> difference each one, and different port*
Do you know what that IP is?
We have similar messages for multiple services that result in an admin
setting up port monitor (nagios, etc.) without the protocol specifics.
Similar messages typically show up when the service is being used by a
client that does not support the protocol, and inst