On 11/1/07, Roger Hoover <[EMAIL PROTECTED]> wrote:
> While rolling out new consumer code, we'd like to suspend the broker
> so that messages can be enqueued but not delivered. Once we've pushed
> the new code out and restarted the consumers, we want to resume
> message delivery.
>
> Is this possi
no problem I hope it works out for you
-Trevor
Roger Hoover wrote:
>
> Interesting idea. Thanks, Trevor.
>
> On 11/1/07, tpounds <[EMAIL PROTECTED]> wrote:
>>
>> If your broker is forwarding to another broker similar to a network of
>> brokers configuration you could stop the network connect
I think the consumers will keep reconnecting so I'm not sure this will
work but will give it a try.
On 11/1/07, Diego Botticelli <[EMAIL PROTECTED]> wrote:
>
> Maybe you could, through JMX, 'stop' the consumer's connections? For example,
> through the JConsole you can invoke the 'stop' operation o
Interesting idea. Thanks, Trevor.
On 11/1/07, tpounds <[EMAIL PROTECTED]> wrote:
>
> If your broker is forwarding to another broker similar to a network of
> brokers configuration you could stop the network connector between them
> temporarily via JMX. The configuration could be similar to the f
Maybe you could, through JMX, 'stop' the consumer's connections? For example,
through the JConsole you can invoke the 'stop' operation on the consumer's
connection.
Joe
Roger Hoover wrote:
>
> Stopping the consumers involves sending SIGTERM to them which could
> kill them in the middle of pr
If your broker is forwarding to another broker similar to a network of
brokers configuration you could stop the network connector between them
temporarily via JMX. The configuration could be similar to the following:
Before Connector Stop:
(Producer) -> (Broker 1) -> (Broker 2) -> (Consumer)
A
Stopping the consumers involves sending SIGTERM to them which could
kill them in the middle of processing a message. Being able to
suspend delivery would allow us to make sure they were no longer
processing messages before we kill them. Granted, we can get around
this problem by retrofitting the
On 01/11/2007, Roger Hoover <[EMAIL PROTECTED]> wrote:
> While rolling out new consumer code, we'd like to suspend the broker
> so that messages can be enqueued but not delivered. Once we've pushed
> the new code out and restarted the consumers, we want to resume
> message delivery.
>
> Is this po
While rolling out new consumer code, we'd like to suspend the broker
so that messages can be enqueued but not delivered. Once we've pushed
the new code out and restarted the consumers, we want to resume
message delivery.
Is this possible with ActiveMQ?
Any advice/info is appreciated. Thanks,
R
I personally don't know much about the ruby client (
http://stomp.codehaus.org/Ruby+Client). You might want to post your
question to the stomp forum (http://stomp.codehaus.org/Mailing+Lists).
Regards,
Nate
On 11/1/07, Marcos Alvares <[EMAIL PROTECTED]> wrote:
>
> Thank you, Nate
>
> Do you have
Thank you, Nate
Do you have any example in SSL/STOMP/Ruby ?
Thanks a lot for your time.
On Thu, 2007-11-01 at 09:36 -0400, Nathan Mittler wrote:
> Our discussion has been specifically about the C++ client, ActiveMQ-CPP.
> The wire format (OpenWire, Stomp) is a layer on top of the transport (t
Our discussion has been specifically about the C++ client, ActiveMQ-CPP.
The wire format (OpenWire, Stomp) is a layer on top of the transport (tcp).
It is done this way so that you can use any wire format with any transport.
ActiveMQ-CPP does not yet support an SSL transport, therefore it is
unavai
In activemq, have no way to build a stomp client using ssl connection?
Have you any activemq clients using ssl examples?
thank you
On Wed, 2007-10-31 at 17:28 -0400, Timothy Bish wrote:
> Stomp provides an interoperable wire format so that any of the available
> Stomp Clients can communicate wi
I thing I seem to have found the problem myself. I was using the latest
SNAPSHOT (25 Oct, 07) version to send and receive messages over HTTP
connection. While sending messages works fine receiving messages doesn't.
When I reverted to the stable version 4.1.1 both sending and receiving seem
to work
Hi,
Evidently the problem may be the use of adapter="#oracle-adapter" in your
. Remove that and try again.
If you want to store message only in database than configuration of
dataDirectory too not required. I can suggest you to use the follwoing.
Since you are using DB for persistence add useData
Thanks for your reply. I am able to send messages to ActiveMQ but the
consumer is not receiving any messages sent by the producer. If I revert
back the configurations to use tcp everything is fine.
Below is the configuration I have used:
http://loc
16 matches
Mail list logo
