Thank you Adrian,
I have tried as you suggested, it worked for Topic, but not queue.
The following is the code for embedded broker. As you see, I have connected
embedded broker to the broker at 61616. When I send a topic, the client
connected to 61616 can receive it, but I can not recieved the
A FailoverListener would be interesting, but afaik, its not provided.
Dingwen Yuan wrote:
> But what is the programmable way to know it?
>
>
>
>
> Dingwen Yuan
> 2007-05-09
>
>
>
> 发件人： spiderman2
> 发送时间： 2007-05-09 11:43:31
> 收件人： users@activemq.apache.org
> 抄送：
> 主题： Re: Way to know whether fai
Having an embedded broker means the JVM running your JMS client will
contain a JMS broker also.
This allows your producer running on the same JVM to keep sending
messages without caring whether the remote broker is up or not, because
the embedded broker will handle message persistence, queuing, et
But what is the programmable way to know it?
Dingwen Yuan
2007-05-09
发件人： spiderman2
发送时间： 2007-05-09 11:43:31
收件人： users@activemq.apache.org
抄送：
主题： Re: Way to know whether failover client is connecting?
When I kill the broker to test a failover, I believe the Consumer's logs show
it try
When I kill the broker to test a failover, I believe the Consumer's logs show
it trying to failover to another broker.
Dingwen Yuan wrote:
>
> Hi all,
>
> Is there a way to know that a failover ActiveMQ client is now trying to
> connect to the brokers?
>
> Thank you!
>
>
>
>
> Dingwen Yu
Hi all,
Is there a way to know that a failover ActiveMQ client is now trying to connect
to the brokers?
Thank you!
Dingwen Yuan
2007-05-09
slight followup to my own question here,
assuming we had a pure master/slave setup and the master dies, we then:
1) stop slave
2) copy files from slave to master
3) delete files from slave?
4) start master
5) (since clients were sitting the retrying, they'll connect and start
sending before slav
Hello Adrian Co,
I think I have to use failover, because we have deployed brokers in
master/slave mode. What do you mean by "embeded broker"? Could you give me any
more suggestion?
Thank you!
Dingwen Yuan
2007-05-09
发件人： Adrian Co
发送时间： 2007-05-09 09:55:41
收件人： users@activemq.apache.org
I'm guessing it blocks because its trying to reconnect to the broker,
and pending the send.
Either don't use failover, or use an embedded broker and make your
network connection failover.
Dingwen Yuan wrote:
> Hi all,
>
> I have used a failover url to configure my JMS client, such as this
> "fai
Hi all,
I have used a failover url to configure my JMS client, such as this
"failover:(tcp://127.0.0.1:61616)?jms.useAsyncSend=true". But when the JMS
broker is down and the client is trying to connect to the broker, all send to
topics or queues just get blocked. Why should I do if I want only
If you read apache pages you ll see that you do not have to create a
specific queue. It is enough just to publish a message and the queue
will be created automatically behind the scene.
I am using this feature and it works very well.
Regards,
Daniel
SBenj wrote:
(MQ 4.1, Java 1.6, Redhat)
I h
On 5/8/07, SBenj <[EMAIL PROTECTED]> wrote:
Thanks much for the explanations.
I've tried to backtrack the exploration process I went through to recreate
the stack trace without success. I can tell you it was in the process of
trying to create a Topic in the code to subscribe to from a virtualQu
Thanks much for the explanations.
I've tried to backtrack the exploration process I went through to recreate
the stack trace without success. I can tell you it was in the process of
trying to create a Topic in the code to subscribe to from a virtualQueue.
Sorry I can't be more specific.
James.
On 5/8/07, SBenj <[EMAIL PROTECTED]> wrote:
(MQ 4.1, Java 1.6, Redhat)
I have a question regarding Queues and Topics as their use relates to our
business case. We have a few hundred clients, each of whom will need to
subscribe to their own "mailbox". New clients are continually created every
few
If you read apache pages you ll see that you do not have to create a
specific queue. It is enough just to publish a message and the queue
will be created automatically behind the scene.
I am using this feature and it works very well.
Regards,
Daniel
SBenj wrote:
(MQ 4.1, Java 1.6, Redhat)
I h
(MQ 4.1, Java 1.6, Redhat)
I have a question regarding Queues and Topics as their use relates to our
business case. We have a few hundred clients, each of whom will need to
subscribe to their own "mailbox". New clients are continually created every
few days (they're remote business sites) and gene
I took a look at the posting you referred me to.
It seems that I should just copy and rename that sqlserver file.
Now for the stupid question.
Does that mean I will need to recompile ActiveMQ?
and build a new activemq.jar.
kd
Mario Siegenthaler wrote:
>
> You can tell ActiveMQ to use a s
Ok it seems I could resolve the problem ... I think it is a socket
problem with antivirus nod32 IMON deamon.
Anyway, I did 2 things ...
1) remove QTJava
http://forum.java.sun.com/thread.jspa?threadID=5169276&tstart=0
2) stop nod32
http://www.wilderssecurity.com/archive/index.php/t-46060.html
n
Fixed
use org.springframework.jms.listener.SimpleMessageListenerContainer instead,
Default one just refetches the message in endless loop. Simple one uses
redelivery policy to do that. No idea why default behavior in Spring so
weird
--
View this message in context:
http://www.nabble.com/Redelive
19 matches
Mail list logo
