Oh, one other thing. @JmsListener is typically used with a
DefaultMessageListenerContainer, which interacts poorly with topics if the
subscription is non-durable because the DMLC typically disconnects and
reconnects for every message, allowing messages to be "lost" for
non-durable subscriptions. Se
On Mon, Apr 23, 2018 at 11:48 PM, pragmaticjdev wrote:
> Highly appreciate the detailed replies and the clarifications on
> distributed
> cache vs database.
> We are trying to build a distributed cache. I agree to all the inputs you
> shared for such a cache implementation. In summary it would me
Any thoughts on how to control the polling interval and other queries
mentioned below?
Thanks!
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
This is going to require a code change; you're not going to be able to
Spring-inject the fix you're looking for.
org.apache.activemq.transport.discovery.http.EmbeddedJettyServer.start()
creates its Server by calling new (no Spring injection), and the code of
that method doesn't provide any means t
@jbertram: 2.5.0
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
What version of Artemis are you using?
Justin
On Thu, Apr 26, 2018 at 5:00 AM, Archibald wrote:
> The more I search for answers by reading other threads the more I get the
> impression, that the whole replication strategy only works on your test
> cases (or single host) but not in a real clust
In general it's important to remember that although the broker and the
hawtio console can both use the same JAAS configuration (specified in
login.config) they don't necessarily support the same specific login
modules.
Justin
On Thu, Apr 26, 2018 at 11:33 AM, Justin Bertram
wrote:
> In the Art
In the Artemis broker the JAAS integration has code to get the certificate
from the remote connection and pass it through in the proper places. I
doubt the hawtio code has the same kind of logic to get the certificate
from the connection to the web server (assuming it's even possible). Taking
a qui
I have configured high available ActiveMQ cluster setup where ActiveMQ is
deployed on WebLogic server.
I have configured corosync and pacemaker for failover through VIP.
The problem I am facing is when I send 10 messages to active node and shut
it down, on the secondary node I didn't see any messag
I have configured high available ActiveMQ cluster setup where ActiveMQ is
deployed on WebLogic server.
I have configured corosync and pacemaker for failover through VIP.
The problem I am facing is when I send 10 messages to active node and shut
it down, on the secondary node I didn't see any messag
Thanks Tim.
I didn't know that ack messages are stored in the journal files as well. Now
it makes sense the logs and why the number of journal files are increasing.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
The more I search for answers by reading other threads the more I get the
impression, that the whole replication strategy only works on your test
cases (or single host) but not in a real clustered (multi host)
environment...
See
http://activemq.2283324.n4.nabble.com/H-A-colocated-replication-envi
I'm struggling to configure Artemis 2.4.0 management console to use the same
client certificate based JAAS realm.
CertLogin {
org.apache.activemq.artemis.spi.core.security.jaas.TextFileCertificateLoginModule
required
debug=true
org.apache.activemq.jaas.textfiledn.user="certif
Hi Justin,
After spending hours of reading through documentation and examples I finally
decided to
continue with the replication/colocate approach.
So I've started two brokers which should pair with each other using static
connectors.
true
1
-1
14 matches
Mail list logo
