Hi Chris,
thanks for the update. Indeed it could be related to client code,
especially around tx/ack management.
Anyway, let me know if you need help, even on KahaDB ;)
Regards
JB
On 13/01/2020 19:13, cmathrusse wrote:
> Hey JB,
>
> We are still seeing this in our production environment but not
Hey JB,
We are still seeing this in our production environment but not quite so
frequently. It seems to be only occurring in certain parts of our code and I
don't have an explanation as to why but since it is tapering off I'm not
going to invest any more time into the issue. Especially since we ar
Hi Chris,
No, I'm not able to reproduce it, but I'm not sure I'm doing the right
use case.
Maybe you are on Slack to chat directly and move forward quicker ?
Thanks,
Regards
JB
On 08/01/2020 17:40, cmathrusse wrote:
> Hey JB,
>
> Just checking in to see if you have been able to reproduce or i
Hey JB,
Just checking in to see if you have been able to reproduce or if you have
found the cause of the issue.
Thanks for your assistance.
Chris
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Nudge, nudge Any news?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi JB,
Sorry to keep going on about this but did you have an opportunity to
reproduce this issue?
Thank you...
Chris
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi Chris,
Not yet started, it's on my TODO for today.
Sorry for the delay.
Regards
JB
On 25/11/2019 10:11, cmathrusse wrote:
> Hey JB,
>
> Just checking in to see if you have been able to reproduce or if you have
> found the cause of the issue.
>
> Thanks for your assistance.
> Chris
>
>
>
Hey JB,
Just checking in to see if you have been able to reproduce or if you have
found the cause of the issue.
Thanks for your assistance.
Chris
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hey JB,
Could using vm for the transport connector be an issue with the broker
being remote on a separate server? I have not attempted changing this to
tcp as of yet since I only just learned of this configuration.
Chris
On Tue, Nov 19, 2019 at 12:56 PM Jean-Baptiste Onofré
wrote:
> Hi,
>
> sa
Hi,
same behavior using the tcp transport connector instead of vm and
advisory enabled ?
I will try to reproduce tomorrow.
Regards
JB
On 19/11/2019 19:00, Christopher Mathrusse wrote:
> Hi JB,
>
> Yes, the broker does have schedulerSupport set to true.
> http://activemq.apache.org/schema/c
Hi JB,
Yes, the broker does have schedulerSupport set to true.
http://activemq.apache.org/schema/core";
brokerName="broker-vv"
advisorySupport="false"
dataDirectory="/data2/activemq-data/vv"
schedulerSupport="true"
schedulePeriodForDe
Hi Chris,
You are using tcp connection right ?
What's the provider URL you are using in the connection factory ?
In your activemq.xml scheduler support is enabled in the
element right ?
Regards
JB
On 19/11/2019 18:42, Christopher Mathrusse wrote:
> We are currently running ActiveMQ version 5.
We are currently running ActiveMQ version 5.15.3 for our broker within a
Docker container. The ActiveMQ client version was just upgraded to 5.15.10,
but we were experiencing the issue prior to the upgrade when our client was
running version 5.6.
We are constantly experiencing communication failure
13 matches
Mail list logo
