I have a jdbc based cluster of two brokers, not a network of brokers.
I also have a 3d party AMQ JMS Java client software that creates a temp
queue on each request it makes.
Whenever I disable advisorySupport, the client can send request but fails to
get response into the temp queue it has created
Hi,
In order to use temp destination (queue), do I have to have
advisorySupport="true" ?
Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Can-one-use-temp-destinations-with-advisorySupport-false-tp4657051.html
Sent from the ActiveMQ - User mailing list archive at
Hi,
A jdbc Master/Slave cluster.
The following steps bring me into a 'no Master' state, causing AMQ clients
to fail.
Layout.
two brokers:
- Master, AMQ v.5.6 on Ubuntu 10.04 host;
- Slave, AMQ v.5.5.1 on Win 7 host.
Postgres 9 on yet another Ubuntu 12.04 host.
Sun Java 6 SDK on all hosts; all 64
With pure jdbc Master/Slave, when Master fails to connect to database (caused
by networking issue), Slave cannot acquire the lock.
Is this what one should expect?
AMQ 5.6, Postrgres 9.1, Ubuntu. Each broker and DB are on separate hosts.
Thank you.
-
Serguei
--
View this message in context:
http
metatech, thank you.
The config piece that actually worked:
Folks,
where one could read about those many options as in activemq-core.xsd?
I could not find answers in AMQ docs, nor in Fuse docs, nor in the "ActiveMQ
in Action" book.
For example, in my context
Hi,
jdbc Master fails to run with AMQ v.5.6, Postgres 9.1 on Ubuntu.
Can run it with AMQ v.5.4.2 (same settings).
Getting:
... ERROR | Failed to update database lock: java.sql.SQLException: Method
org.postgresql.jdbc3g.Jdbc3gPreparedStatement.setQueryTimeout(int) is not
yet implemented. | org.apa
Hi,
Setup a Pure Master/Slave with KahaDB.
After deleting a message previously sent to the Master, I am still seeing it
in Slave.
The expectation was that the message would disappear once consumed/deleted.
Using web admin console:
(1) submitted a non-persistent message to Master;
(2) a copy showe
whaley,
Thank you.
No free cheese then for me. As expected but hoped otherwise.
Are there any best practice/advice on how to better deal with such use
cases?
My "such" use case is:
- a message group may contain large (MiB) message(s);
- an admin may want to shutdown the application at any time (
Hi,
Having multiple message groups producers and multiple async consumers,
would it be correct to anticipate that a single consumer may get the
messages received being interleaved from different groups of messages?
Example:
- msg producer P1 sends a group of 2 msgs: P1.1 and P1.2,
while at the sa
