With a single connection factory you can only use the failover transport (
http://activemq.apache.org/failover-transport-reference.html ) to connect to
multiple brokers, but only one broker URL will be used at a time.
If you want to have two active connections (or connection pools) to two
dif
How to create connections to different brokers by using one
ConnectionFactory?
Can the code be written as
ActiveMQConnectionFactory connectionFactory = new
ActiveMQConnectionFactory();
for each url in URLs {
connectionFactory.setBrokerURL(url);
Connection connection = connectionFactory.createCon
Create a file start.sh (in Linux environment) with the following content:
#!/bin/bash
export JAVA_HOME=/home/jdk6
export ACTIVEMQ_HOME=/home/amq
export ACTIVEMQ_BASE=/home/amq
export PATH=.:$JAVA_HOME/bin:$ACTIVEMQ_HOME/bin:$PATH
export LOG_FILE=$ACTIVEMQ_HOME/logs/activemq.log
export ACTIVEMQ_OPT
for consumers sure, not sure about producers, think they just work
with composite destinations, but you got to ask the computer
2011/9/14 SuoNayi :
> Hi all,it's said that we can send a message to multiple destinations using
> composite destinations as following,
>
> Queue queue = session.createQ
Hello everybody,
I did search the forum for some similar questions/problems, but didn't find
matching entries.
I normally work with the Spring JmsTemplate, but did also try to reproduce
the problematic behaviour in a native ActiveMQ Java implementation.
// given factory is a ActiveMQConnectionFa
Our subscribers are not durable, however I have noticed that it does appear
to occur around our peaks (sometimes before, sometimes afterwards). Although
I have had it occur once at night, when our traffic was very load (1% of
peak).
I'm using the OpenWire protocol, not stomp. So I'm guessing that
Dom writes:
> Hi,
>
> I've starting having unusual problems with my ActiveMQ consumers, we send
> object messages via JMS 24 hours a day, peaking at around 10k per second to
> various different consumers. All these consumers are consuming from the same
> topic, however from different physical ser
Thanks Torsten, it worked
Thanks & Regards
Venkatesh Laguduva
On Wed, Sep 14, 2011 at 2:34 PM, Torsten Mielke wrote:
> By default the broker does not authenticate connections from JMS clients.
> If you require this, then you need to enable authentication in the broker.
> See http://activemq.apa
On Wed, 14 Sep 2011 11:07:33 +0200, Torsten Mielke
wrote:
>Can you paste the full error please?
>The error seems to be related to the Jetty web container that is also loaded.
>
>Also does the error go away if you comment the line
>
>
>
>from activemq.xml?
The errors do go away if I comment out t
Can you paste the full error please?
The error seems to be related to the Jetty web container that is also loaded.
Also does the error go away if you comment the line
from activemq.xml?
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Sep 14, 2011, at 10:23 AM, Mark wrote:
> H
Rajesh
You can't do anything on the WMQ side to enable that kind of communication.
If you want a MessageProducer running against a WMQ JMS Provider to have its
messages delivered to a.n.other JMS Provider, you need some kind of bridging
agent. One solution could be the WebSphere Message Broker, wh
By default the broker does not authenticate connections from JMS clients.
If you require this, then you need to enable authentication in the broker.
See http://activemq.apache.org/security.html
Torsten Mielke
tors...@fusesource.com
tmie...@blogspot.com
On Sep 14, 2011, at 6:06 AM, Venkatesh L
Hi,
When trying to start ActiveMQ using the command:
$ ksh bin/activemq console
as recommended in the "ActiveMQ in action" book.
I get several java exceptions including this one:
javax.servlet.UnavailableException:
org.fusesource.web.console.server.AgentServiceImpl
at org.eclipse.jetty.
13 matches
Mail list logo
