Hello again,
I am experiencing with the configuration and I see now I still had some
misconceptions. I see now that:
- ha-policy is all about live and backup groups
- cluster-connections is all about linking those groups together
So, it looks like what I would like to do is setup two live server
Thanks again for the reply.
So, after your explanation, I think I understood it better and will
definitely try that.
Question now in my mind is: with the cluster connections, discovery and
broadcast groups configured, the session state will be shared between all
the nodes, correct? That being sai
> But can I configure a timeout for this instead of number of connections?
No.
The recommended option would be to use initial-connect-attempts and
reconnect-attempts and needed. If you need functionality beyond that then
I'd recommend writing a utility class yourself to catch the exceptions and
r
> I guess what I would really want is to have 2 live servers sharing the
same
> storage on the filesystem and if my load balancer tries a server that is
> killed for some reason it then sends the same requests to the other server
> and it works transparently, but I recognise that is not the Artemis
I all.
I'm trying to continue my troobleshooting..
I downgrade to activemq 5.5.1 because we used this version production and it
seems the problem is still observable.
With the old logger, I have a trace now: with a
concurrentModificationException.
Please, any help ?
mai 14, 2019 3:32:26 PM
org.a
Hello and thanks for your reply,
I guess what I would really want is to have 2 live servers sharing the same
storage on the filesystem and if my load balancer tries a server that is
killed for some reason it then sends the same requests to the other server
and it works transparently, but I recogni
Hello all,
I have a standalone Artemis 2.6.4 running and I am connecting to it using
JMS from the client of an embedded Artemis on Wildfly 13, so Artemis client
1.5.5.
My client code looks like this:
@Inject
@JMSConnectionFactory(JMSConnectionFactoryName.DEFAULT)
private JMSContext jmsContext;