Please post a stack trace of all those threads that on the broker side when you run this test. It would help us tremendously in figuring out the problem. and BTW I do think it's a problem.
On Thu, May 22, 2008 at 2:40 PM, Danilo Tuler <[EMAIL PROTECTED]> wrote: > > 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. > The program is sending messages to 5000+ topics (using a single connection > and session). > > And that produces 5000+ threads on the server, not on the (client) program. > And worse, those threads are kept alive forever, even when the client is > shutdown. And there are no consumers. > > IMHO that sounds like a thread leak, but maybe I'm wrong... > > Best regards, > Danilo > > -- > View this message in context: > http://www.nabble.com/java.lang.OutOfMemoryError%3A-unable-to-create-new-native-thread-on-AMQ-5.0-tp17005441s2354p17410886.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
