I think you'd have better luck asking this question in a forum specific to
GRAYLOG.
Tim
On Tue, Jun 18, 2019, 3:06 PM Andres Tarallo wrote:
> Hello:
>
> I have sucesfully sent messages from SYSLOG to ApacheMQ. In the ApacheMQ
> console I can see the messages in a QUEUE I've created (TESTQUEUE).
Seth Pyle,
for the record I stumbled across another user with the same issue. it looks
like there is already a JIRA issue created:
https://issues.apache.org/jira/browse/ARTEMIS-2165 that issue links to a
couple SO questions around the same space. I will add your example test
case to that jira ticke
we are using Artemis 2.8.1 and we have 2 nodes in a cluster (Jgroup, TCP
ping, load balancing=On Demand). we build each queue and address on each
node and put address settings and security settings on each node (via the
jolokia http api). the two nodes are behind a single vip so each incoming
conne
Hello:
I have sucesfully sent messages from SYSLOG to ApacheMQ. In the ApacheMQ
console I can see the messages in a QUEUE I've created (TESTQUEUE).
I 'm lost when I have to configure Graylog Inputs. My Queue supports:
openwire,amqp,stomp,mqtt. I´ve tried Graylog availiable inputs without
success.
Hi JB,
I think it make a lot of sense to focus on this points and I will be
more than happy to contribute!
There is a very large community of users around the ActiveMQ 5.x and
it's still very widely use in production environment.
I'm not sure that the users actually understand the difference bet
So I will preface this by saying hopefully my comments are not taken the
wrong way and turn into a big fight but instead can lead to a productive
discussion about the next steps.
First, I'm certainly not opposed to anyone who wants to work on modernizing
and adding features to existing software.
Hi all,
I would like to discuss with you about the ActiveMQ 5.x roadmap.
Even if Artemis is there, the stack is different and we still have lot
of users on ActiveMQ, and, as a ActiveMQ 5.x fan and contributor, I
think it's worth to give a new "dimension" to ActiveMQ 5.x.
As all Apache projects,
I don't see why federation wouldn't work for you. It doesn't require
preconfigured addresses & queues. The address-match and queue-match
configuration parameters use wildcard matching [1]. As a quick test I ran
the "federated-queue" example (at
examples/features/federation/federated-queue) after re
For what it's worth, the broker is pretty much at the mercy of the
filesystem here. The broker attempts to acquire a file lock using standard
Java file APIs. If the filesystem allows those API calls to complete
normally (i.e. without throwing an exception) then the broker must assume
they were succ
Failover issues were due to inability to take the lock on the filesystem.
Moving to an external NFSv4 solved the problem.
Unfortunately, from logs this is not immediate. Actually, the backup server
says that it acquires the backup lock even if this is not true.
Thanks for help.
--
Sent from:
10 matches
Mail list logo
