[Performance Tuning] - maxThreads/ThreadPool configuration
by njrfrens
I'm little confused with the following 2 parameters
1. <Connector port="8443" maxThreads="500" in server\default\deploy\jboss-web.deployer\server.xml
2.
JBoss System Threads
10
in \server\default\conf\jboss-service.xml
First one is referring to the max no. of HTTP threads that the server handle
How the MaximumPoolSize is related to this one?
My application has to handle 500 concurrent requests.
My application is running on a server with 2GB RAM. My JBoss version is 4.2.3.
I've used the below configuration:
1. maxThreads="500" in HTTPConnector
2. MaximumPoolSize is 10 in jboss-service.xml
3. max-pool-size = 60 in mssql-ds.xml
Is there any issue in my configuration?
When I'm running load test
With <200 users, application is running fine
Beyond 200 users, I'm getting the errors "Peer shut down incorrectly" and
"500 Internal Server error"
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256609#4256609
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256609
16 years, 7 months
[JBoss Cache Users] - Re: JBoss 4.2.2 with TreeCache 1.4.1.SP5: nodes, attributes
by the_olo
OK, I've found the solution to my problem.
First, it wasn't in the configuration of the TreeCache itself, but of the Hibernate Cache provider.
It turns out that this behaviour is by design the default in the Hibernate JBoss Cache provider (hibernate-jbc-cacheprovider-1.0.1.GA.jar).
See: http://www.jboss.org/community/wiki/NewJBossCache14xBasedHibernate32Cache....
The option responsible for this behaviour is hibernate.treecache.local_puts_only:
anonymous wrote : The aim of this property, whose default value is true, is to makes sure any put calls on the Second Level Cache as a result of a read operation from the database are done locally which means that data read from database is not replicated to other nodes.
So placing the following line in my hibernate.cfg.xml has enabled full cache replication across the cluster:
<property name="hibernate.treecache.local_puts_only">false</property>
|
The relevant portion of my Hibernate session factory configuration now looks like this:
<property name="hibernate.cache.provider_class">org.jboss.hibernate.jbc.cacheprovider.JmxBoundTreeCacheProvider
| </property>
| <property name="hibernate.treecache.mbean.object_name">jboss.cache:service=MyTreeCache</property>
| <property name="hibernate.treecache.local_puts_only">false</property>
| <property name="hibernate.cache.use_second_level_cache">true</property>
| <property name="hibernate.cache.use_query_cache">false</property>
|
| <!-- Tuning -->
| <property name="hibernate.jdbc.batch_size">32</property>
| <property name="hibernate.jdbc.fetch_size">32</property>
| <property name="hibernate.default_batch_fetch_size">32</property>
| <property name="hibernate.jdbc.batch_versioned_data">true</property>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256600#4256600
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256600
16 years, 7 months