Timothy Bish said that it may have something to do with the destination
lookup and that can be configured via the wireFormat... I have started a new
thread here:
http://activemq.2283324.n4.nabble.com/Need-help-configuring-wireFormat-for-Apache-NMS-Stomp-1-5-4-to-talk-to-HornetQ-td4686002.html
-
Timothy Bish said that it may have something to do with the destination
lookup and that can be configured via the wireFormat... I have started a new
thread here:
http://activemq.2283324.n4.nabble.com/Need-help-configuring-wireFormat-for-Apache-NMS-Stomp-1-5-4-to-talk-to-HornetQ-td4686002.html
-
Related to my other post:
http://activemq.2283324.n4.nabble.com/Stomp-Client-1-5-4-error-creating-subscription-to-topic-on-JBoss-HornetQ-Jboss-6-4-2-GA-td4685987.html
I put in a JIRA issue for the problem above and Timothy Bish replied:
HornetQ uses different destination names then the default o
It seems like you're having similar problems to the ones ahsanali is
having, so the questions I just asked him apply to you as well. Since you
haven't shared much info about your configuration, it's harder to suggest
where to look, but hopefully you can look through your endpoints and figure
out w
It looks like you're failing to get an HTTP connection in one of your
routes. Four of the six endpoints you listed use HTTP; have you been able
to figure out which of them is the one you're failing on, and whether
there's anything unusual about hitting that endpoint? When this fails, are
you proc
Have you tried attaching a debugger to the broker and setting a conditional
breakpoint (with the condition that the header in question is null) to see
better what's going on? I've had pretty good luck figuring out what
ActiveMQ is doing using that approach, so it might help you figure out why
it's
Sounds good; thanks for the explanation.
On Mon, Sep 29, 2014 at 4:17 AM, Gary Tully wrote:
> everything is possible! but they evolved independently, hence the overlap
> in functionality
>
> On 26 September 2014 16:02, Tim Bain wrote:
>
> > Would it be possible for the failover transport to use
Hi again,
as far as I understood (and believe I have observed it in our case) you
can use wildcards
to qualify the kahadb instance. The instance with no destination
qualification is the default
kahadb instance.
Best regards
Andreas
On 29/09/14 14:56, petrk wrote:
That is an interesting solu
Hi again,
the ActiveMQ gods may correct me, but the acknowledgement mode has nothing
to do with how the messages are actually dispatched. As I said before -
the easiest way
to grasp a Virtual topic is to to see it as a group of subscribers
acting as one.
Technically there is a queue underneat
That is an interesting solution as we do have two streams of messages on our
queues, fast one with lots of data and a slow one with more smaller sized
messages.
Does anyone know if the kaha db adapter supports use of wildcards (i.e.
"OrdersForDevice*"), as we have dynamic queuenames. would somethi
technology version I have used:
1. jdk 1.6
2. spring 3
3. activemq-core 5.4.1
4. camel-core 2.5.0
I have used below configuration in application context for activemq pool and
jms configuration
> class="org.apache.activemq.pool.PooledConnectionFactory"
> init-method="start" destroy-method
Hi,
I am wondering activemq's broker can handle the following use case:
before broker sending message to the consumer, the broker will detect the
dlq, if there is message in the dlq with the same JMSXGroupID as the one is
going to be sent to the consumer, the broker will reroute the message to dlq
Hi, there are 4 things to check out in your configuration.
1. The JMX configuration should be done from your wrapper file as someone
pointed out. Easier to mantain and goes with the documentation, but it's
still "optional" as there are several ways to implement it, and as
ActiveMQ's documentation l
Hi We are facing below exception in production. Could any body help me out
immediately on below error:
becz of this error Ques are filling up very fast,, Awaiting for reply:::
ERROR processor.DefaultErrorHandler: Failed delivery for exchangeId:
ID:as-mm-app1-46371-1411487151507-0:37:1:1:341. Exh
Thanks Andreas
So normal acknowledgement that works with persistent messages in case of
topics with durable subscriber will not be there in case of virtual topic.
Or will it be there and have some other behavior?
Any idea on this ?
Thanks,
Pradeep
--
View this message in context:
http://acti
Hi
I would dare to say thats fairly unpredictable.
If you are relying on the order in which multiple recipients of a topic
recieve a particular message,
then you should reconsider your appliaction design with respect to the
message flow.
In a nutshell, you can consider each virtual destinati
Hi,
I am trying to use virtual topic and am unable to find answer to this
question, Can anybody help?
*Question*: I am sending to topic "VirtualTopic.Test" and have a logical
Queue "Consumer.A.VirtualTopic.Test". I have a subscriber (A) to topic and a
consumer (B) to physical queue corresponding
Hi Petter,
Thanks for stackoverflow link, you have not mentioned that virtual topic
should be preffered way but you haven't mentioned why. Are there any
performance difference?
I need to decide on one of these with a proper answer so that I need not
switch in future because of some hidden differe
Hi
we had a similar issue in our ActiveMQ broker. The reason was that we
had a topic that we use for guaranteed message delivery with message
persistence and durable subscribers. Some durable subscribers might be
offline and we spotted that even with a few MB worth of messages our
persistent
everything is possible! but they evolved independently, hence the overlap
in functionality
On 26 September 2014 16:02, Tim Bain wrote:
> Would it be possible for the failover transport to use the same
> DiscoveryListener mechanism that the static transport uses, but that's just
> not how it's be
I wrote something about that on Stackoverflow a few days ago.
Take a look. If that generic answer is not enough, don¹t hesitate to ask a
bit more detailed what you want to achieve.
http://stackoverflow.com/a/26052645/412763
BR
Petter
Den 2014-09-29 07:31 skrev bansalp :
>Hi,
>
>I have a use-
21 matches
Mail list logo