Could you try updating your activemq startup script so that instead of: ACTIVEMQ_OPTS="-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true" it reads as: ACTIVEMQ_OPTS="-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=false"
I think that should help with your thread usage issues. On Tue, May 13, 2008 at 9:03 AM, Danilo Tuler <[EMAIL PROTECTED]> wrote: > > 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 differents topics. There are no subscribers to those topics. > Async send is set to false. Even when the client application is shutdown the > threads are kept alive. > > There is surely a thread leak, and maybe there is a direct relationship with > the number of topics created. > > I've read several topics here, JIRA issues, and an article about AMQ thread > handling, but did not come out with a clue. > > 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-tp17005441s2354p17207910.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
