Hi,
My setup is:
- single AMQ 5.3 broker, with no persistence (persitent=false)
- useDedicatedTaskRunner=false
- two nio producers
- around 70 tcp consumer
- 5000 topics total with lastImageSubscriptionRecoveryPolicy and
constantPendingMessageLimitStrategy=10
- producers do asyncSend
- no
magellings wrote:
Could anyone tell me what edition of the 32-bit wrapper we get when we
download activemq? Hopefully the 32-bit version is community...
From http://wrapper.tanukisoftware.org/doc/english/download.jsp:
64-bit Windows versions of the Java Service Wrapper are not currently
Hi,
We're experiencing a lot of stomp connection drops.
There are a dozen connections. We're using ActiveMQ 5.2.
The clients are java applications over internet connection.
There is nothing on AMQ log.
How do I tune the logging to see these droppings?
I've read the links below, but I'm not sure
Hi,
I've read several references and posts like [1], [2] and [3], to decide
which should I use, DefaultMessageListenerContainer or
SimpleMessageListenerContainer.
Once I decide to go with DefaultMessageListenerContainer, should I use a
plain ConnectionFactory or a PooledConnectionFactory?
DMLC
Hi,
Did anybody try to install ActiveMQ as a windows service using yajsw instead
of jsw?
http://yajsw.sourceforge.net/
Thanks,
Danilo
--
View this message in context:
http://www.nabble.com/Install-as-service-using-yajsw-tp21875241p21875241.html
Sent from the ActiveMQ - User mailing list
Hi Stefan,
I'm on the same boat.
I'm hitting some 4.1 issues, and I'm considering (again) to migrate to
5.2.0.
But this issue is pushing me back.
Danilo
stefan.moser wrote:
Has there been any progress on this issue? I've just started using
ActiveMQ and require a large number of topics.
Hi Filip,
Filip Hanik - Dev Lists wrote:
in the test case provided, the program is trying to create 5000+
connections/sessions, hence that would require 5000 threads, not very
scalable.
No, the program is not creating 5000+ connections/sessions. There is a
single connection and session.
Hi Hiram,
Hiram Chirino wrote:
Please post a stack trace of all those threads that on the broker side
when you run this test.
I'm attaching both debug logs from the server and the client.
The OOME stack trace is below.
INFO | jvm 1| 2008/05/22 23:29:01 | java.lang.OutOfMemoryError:
Hi Filip,
Filip Hanik - Dev Lists wrote:
essentially, it's more of a tuning thingy then a memory leak, if one
needs that many topics/queues, then not running with the dedicated task
runner sounds like the solution,
I didn't understand why you classify this issue as a tuning thingy and
Hiram Chirino wrote:
Still it would be nice if you could create a test case that shows the
problem and submit it so we can get to the root of the problem.
The attached code shows the problem.
With UseDedicatedTaskRunner=false it works ok.
http://www.nabble.com/file/p17281318/App.java
Hiram Chirino wrote:
I modified your case so that it's a JUnit test and so that it starts
an embedded broker.. I did not see the threading problem against the
trunk, but I did see :
javax.jms.JMSException: Java heap space
If you run my modified test case do you still see the
Hi,
I have this problem too. It happens with AMQ 5.0.0 and 5.1.0. Works fine
with 4.1.1 and 4.1.2.
I can see the number of threads using the windows task manager, and it's not
good :-) +2000 threads.
My client application is a producer, and it sends thousands of messages to
thousands of
unfortunately we are waiting for the Incubator to decide where to put
maven 2 releases of incubated projects.
Is this issue resolved?
Is there any issue raised at jira related to this?
Thanks,
Danilo
--
View this message in context:
13 matches
Mail list logo
