Thanks a lot Nate!
nmittler wrote:
>
> Discovery is not currently supported by activemq-cpp. You can see the
> list
> of options here:
>
> http://activemq.apache.org/cms/configuring.html
>
> Regards,
> Nate
>
> On 5/16/07, cppUser <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi All,
>>
>> I tried t
Hello,
I tried to use JNDI and the lookup() methode to get a topic for a client.
properties = new Hashtable();
properties.put(Context.INITIAL_CONTEXT_FACTORY,
"org.apache.activemq.jndi.ActiveMQInitialContextFactory");
Context context = new Initia
temp queues are discarded when the creating session closes (goes away,
crashes etc)
also, if you want message to not be received when a client isn't there, you
could always use topics
On 5/17/07, Gustavo Lanna <[EMAIL PROTECTED]> wrote:
Right, but if client doesn't connect and others service
Right, but if client doesn't connect and others services send him messages,
his queue grows and the server crashes. I wish the ActiveMQ server to remove
or discard the messages !!
James.Strachan wrote:
>
> You could use a temporary queue for each client; then all messages are
> removed when the
Is there any place listing what hardware various ActiveMQ configurations
require? How many users you can support, etc?
--
View this message in context:
http://www.nabble.com/Resource-Specs-tf3774118s2354.html#a10671511
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi everyone,
I am trying to setup two MQ Servers (4.1.1), sharing the same data directory
(I tried Derby and Kaha), on top of OCFS, but the locking doesn't seem to be
working. It works fine when both MQs are running on the same server (still
using OCFS). I see the second MQ waiting for the lock t
You could use a temporary queue for each client; then all messages are
removed when the client disconnects
On 5/17/07, Gustavo Lanna <[EMAIL PROTECTED]> wrote:
Hi,
How to configure ActiveMQ to discard/remove messages for disconnected
clients. If I send a message to queue that has no clients li
Hi,
How to configure ActiveMQ to discard/remove messages for disconnected
clients. If I send a message to queue that has no clients listening, when a
client connect to ActiveMQ his receive a message that I sent. I would like
that the ActiveMQ delete the message if there is not client
listening/co
On 5/17/07, mjparme <[EMAIL PROTECTED]> wrote:
>>I've tried to describe it here
>>http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
>>by all means edit that wiki page if you think it could be more clear etc.
Yeah, I used that wiki page for my initial develop
>>I've tried to describe it here
>>http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
>>by all means edit that wiki page if you think it could be more clear etc.
Yeah, I used that wiki page for my initial development a few weeks back;
very helpful, the correlat
On 5/17/07, mjparme <[EMAIL PROTECTED]> wrote:
On 5/17/07, mjparme <[EMAIL PROTECTED]> wrote:
>
> When you are using JMS for request/response and you set the correlation ID
> on
> the message does this ID have to be unique for the lifetime of the
> well-known queue you are sending to or does i
On 5/17/07, mjparme <[EMAIL PROTECTED]> wrote:
>
> When you are using JMS for request/response and you set the correlation ID
> on
> the message does this ID have to be unique for the lifetime of the
> well-known queue you are sending to or does it only have to be unique for
> the messages curre
Found an existing open issue for this, AMQ-1116. I've submitted a patch
for it, slightly different than the patch already on the ticket. Any
chance it can be included in the next release?
Adam Lewandowski wrote:
I'm using Spring's DefaultMessageListenerContainer inside of an app
server instanc
On 5/17/07, mjparme <[EMAIL PROTECTED]> wrote:
When you are using JMS for request/response and you set the correlation ID on
the message does this ID have to be unique for the lifetime of the
well-known queue you are sending to or does it only have to be unique for
the messages currently in the
When you are using JMS for request/response and you set the correlation ID on
the message does this ID have to be unique for the lifetime of the
well-known queue you are sending to or does it only have to be unique for
the messages currently in the queue?
--
View this message in context:
http://
15 matches
Mail list logo