Hi,
We have a two active data centre messaging solution with activemq running
master/slave/slave on gfs2. The activemq instances are connected with a
network of brokers between the datacentres so that messages follow consumers
on failover.
We are using version 5.13.2 and the system has been fast
Thanks. I'd prefer the clients to not have to do anything special.
Is there any way to intercept an inbound message and affect the
acknowledgement back to the producer so they know the send failed
immediately?
This doesn't necessarily have to be camel if there is another way to achieve
the same.
Hi,
I've configured a camel route intercepting an inbound message.
If something goes wrong when processing the camel route, I'd like to be able
to reject the incoming message in a way that the client knows that the
message hasn't been accepted.
If my route doesn't forward the message back to the
Hi,
>From the docs:
The broker camel...intercepts messages as they move through the broker
itself, allowing them to be modified and manipulated before they are
persisted to the message store or *delivered to end consumers*.
I can see how to intercept messages before they are persisted to the mess
Hi,
For every connection over SSL made to artemis I get this warning:
18:46:43,276 WARN [org.apache.activemq.artemis.core.client] AMQ212040:
Timed out waiting for netty ssl close future to complete
The message sends and follow up connections succeed. Is this anything to
worry about - apart from
Hi,
If the certificates are set in ActiveMQChannelHandler.channelRead then they
should be available to all protocols no?
E.g.:
Then we'll need a different ActiveMQSecurityManager depending on which
callback handler is needed, JaasCertificateCallbackHandler or
JaasCredentialCallbackHandler.
Che
So based on ActiveMQ 5, I want to grab the certificate from the
ConnectionInfo.transportContext.
I can get the certificate array in ActiveMQChannelHandler.channelRead, but
means I have to propagate it using bufferReceived.
Then in OpenWireConnection.bufferReceived I can setTransportContext on the
Hi,
Hoping to get some advice on adding a security plugin to Artemis.
We are using an Artemis 1.1.0 broker.
Client systems post messages to a common queue and listen for messages on a
client specific queue.
There will be thousands of client systems.
Each client should be able to write to the
Hi,
If I modify the example project: protocols/openwire/message-listener and
change the session to CLIENT_ACKNOWLEDGE and update onMessage to call
message.acknowledge(). If I terminate the process before it has acknowledged
the messages, then I get similar behaviour. The messages remain marked as
Hi,
We have an Artemis server (1.1.0) with a transacted consumer.
The consumer is an Apache Camel (2.15.2) route running in Karaf 3.0.4. We
are using the ActiveMQ 5.12.0 libraries.
Within the transaction, the message is marked as being delivered (i.e.
accessible from listDeliveringMessages), ho
If you could, that would be absolutely fantastic!!
Many thanks,
Steve.
Clebert Suconic wrote
> I will fix this on Monday. Ok?
>
> -- Clebert Suconic typing on the iPhone.
>
>> On Aug 21, 2015, at 12:45, slew77 <
> stephen.lewis77@.co
> > wrote:
>>
>&
;
>
> Perhaps you could build master and try it out before we release ?
>
> -- Clebert Suconic typing on the iPhone.
>
>> On Aug 21, 2015, at 06:37, slew77 <
> stephen.lewis77@.co
> > wrote:
>>
>> Hi,
>>
>> I have setup a client (Jm
Hi,
I have setup a client (Jmeter) using an Openwire connection to an Artemis
broker.
With one thread continually publishing and consuming messages, everything is
fine for 60 seconds, then the broker issues the messages:
11:31:42,665 WARN [org.apache.activemq.artemis.core.server] AMQ222061:
Cli
13 matches
Mail list logo
