Running "activemq-admin query" from the command line only works about every
third or fourth try. Usually I get this error:
[EMAIL PROTECTED]:~/apache-activemq-5.0.0/bin>
[EMAIL PROTECTED]:~/apache-activemq-5.0.0/bin> ./activemq-admin query
ACTIVEMQ_HOME: /home/andrew/apache-activemq-5.
I saw the same thing. Put in a JIRA so someone fixes it before the next
version comes out.
Michal Singer wrote:
>
> Hi. I use the 5.1 snapshot.
> I see that the queue size of broker, and ActiveMQ.Advisory.TempQueue,
> increase all the time.
>
> At first, the problem was that auto_ack did not w
Since 5.0.0 is basically unusable with all the InactivityMonitor and
EOFExceptions when will a 5.0.x version become available that we can use?
5.1 Snapshot seems not much better.
Just out of curiosity, how did 5.0.0 come out with so many bugs in it that
it is practically unusable? How will the te
Hi,
My chat application needs to multicast messages to the proper chat rooms. An
important requirement is that clients must be able to subscribe and
unsubscribe to/from chat rooms. It looks like that it could be done with
message selectors.
Here is my tentative architecture:
1) 1 server runs th
I think I would be a bit more inclined to look into virtual topics. Primarily
because they're easier to work with - vs durable subscriptions - and they
also offer the functionality provided by queues. So you get the best of
both worlds ;)
Joe
Ramit Arora wrote:
>
> Hi Joe,
> Thanks for yo
Hi Joe,
Thanks for your time. My application requires a hub & spoke architecture
with around 100 publishers & 500 consumers at peak load. All publishers
would be pushing messages to different topics. One consumer would be durable
as it needs to collect all messages. The rest would be online sporad
Your non-durable subscriber will only get those messages that were published
while it is active. When you bounce the broker it does not retain the
identity of your non-durable subscriber. So when the broker comes back up,
it doesn't consider your non-durable subscriber to have been active when th
I am brand new on ActvieMQ.
I am wondering how the resolution of the clients IP adress is done by the
broker. Do I have to assign a URL to each client and define it in a DNS ?
How the client is wake up when a new message. I know that the client have to
use an API but what is in this API. Is this
On 28/03/2008, carbon60 <[EMAIL PROTECTED]> wrote:
>
>
> James.Strachan wrote:
> >
> > On 27/03/2008, carbon60 <[EMAIL PROTECTED]> wrote:
> >> I apologize for asking basic questions! I am trying to configure
> >> multicast
> >> discovery among brokers on an insecure network. Is this possibl
James.Strachan wrote:
>
> On 27/03/2008, carbon60 <[EMAIL PROTECTED]> wrote:
>> I apologize for asking basic questions! I am trying to configure
>> multicast
>> discovery among brokers on an insecure network. Is this possible or a
>> good
>> idea?
>>
>> I don't know much about multicast, so
Iam using ActiveMQ 4.1.1 and ActiveMQ-cpp-2.1.3 on Windows 2003 server
Enterprise Edition with VC++ 8.0.
Iam sending persistent text messsage using Topic to a destination.
(wireFormat=openwire, transport.useAsyncSend=false,
Session::AUTO_ACKNOWLEDGE, DeliveryMode::PERSISTENT )
Hi All,
I have a situation where I have to consume persisent messages from many
non-durable subscribers. My publishers push persistent messages to a topic,
which are consumed asynchronously by non-durable subscribers. I am using the
AMQ Persistence Adapter & CLIENT_ACKNOWLEDGE. If I kill a non-dur
As I understand such "synchronous publish" is not available in current
ActiveMQ release but this is a desirable feature?
Does this statement apply to both communication models? publish-subscribe
(topic) and send-receive (queue)?
Is such feature included in any concrete future implementation sche
On 27/03/2008, carbon60 <[EMAIL PROTECTED]> wrote:
>
> I apologize for asking basic questions! I am trying to configure multicast
> discovery among brokers on an insecure network. Is this possible or a good
> idea?
>
> I don't know much about multicast, so I don't understand how to restrict
>
14 matches
Mail list logo