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
> Using JMeter I sent a total of 50.000 messages using 50 threads to my
servicemix which puts the messages on the Artemis broker. Next a bunch of
processes get a message, does it's work and puts it on the next queue
(/endpoint)
Also, make sure that each thread is using its own Session / Producer
when you send messages in paging, they get written into page and the
journal in case you send transactionally.
if you restart the system, or kill, in case you're sending paged.. the
record will be written on the page files but it may be lost from the
journal.
Once you restart the page-tx is not
Currently I'm able to start some load testing using Artemis; The load is
nowhere near what I expect to need, but that's currently not the issue.
Of course I test both Artemis performance and the producers / consumers. The
performance itself is not at stake though, there's plenty of room for