Hi, we are running an application on JBoss 3.0.5 with some 70 entity beans, 60 session beans and currently around 1500 JMS queues on a Solaris 8, machine with a 1.4.1_02 Sun HotSpot Client JVM.
Some important memory VM params are set to -Xmx3G -Xms2G -Xss512M When the app has around 600 threads going the OutOfMemoryError shown in the subject appears. How is it possible to increase the total possible number of threads in terms of OS or JVM settings? As an alternative, how do we reduce the number of threads JBoss uses. What are the most worthwhile settings to test? Decrease the session bean pool size? Use the secondary cache for the message queues earlier in contrast to holding all or most messages in heap memory? Thanks for your insights. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852313#3852313 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852313 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
