Let's say I set up a network of brokers, where each "node" is a master/slave
pair sharing a NFS file system. From my research I should set the brokerName
differently on master and slave, but I should set the brokerId the same on
master and slave am I correct?
>From my research brokerName is used
Thanks for your help Tim!
The system has been smooth since.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Can you elaborate on what functionality was identified as missing? We're
always looking to improve things so if there's a legitimate need/gap it's
worth exploring.
Justin
On Mon, Oct 23, 2017 at 1:00 PM, pypen wrote:
> We actually use more than 2 nodes, but still an even amount.
> About the p
We actually use more than 2 nodes, but still an even amount.
About the prime-time ready: A consultant told me that some functionality was
missing.
Maybe I will look into Artemis.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi everyone,
The ActiveMQ team is pleased to announce that Apache ActiveMQ 5.15.2
has been released.
A list of issues resolved in this release is available here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12341669
The Wiki page for the release is here:
http
> I DON'T want persistent messaging via KhahaDB (or jdbc). I don't want to
introduce a database, a NAS or shared folders (I'm on windows).
You could move to Artemis and use the network replication functionality
which doesn't use a database, NAS, etc. The only concern here is with
split brain whic
:)
You are right. And you are wrong.
I DON'T want persistent messaging via KhahaDB (or jdbc). I don't want to
introduce a database, a NAS or shared folders (I'm on windows).
I DO want in memory behavior similar to it, where two brokers share their
messages (in memory) so that if both brokers die, m
On 10/23/2017 09:46 AM, MillieretXavier wrote:
Hi all,
I have a question about the authentication mechanisme, I use Activemq 5.12.3
with Karaf.
I need an authentication between two application, I saw the handshake
mechanism for the autentication based on SASL. ActiveMq can do only
ANONYMOUS, or
On 10/23/2017 02:51 AM, billson wrote:
I'm not sure where to post, hopefully someone can advise as per Subject.
broken link#1
http://apache.apache.org/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/package-summary.html
in
JMX MBeans@http://activemq.apache.org/jmx.html
broken link#2
Hi Tim,
Thank you for your extensive reply. If I can get it to work by
hardcoding the mcNetworkInterface value first, I'm more than willing to
spend some additional time into getting a nicer permanent solution and
contributing this back to the ActiveMQ project.
However, I still don't have mu
Hi all,
I have a question about the authentication mechanisme, I use Activemq 5.12.3
with Karaf.
I need an authentication between two application, I saw the handshake
mechanism for the autentication based on SASL. ActiveMq can do only
ANONYMOUS, or PLAIN TEXT (for my version).
My question is: the
We have a very strange problem with our ActiveMQ broker that happens when we
restart it after
running it for several months. We have not been able to reproduce it
in-house. It only happens in
production at our customer's site. At this time we have seen this issue at
least three times.
What happens
*Where am I?*
Ubuntu 17 -> Queues -> accounting -> ID:shp-38553-1508757565190-1:1:1:1:1
-> Error!
*Error message:*
Exception occurred while processing this request, check the log for more
information!
What do you want to do next?
*Error message from log:*
2017-10-23 13:26:27,202 | WARN | |
or
13 matches
Mail list logo
