Hi,
A few more recent observations.
consider this -
we have a message producer that uses a failover transport
failover://(tcp://host1:61616,tcp://host2:61616).
there are 2 brokers - 1 on host 1 and other on host2 and both listen to
61616 on the respective machines. Both point to same data stor
Hi,
Can you please confirm whether i can go ahead with my proposed solution? It
doesn't look to be a very neat solution, but we have a production release
coming up this weekend, so appreciate if you can confirm that it should not
have any negative impacts. Willing to explore any alternate options
No, deletion of inactive destinations is not enabled. The only option I can
think of is creation of the DLQ's on restart by adding an entry for each dlq
in . Is that fine? or do you see any better options?
We dont want to consume messages from the DLQ. We have a monitoring set up
that monitors the DLQ'susing jmx and the monitoring is no longer able to
alert us regarding DLQ messages because the queues are dropped after a
restart.
--
View this message in context:
http://activemq.2283324.n4.nabble.
Hi,
We notice that if a queue is not defined in of
activemq.xml, it does not get created when the broker is restarted.
Our actual problem is that DLQ's do not get created on restart of the broker
although the messages are there in our persistent data store(oracle DB). I
checked this with normal
This is the background of the issue -
Earlier the embedded broker in the tomcat used to be the default one that
gets created when you make a vm connection. So the memory limit used to be
64 mb and producer flow control used to be enabled. Also, there was only 1
camel consumer. With that state, onc
Thanks for the quick reply Gary and Sorry for the delayed response
I am not able to figure which exactly which thread is the Transport reader
thread. Could you please help with some pointers? Would be good if I can
just paste the required threads. I have the thread dump of both the broker
and the
Hi,
We are having a webapplication running on tomcat in which we have an
embedded broker. We also have a separate broker that we make TCP connections
to.
We use activemq 5.5.0
We have a camel route that looks like this -
We send object messages to the vm broker queue that routes the message to
I'm upgrading Active MQ from 5.4.2 to 5.6.0 (latest available in Maven
repository)
All our Unit test cases and Build goes well, however,
... on deployment we find it creating Random URL connections to
tcp://127.0.0.1:
We create a ConnectionFactory in Spring that uses the following adapter
where
ok,. .. turns out this is generated by the Borker
..and is not the URL the client is sending on but the Broker indicating the
connection was abruptly broken by the client.
See: https://issues.apache.org/jira/browse/AMQ-2730
..however am still not sure how to Mute this?
The messages are sent usi
..we had a Check to test i a Connection is available before allowing the user
to enter a message.
In earlier verison (and yet to verify) , "con =
template.getConnectionFactory().createConnection();" was not relibale to
state if the Broker was up or not. ... not sure if there is a better way for
the
11 matches
Mail list logo
