something somewhere as it all works fine with 40
nodes, but dies when I get around 60.
Thanks very much,
Aidan
--
View this message in context:
http://www.nabble.com/Topic-Connections-dying-with-more-than-60-nodes-tp18567995p18567995.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/Topic-Connections-dying-in-large-install.-tp18567601p18567601.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks for the reply Dejan,
I switched to the Sun JDK and it works fine now. I should have noticed when
I ran a yum install java that it was going to grab the GIJ version and not
the Sun version.
Cheers,
Aidan
Dejan Bosanac wrote:
>
> Hi,
>
> This seems to me like GIJ related
I just thought I'd throw some more information on what I've been doing to try
and debug this, sorry if it's too much information, but somebody might be
able to see what I am doing wrong...
I have tried running the run.jar in the bin folder, and that appears to
start activemq just fine.
If I run
428 (Red Hat 4.3.0-8)
Sorry if I'm missing something, but I've followed the install instructions
and I've tried fiddling with path's and chmod-ing directories but I can't
get ActiveMQ started.
Thanks,
Aidan
--
View this message in context:
http://www.nabble.com/Problem-in
ny way I can get the ActiveMQ internals to release resources once
a client has disconnected? The memory usage seems to grow to around 100 and
then will stop accepting any further messages.
Thankyou for your help!
Aidan
--
View this message in context:
http://www.nabble.com/What-is-best-practice-fo
that this sounds like an anti-pattern. After using
JProfiler and seeing how many ProducerId objects are created (and don't
appear to be garbage collected).
So my question is: Should I be creating one producer per queue/topic and
re-using it, or am I able to create one-per-request?
Cheers,
