I've never seen anything like this on the mailing list, and the one project
where I've been directly involved in managing brokers used non-persistent
messaging exclusively so I've never seen it personally.
Here are a few crazy ideas of what might possibly cause the behavior you
described:
- As
Frans,
You provided stats for the ActiveMQ.Advisory.Producer and
ActiveMQ.Advisory.Consumer advisory topics, but the stats we'd really have
liked to see were the ones for the queue itself. For future
troubleshooting, I recommend you look at the stats on the actual queue (or
topic), since they give
You could also remove the files.. use a temporary folder that's used
for each test.
On Wed, Oct 25, 2017 at 2:03 PM, preben wrote:
> Thanks Justin. Will try it out
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
--
Clebert Suconic
Thanks Justin. Will try it out
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
You should be able to use the code I pasted previously (or some
approximation thereof) to get the functionality you're looking for. Have
you tried that out?
Justin
On Wed, Oct 25, 2017 at 10:59 AM, preben wrote:
> Actually I start and stop the broker between each test, but when running a
> se
Actually I start and stop the broker between each test, but when running a
series of tests it seems that the newly started broker picks up messages
produced in the previous test ?
I would have presumed, that it would get a clean broker. To work around this
I need the deleteAllMessages.
I like the
You could do something like this:
for (String queueName :
broker.getJMSServerManager().getActiveMQServer().getActiveMQServerControl().getQueueNames())
{
((QueueControl)broker.getJMSServerManager().getActiveMQServer().getManagementService().getResource(ResourceNames.QUEUE
+ queueName)).removeM
ActiveMQ 5.11
When using failover URLs like this in a network of brokers where
updateClusterClients=true, how is failover handled?
failover:(tcp://hydra:61616,tcp://orion:61616,tcp://omega:61616,tcp://bigmoma:61616)?randomize=false
The behavior we're seeing is that, upon initial connect, the fir
You could do it per queue...
What we do in our own testsuite.. is to stop the server and start the
server on each test.. and use small journal files.. so it starts
really fast.
There's even artemis-junit, that you could embed in your tests.. and
that would do that work for you.
Look into our te
Im switching from Activemq to Artemis and have to migrate some unittests
I got a activemq baseclass like ->
@Before
public void startEmbeddedBroker() throws Exception {
broker = new BrokerService();
TransportConnector connector =
broker.addConnector("tcp://localhost:61616");
There is a .NET client library for ActiveMQ 5.x that uses the OpenWire
protocol, which means that it should work for Artemis as well. That's
probably the easiest option. But you could also use STOMP or an AMQP
library if you had a reason to want to use those protocols instead of
OpenWire.
Tim
On
How is this different from your previous question?
On Oct 25, 2017 1:24 AM, "bhattacharyyasom"
wrote:
> Hello,
>
> I have the following scenario that i want to address using queuing. I am
> not
> very sure if this is feasible though.
> So today i have a .NET rest services developed on the WebAPI
In our application we use guava eventbus along with activemq to implement
event based requirements between two web applications. Events are being
published and subscribed by different components of thw two web
applications. For receiving a message published by a component of a
different web applica
Thank you very much for quelling my doubts whether this can be worked at all
!
Yes i have a very cursory idea of how the messaging works. So i will read up
on protocols and their differences.
I have one question though what is the recommended protocol for use with
.Net ?
--
Sent from: http://act
Hello,
I have the following scenario that i want to address using queuing. I am not
very sure if this is feasible though.
So today i have a .NET rest services developed on the WebAPI interface that
receives JSON messages and calls different database procedures with that
parsed data.
Recently i ca
15 matches
Mail list logo