Thanks! Now for a extra layer
What if we have 3 clients
A B and C
A has a temp queue, B now has a temp queue.
A message is sent from A to B like you said but instead B takes the message
and forwards it to C.
B puts in the correlation ID from A and sets the replyto its own temp
queue, does
GitHub user alanprot opened a pull request:
https://github.com/apache/activemq/pull/301
AMQ-7056 - Fix AMQ3625Test and JaasNetworkTest Tests
Those tests were faling due:
Caused by: javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: No name
Typically, the best way to accomplish request/reply is to use a temporary
queue. Like this:
- JMS client A creates a temporary queue
- JMS client A produces message to request queue
- On that message, the temporary queue is set as the JMSReplyTo using
javax.jms.Message.setJMSReplyTo()
- JMS
Oddly enough, this same exact question was asked (and answered) 2 days ago
[1] by a user also named "Abhijith PA" but with a different email address.
Justin
[1]
http://activemq.2283324.n4.nabble.com/Backporting-host-verification-support-to-5-6-0-td4743547.html
On Wed, Sep 19, 2018 at 9:55 AM
> So if client 2 sends "hello" with a correlation ID of unique UUID to
server 1 when server 1 sends the response will the broker know to send the
message back to client 2.
No. As stated previously, the correlation ID is not used by the broker to
dispatch messages to clients. I'm not exactly
I'm sorry i guess my question was not clear. Basically what it boils down to,
is if a client sets a correlation ID that is unique and sends a message.
When the server responds will the broker know based on the correlation ID
which client sent the data. i.e
client/producer 1: 192.168.1.2
The correlation ID is not used by the broker to dispatch messages to
clients. The correlation ID is set by a client and can be used in a
client's selector to implement a request-response pattern. There's lots of
documentation about this on the Internet.
For what it's worth, messages are never
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2324
---
Github user asfgit closed the pull request at:
https://github.com/apache/activemq-artemis/pull/2318
---
GitHub user alanprot opened a pull request:
https://github.com/apache/activemq/pull/300
AMQ-7055 - Optimization on SequenceSet to prevent iterating through tâ¦
When the index file has a huge number of free pages and the broker is
starting up (loading the index) we end up in a
On 09/19/2018 10:43 AM, Abhijith PA wrote:
Hello.
The Debian LTS (jessie) have only activemq-5.6.0 in the archive. I was
wondering is it possible to backport TLS[1] feature to the 5.6.0 ?
After going through the codebase I found, none of the files that
changed for TLS support in latest release
Hello.
The Debian LTS (jessie) have only activemq-5.6.0 in the archive. I was
wondering is it possible to backport TLS[1] feature to the 5.6.0 ?
After going through the codebase I found, none of the files that
changed for TLS support in latest release is not present in 5.6. Does
someone
So i am reading and one thing I am trying to look for is. If i have a
multiple producers and multiple consumers. When the producer sends a message
with a correlation ID and the consumer receives the message and responds
back with the same correlation ID will the broker return the message back to
GitHub user wy96f opened a pull request:
https://github.com/apache/activemq-artemis/pull/2324
ARTEMIS-2092 fix first page messages lost on server crash bug
Reproduction steps:
1. Send messages(using non transactional session), ensure the queue enters
page mode and only one
14 matches
Mail list logo
