Hello
We are having similar problem in request/reply pattern with temp queue. we
are not getting response when we are using addDynamicallyIncludedDestination
on networkconnector with some queues.
so can anybody suggest what pattern to use if we are using in java code. for
example :
NetworkConnec
What i meant, is if you publish the rest war under "artemis-rest" using
you should therefor call
http://10.141.65.248:8080/artemis-rest/queues
instead of
http://10.141.65.248:8080/activemq-rest/queues
Br, A.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I'm still facing an issue with somewhat confusing behavior regarding message
expiration in the DLQ, maybe related to the memory issues I've been having. My
aim is to have messages routed to DLQ expire and dropped in one hour. To
achieve this, I've set an empty expiry-address and the appropriate
Can ActiveMQ support NMS and JMS at the same time as part of a single
interface.
There are two applications (both support ActiveMQ), both using different
connectors *App1 uses JMS* (written in Java) and *App2 uses NMS* written in
.NET.
I am trying to have a message from App1 using ActiveMQ to Ap
On 02/23/2018 05:43 AM, almin wrote:
Can ActiveMQ support NMS and JMS at the same time as part of a single
interface.
There are two applications (both support ActiveMQ), both using different
connectors *App1 uses JMS* (written in Java) and *App2 uses NMS* written in
.NET.
I am trying to have a
Couple of questions:
- Do you have any consumers on the DLQ?
- Are messages being sent to the DLQ by the broker automatically (e.g.
based on delivery attempt failures) or is that being done by your
application?
- How are you setting the expiry delay?
- Do you have a reproducible test-case?
J
Having the same issue. Did you figure out a solution?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Based on previous emails on this thread I believe he's already gotten past
the url issue.
Justin
On Fri, Feb 23, 2018 at 3:13 AM, Archibald wrote:
> What i meant, is if you publish the rest war under "artemis-rest" using
>
>
> you should therefor call
> http://10.141.65.248:8080/artemis-rest/
For ActiveMq 5.11, masterl/slave on NFSv4, is this broker configuration
invalid due to multiple shared lockers?
...
Hi,
Did you find any solution to this? I am facing the same issue.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi,
How did you resolve it? I am facing the same issue.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
11 matches
Mail list logo