I'm sure there are STOMP and/or AMQP clients out there which you can use
from PowerShell to send messages. However, ActiveMQ itself doesn't provide
such clients.
I recommend you check out stomp.py [1]. I know it supports the ability to
send messages from the command-line so you should be able to i
It looks to me like the call-timeout set on the isn't
applied to this specific connection. I opened this Jira [1] to resolve that.
In my view the bigger question is why is it taking 30 seconds for the
broker to respond in the first place? Perhaps there is a network problem of
some sort? Perhaps t
> Does Artemis cache both successful and unsuccessful logon attempts?
Yes. Otherwise, for example, a malicious client with bad credentials could
flood the back-end LDAP server.
> Should we have relatively long timeout to avoid overloading LDAP servers
or small timeout to avoid caching user logon
I've been investigating this more the whole week, I would really appreciate a
response. What I can see from inspecting the logs and metricbeat analysis, is
that the mssql connection in the first broker starts getting very slow, which
causes it to lose the master lease while messages are still in
Hi Team,
I would like to clarify the meaning of parameters used for authentication and
authorization in ActiveMQ Artemis:
authentication-cache-size
security-invalidation-timeout
Does Artemis cache both successful and unsuccessful logon attempts? Should we
have relatively long timeout to avoid
you are getting this issue because the CORE clients uses topology for
load
balancing by default, you can solve this issue disabling topology for
load
balancing, i.e.
useTopologyForLoadBalancing=false
Oh wow. I completely missed that even though it's in the docs. Thanks
for pointing that out.
