Hello,
we're testing the use of JBoss EAP 7.2 and its bundled Artemis resource
adapter for connecting to the Artemis cluster which consists of 6 nodes
total (3 master/slave pairs).
The current config is based on:
- https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_
app
Hello,
> The JVM flags used are: ... -Xss1024m
Are you sure about that -Xss1024m? That would set the thread stack size to a
monstrous 1GB. Perhaps you wanted to configure the initial heap size (-Xms)
there but made a typo? If that's really what's configured there try to
remove it or modify i
Hello,
there are various reasons why this may happen, but with your low amount of
threads - are you by any chance running this at 32-bit OS or at least JVM?
If yes, it isn't that difficult to achieve that with large heap sizes when
you're operating near the address space limitations.
In such ca
I'd also suggest to add something like "connection parameters reference"
listing all possible options at single place.
There's already something like that for the server configuration: http://
activemq.apache.org/artemis/docs/latest/configuration-index.html
But the client side connection parame
Hello,
in the Artemis docs:
https://activemq.apache.org/artemis/docs/latest/using-jms.html
(https://activemq.apache.org/artemis/docs/latest/using-jms.html)
https://activemq.apache.org/artemis/docs/latest/perf-tuning.html
(https://activemq.apache.org/artemis/docs/latest/perf-tuning.html)
it'
