Hi, As most of you are probably aware, JBossMQ creates a _lot_ of threads. This can be particularly annoying with native threads Java VMs on Linux where threads are just processes with shared memory and io, and where the number of operating system threads by default are limited to 512. I am a Linux user, and I am a bit annoyed by this. Sometimes when I play with JBoss, I cannot even open a new shell, because all available OS processes are in use by JBoss.
Looking into the JBossMQ sources, it looks like the message pusher threads in org.jboss.mq.server.ClientConsumer are allocated per-connection. I do not think that this approach is very scalable. So what I propose (and intend to do, if noone complains) is: 1) Add code to JBossMQ that implements a thread pool with an embedded work queue. 2) Change the per-connection message pusher thread implementation to use an instance of 1) above. Best Regards, Ole Husgaard. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
