Here is the source of that class in 5.11.1:
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/activemq-all/5.11.1/org/apache/activemq/util/ClassLoadingAwareObjectInputStream.java?av=f
If you look at line 112 (the one from your stack trace), you can see that
it doesn't log the err
Clients are running on older version : < 5.11.1
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
What specific version of 5.11 is your client running? The security fix that
added this check (https://issues.apache.org/jira/browse/AMQ-6013) was
back-ported to 5.11.3, so if you're using that version of 5.11 or later,
then you have that change.
Tim
On Tue, Sep 12, 2017 at 12:19 AM, khandelwalanu
I believe the problem is that your current configuration has your messages
expire after 24 hours on the DLQ, only to be deleted and sent to. the
DLQ. I believe this is what is referred to by the warning in the Setting
Expiration on Messages in the DLQ section of
http://activemq.apache.org/messa
Hi,
Currently ActiveMQ broker is using ActiveMQ v5.14 while clients are still
running on v5.11. In the client migration process, we are facing below
problem with ObjectMessages:
The cases when producer is migrated to 5.14 but consumer is still using the
older version(5.11) are failing and throwi
Hi,
Currently ActiveMQ broker is using ActiveMQ v5.14 while clients are still
running on v5.11. In the client migration process, we are facing below
problem with ObjectMessages:
The cases when producer is migrated to 5.14 but consumer is still using the
older version(5.11) are failing and throwi
Hi,
We are using REST to post data in to the queue. The application that posts
data do anything other than sending the payload data. In this case, ActiveMQ
needs the content-data to be set, otherwise we are not getting the payload
data. Is there a way to set the content type by default for the en
Are we talking about 204 No Content, or 404 Not Found? Your first sentence
seems to have put one error code and a different error message together,
though your last sentence makes it seem like you're talking about a 204.
What URL are you hitting when you get this response? And I assume you're
doin
That attribute was added in 5.6.0 under
https://issues.apache.org/jira/browse/AMQ-3634.
Tim
On Sep 11, 2017 1:00 PM, "bbuzzard" wrote:
> I'm using ActiveMQ-5.5.1 (Yes I know it's very old). I'm trying to set
> archiveCorruptedIndex to true, but I get the error message: "Attribute
> 'archiveCor
To be clear, you're asking about doing this in Artemis, not ActiveMQ 5.x,
right? What version of Artemis?
On Sep 11, 2017 2:48 PM, "Harrison Tarr" wrote:
> I just wanted to follow up: Does anyone know how to put an
> attribute/property on a message in an ActiveMQServerPlugin that I can then
> pu
Do you need to have access to messages published to the first broker when
it goes down? If so, you should be looking at a master/slave pair instead
of two active brokers.
If not, you should network the two brokers to allow messages published on
either one to be delivered to a consumer on any broke
I just wanted to follow up: Does anyone know how to put an attribute/property
on a message in an ActiveMQServerPlugin that I can then pull out of the message
in Camel?
Regards,
Harrison Tarr
-Original Message-
From: Harrison Tarr [mailto:harrison.t...@connexta.com]
Sent: Wednesday, Se
I'm using ActiveMQ-5.5.1 (Yes I know it's very old). I'm trying to set
archiveCorruptedIndex to true, but I get the error message: "Attribute
'archiveCorruptedIndex' is not allowed to appear in element 'kahaDB'.".
This is what I entered:
What am I doing wrong? Is
By using LevelDB, you're using an unsupported configuration. You have four
options:
1. Switch to a supported persistent store as I suggested.
2. Keep using LevelDB and live with this behavior.
3. Keep using LevelDB and use the source code to figure out yourself what's
wrong, and then fix it yourse
You could grab the ActiveMQ source code and set a breakpoint at the line
where the logging should be occurring and see whether you're actually
getting to that line.
Tim
On Sep 11, 2017 8:59 AM, "peakey" wrote:
> Hi all,
>
> I have a strange issue with AMQ, i have logging set to DEBUG so i can s
Hi all,
I have a strange issue with AMQ, i have logging set to DEBUG so i can see
messages being produced and consumed by external subscribers however one of
the subscribers is not registering the messages it consumes in the AMQ Log,
all other subscribers are.
It is consuming the messages but its
hi，
Added that: in peacetime, such as today, our system consumes 94 million
messages, only 12 such duplicate messages appeared.
原始邮件
发件人:youngzilyoung...@163.com
收件人:ActiveMQ usersus...@activemq.apache.org
发送时间:2017年9月11日(周一) 22:14
主题:Re: Message repetition consumption：Four consumers consume the
hi：
We currently have four consumers, so far, two consumers receive the same
message is the main, a small amount of three or four consumers received the
same message, due to the difference in receiving time in about 1ms, so I Doubt
the problem lies in the broker,the broker sends the same message
hi，
I confirm is two the same message, because their message id is the same, is not
only the message content is the same, there is no test of other ways to store,
because my way is to use a zookeeper + leveldb deployment, when because of
dirty data, leading to the master node and slave node freq
Also, I'd want to know if the two messages had the same JMSMessageID (i.e.
were they the same message, or were they two different messages with the
same content).
On Sep 11, 2017 7:50 AM, "Tim Bain" wrote:
> Do you see the same behavior if you switch to KahaDB or JDBC? As Tim Bish
> said on that
Do you see the same behavior if you switch to KahaDB or JDBC? As Tim Bish
said on that JIRA bug, LevelDB is no longer supported, so you're only going
to get a fix if you can demonstrate that it's still a problem if you switch
to one of the supported store types.
Tim
On Sep 11, 2017 7:05 AM, "youn
hi，all：
Does anyone have this problem：
Summary: Message repetition consumption：Four consumers consume the same queue
message, with two consumers receiving the same message at the same time,
receiving a gap of 1ms Key: AMQ-6807 URL:
https://issues.apache.org/jira/browse/AMQ-6807
broker version：5.
Hi all,
I have some concerns about the configuration of my spring application.
I have 2 brokers (one main and one failover) and I want my client to produce
messages to the first broker. It should go to the second one just in case
the first broker is down, and automatically go back to the first br
Hi all,I have some concerns about the configuration of my spring application.
I have 2 brokers (one main and one failover) and I want my client to produce
messages to the first broker. It should go to the second one just in case
the first broker is down, and automatically go back to the first broke
24 matches
Mail list logo
