I'm able to reproduce this issue in a much simpler way. Instead of starting
up brokers from within my application, I am using a clustered activemq setup
with 2 instances as follows. Both instances share the same data directory so
that only one broker is active at a time.
broker-1 has the
Perhaps we could add this to the next 1.5.3, if you cherry-pick the fix in 1.x
On Mon, Feb 6, 2017 at 10:55 AM, Martyn Taylor wrote:
> Hi Francesco,
>
> It appears that there is a bug in the MessageImpl code that is not properly
> setting the endOfBodyPosition when the server
Hi Martyn,
great to know it!
Thanks a lot for your work.
Francesco
From: Martyn Taylor
Sent: Monday, February 6, 2017 4:55:37 PM
To: users@activemq.apache.org
Subject: Re: MQTT retained messages with weird characters
Hi Francesco,
It
it seems a result from a previous running broker. It means the TX is
not available on the journal and it will be ignored.. I think it's
safe since you had these issues while running the broker.
I would start fresh and re-run your tests.
On Mon, Feb 6, 2017 at 11:10 AM, mlange
Strangely, the situation is a bit complicated:
In a prior test I received messages that the broker could not start a thread
due to not having enough heap available. It would not even shutdown, because
it could not start the shutdown thread. Eventually the broker got killed,
which then was taken
Francesco,
Thanks for providing this information. I think there's a couple of things
going on and I'd like to work with you to create some reproducers, we could
have a chat IRC #apache-activ...@freenode.net and I'll see if I can
recreate your env / case in our test suite.
With the case above,
Hi Francesco,
It appears that there is a bug in the MessageImpl code that is not properly
setting the endOfBodyPosition when the server restarts (reads from journal)
and then there's a subsequent message copy (i.e. retain). I've enabled
correct pointer setting and added the fix to MQTT.
I'm
Two of the three instances of the error saying that the port was in use
were related to Jetty, but the third looked unrelated. Thanks for
clarifying that all three relate only to Jetty.
Tim
On Feb 6, 2017 7:34 AM, "All in" wrote:
Hi Tim,
I've created the JIRA :
Hi Tim,
I've created the JIRA : https://issues.apache.org/jira/browse/AMQ-6592.
To answer some of your questions, no data has to be running on the queues.
One thing i noticed is that if i disable the admin console by commenting out
the line: in the activemq.xml, the problem
will not show up.
I am using ActiveMQ in my application, which send and receive lot of request
through this queue. I see the following error in the logs
[ActiveMQ Transport: tcp://localhost/127.0.0.1:61616] WARN
org.apache.activemq.ActiveMQConnection - dispatch paused, waiting for
outstanding dispatch
I tried to set with your suggestion as below, however, performance is still
slow. Fortunately, I found another ways to improve that set
journalDiskSyncStrategy="periodic" and clear the /data before
start ActiveMQ. The performance can go to 1,000 msg/s with 2K message size.
Second way, use SSD
Does this question have anything to do with ActiveMQ? If not, you may want
to post it on the Camel and RabbitMQ mailing lists, or on StackOverflow.
On Feb 6, 2017 3:04 AM, "sumit" wrote:
> HI
>
> I was previously using file component and was able to successfully move a
HI
I was previously using file component and was able to successfully move a
file after processing to a desired folder.
Now I am listening for a Rabbitmq and want to make a file after processing
the mq message and then move that file to a specified folder as does the
move option in file
13 matches
Mail list logo