Hi,
We're using activemq as an mqtt broker. We're using OAuth2 for
authentication, which we've implemented via a brokerfilter that intercepts
connections, and checks whether the sender has a valid token. However, we'd
like to be able to do this whenever a client either publishes or consumes a
mess
Sounds like it is working as intended if I understand the usage you are
saying is happening. The client will refill the link credit in this
case every time a message is either read via (receive, receiver(timed)
or receiveNoWait) or when a message is handed off to an async consumer.
This happe
Yes,
confirmed.
Just setting 'log4j.logger.org.eclipse.jetty' to DEBUG breaks web console.
Looks like same problem with 5.13 and 5.11.3, have not checked further.
Mats
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Possible-loop-after-enabling-DEBUG-tp4719697p4719767.
Hi,
We need a high availability solution. To this extent I did some research on the
usage of ActiveMQ.
According to this documentation
(http://activemq.apache.org/replicated-leveldb-store.html) LevelDB store is no
longer supported.
Wasn’t LevelDB newer DB solution? Wasn’t it going to replace K
I'll check this next time the issue shows up. But I'm pretty sure that if the
connection is there on TCP level, it can be to nothing else than one of the
two backoffice brokers, since only these are defined in the connection URI
for the network connection. But anyways a good idea to check whether t
This is a copy paste error. It's randomize naturally.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-failover-transport-producers-consumers-work-on-different-hosts-tp4719747p4719752.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ConnectionURL
failover:(tcp://broker1:61616,tcp://broker2:61616)?andomize=false&jms.useAsyncSend=false&jms.dispatchAsync=false&maxReconnectAttempts=30&maxReconnectDelay=3000&jms.prefetchPolicy.queuePrefetch=1000
Scenario:
*Producer puts a message to the queue_1*
create connection
put message
c
Mats,
That's definitely an infinite loop: look at thread 3079.
If you configure org.eclipse.jetty.webapp.WebAppClassLoader at INFO but
everything else at DEBUG, does the problem disappear?
Tim
On Dec 5, 2016 2:38 AM, "mf" wrote:
> Thanks for reply Tim,
> following is a list of commands and ou
You'll probably want to use the priorityBackup option on the failover
transport, to ensure that any long-running connections return to server #1
when it comes back up.
http://activemq.apache.org/failover-transport-reference.html
If you're going to run two standalone brokers for this scenario, they
Hi,
maybe just copy-paste error or you have a typo with 'andomize', it should be
'randomize' (?) :)
Maybe off topic, but I think a network of brokers setup is sweet, running
two brokers with independant storage, in case one broker goes down and comes
back, the brokers would be able to pass message
Thanks for reply Tim,
following is a list of commands and output so should make it easy to
reproduce,
I'm not too used to debug java so list all output from jstack;
Mats
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Possible-loop-after-enabling-DEBUG-tp4719697p471974
11 matches
Mail list logo
