On Tue, Sep 25, 2007 at 12:32:31PM +, David Holroyd wrote:
> So, I'm starting to learn C#, and am attempting to prototype some
> generic NMS bridging code that I can use to connect ActiveMQ and MSMQ
> implementations.
So, attached are some vaguely bridge-flavoured bits.
Any comments?
I suspe
On Fri, Sep 28, 2007 at 10:39:37PM +, David Holroyd wrote:
> On Wed, Sep 26, 2007 at 11:11:30PM +, David Holroyd wrote:
> > I tried to adapt the NMS example code for MSMQ, but it seems to just
> > hangs trying to get the message back from MSMQ. Under Computer
> > Management, I can see that
We did not do a jvm kill -3, we got the OOME on the broker. We were able to
send more messages because we pushed the memory size to 1024M for jvm, 512M
for broker to allow more time for the check point to occur (we were guessing
that was the issue, but it was not).
BTW we are using AMQ version
I'd be very grateful if someone could just let me know how to get a handle to
the Multicast Discovery Agent Notifier, so I can stop that manually. Anyone
know how to do this?
thanks,
Andrew
andrew1234 wrote:
>
> We're running a webapp on Tomcat 5.5.20 that uses ActiveMQ 4.1.1 (and JDK
> 1.4.2
Mike,
Are you getting OOMEs on the publisher (the client) or in the broker?
I'm wondering if you can send your jvm a kill -3 signal to get a
thread dump, because it sounds vaguely like the problem that I'm
currently experiencing. However, my publishers can only send ~1390
messages before
Is there any chance someone from the ActiveMQ team can give some insiders
feedback on the below? Even if it's 'durable subscribers are unstable -
don't use them'?
Thanks,
Mike Roberts (development manager for the team Ahmed is on)
aselshamy wrote:
>
> Hi
>
> We have one topic publisher that
:)
On Oct 1, 2007, at 3:13 PM, j0llyr0g3r wrote:
Ok, please forget this embarassing posting..
Ah colleague of mine had another consumer running on the same
queue, and i
had totally forgotten about this...
j0llyr0g3r wrote:
Hey folks,
i got a strange problem here:
I connected two
Ok, please forget this embarassing posting..
Ah colleague of mine had another consumer running on the same queue, and i
had totally forgotten about this...
j0llyr0g3r wrote:
>
> Hey folks,
>
> i got a strange problem here:
>
> I connected two brokers, let's say A and B, using SSL.
>
>
Hey folks,
i got a strange problem here:
I connected two brokers, let's say A and B, using SSL.
Then i started the activemq-consumer example and the activemq-producer
example.
Surprisingly, some messages are NOT received.
Here is the output of the consumer:
consumer:
[echo] Running con
Hi all,
I am experimenting a strange problem using activemq-web module.
I have a web client using a topic and a producer producing messages at
a very fast rate.
>From time to time I reset the connection by relistening at the web
client side at the same topic.
After some resets the consumer hangs,
On Oct 1, 2007, at 8:21 AM, ttmdev wrote:
The messages are persistent, so shouldn't this give the broker the
option of
sending them to the store, thus freeing up memory? Only if the
messages are
non-persistent does the broker have no choice but to keep them in-
memory.
That is my understan
I'm going to see if I can reproduce on OS/X
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 1, 2007, at 1:06 PM, WHIRLYCOTT wrote:
Thanks for your response, Saqib,
On Oct 1, 2007, at 6:24 AM, srasul wrote:
from what i can see, you are sending persistant messages to a
topic, this
mea
The messages are persistent, so shouldn't this give the broker the option of
sending them to the store, thus freeing up memory? Only if the messages are
non-persistent does the broker have no choice but to keep them in-memory.
Saqib is right, you should only have to create one connection. Connect
Thanks for your response, Saqib,
On Oct 1, 2007, at 6:24 AM, srasul wrote:
from what i can see, you are sending persistant messages to a
topic, this
means that if no one is listening on that topic, your messages will he
stored (aka held in memory) until someone listens on that topic.
this w
Hi Phill,
from what i can see, you are sending persistant messages to a topic, this
means that if no one is listening on that topic, your messages will he
stored (aka held in memory) until someone listens on that topic. this would
explain why you run out of memory. Essentially you experiencing th
Hi,
I think current activemq-console module cannot authenticate JMX. Here is the
patch of the activemq-console that can login to JMX (just put
-Djmx.userid=x -Djmx.password in the shutdown script + put the jar file
attached below under %ACTIVEMQ_BASE% folder, NOT %ACTIVEMQ_BASE%/lib
folder).
Hi,
sometimes our activeMQ freezes with the JMX console reporting that the
Borker's MemoryPercentUsed is 100%.
In out activeMQ setup, we have no queues and _only_ topics. We have this to
avoid the memory issues related with slow-consumers.
we are running activeMQ 4.1.1.
What is also strange is
Thanks Hiram, I rebuilt this morning from subversion and it works now.
-Dominic
--
View this message in context:
http://www.nabble.com/Compatability-between-AMQ-4.1.1-and-5.0-Snapshot--tf4488111s2354.html#a12974695
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
I'm using ActiveMQ 4.1.1 and it seems like ./shutdown script is using JMX to
shutdown ActiveMQ. After I secured ActiveMQ's JMX (by following
http://activemq.apache.org/jmx.html#JMX-PasswordProtectingtheJMXConnector),
I cannot use ./shutdown script anymore.
I tried to use ./shutdown --jmxurl
19 matches
Mail list logo
