I have already opened an issue AMQ-7453 with detailed description, logs and
examples, please, take a look:
https://issues.apache.org/jira/browse/AMQ-7453
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Thanks for testing that; it will help make sure that whoever works on a fix
focuses quickly on the right part of the code. Would you be able to submit
a bug in JIRA to capture the problem as you observed it? If you're able to
attach any config files that would make it easier to quickly reproduce th
On 3/27/20 10:00 AM, Dirkjan Ochtman wrote:
Hi there,
I'm still trying to build an AMQP RPC message flow. I have the request path
working and am now debugging the response path. In doing so, it seems that
the response message is correctly being sent over the expected channel, but
the broker seem
I appreciate the suggestion and I will go forward using the STOMP interface
since it works so well out of the box, so to speak. I've already been able
to get further with it and I'd rather keep making progress rather than
wrestling with setting up the REST server.
I was using REST because I have
Hi Jérôme,
Please let me know if you need help about that.
Regards
JB
> Le 27 mars 2020 à 14:10, Jérôme Barotin a écrit :
>
> Hi Jean Baptiste,
>
> > Did you take a look on message groups ?
>
> Of course, if I have just set a group specific for the batch and then set a
> property for exampl
I'm curious about why you're using the REST interface at all. In my opinion
a standardized protocol like STOMP would be a much better solution for the
types of clients that would typically want a REST interface. The main
problem with the REST interface is that it's non-standard. Once you write
your
Hi there,
I'm still trying to build an AMQP RPC message flow. I have the request path
working and am now debugging the response path. In doing so, it seems that
the response message is correctly being sent over the expected channel, but
the broker seems to die from an out of memory error. In tryin
Also, can you define "metadata" for your use-case? Are you talking about
just the message's headers/properties?
Justin
On Fri, Mar 27, 2020 at 4:21 AM Bummer wrote:
> Hello.
>
> I'd like to receive only metadata of each message and not the message
> payload itself in order to save quite a lot
Hi Jean Baptiste,
> Did you take a look on message groups ?
Of course, if I have just set a group specific for the batch and then
set a property for example called last_message ="yes" to the last
message of the batch (last_message = "no" for other message). And, in my
consumer, if I check the
Hi Jan,
there isn't a way to receive only the metadata of a message.
It could be an enhancement, but I can't understand the purpose.
Could you share more information about your context?
What interface are you using to receive the messages?
Do you want skip the message body on consuming or browsi
Anyway, not sure it should be on the broker scope.
In Apache Camel, that’s exactly the purpose of aggregator strategy. Maybe you
can implement something similar as well (if you don’t use Camel) ?
Regards
JB
> Le 27 mars 2020 à 11:16, Jérôme Barotin a écrit :
>
> Hi,
>
> I've got the followi
Hi Jérôme,
Did you take a look on message groups ?
Regards
JB
> Le 27 mars 2020 à 11:16, Jérôme Barotin a écrit :
>
> Hi,
>
> I've got the following installation :
>
> * 2 ActiveMQ brokers installed in a Network of Broker with KahaDb
> persistence actived
> * I consume these message though
Hi,
I've got the following installation :
* 2 ActiveMQ brokers installed in a Network of Broker with KahaDb
persistence actived
* I consume these message thought the Spring's
DefaultMessageListenerContainer & the ActiveMQ's PooledConnectionFactory
I produce a batch of message every nigh
Hello.
I'd like to receive only metadata of each message and not the message
payload itself in order to save quite a lot of resources as I don't care
about the payload. Is it possible? From what I found the payload is
downloaded automatically even though I don't read it from the buffer.
Thank you
14 matches
Mail list logo