There is no guide for tuning at the moment.
If you have specif questions you might ask here.
Thanks Wolf-Dieter, there is no specified issue currently. The obvious case is the system is becoming a little slow after running some time, so I am wondering if there is any configuration that can be done to improve the performance.
If the system getting slow after some time the first thing is to analyze the load behaviour, maybe the load is increased.
Also the memory consumption and the GC is always and issue in this case, but there is no difference for the AS versions.
The only difference is where you have to set the JVM parameters
we have with our application the problem that it gets slower in 24 hosts. Heap and CPU usage is good. After restart of jboss all is fine. Which parameters we have to look at to find where the problem is? We have 10 CUs on the system and not heavy traffic. Over night there are no users on the system.
Daniel Wehrle schrieb:
we have with our application the problem that it gets slower in 24 hosts.
Do you meant that the application get slower after 24 hours?
What is slower as I understand that there is no issue with heap memory and CPU load?
Yes. 24 hours. Sorry.
No issue with heap and cpu. We have i.e. implemented some background processes with JPA transaction timeout 5 min. If the system is fine, this background process runs in a few seconds. If the system becomes slow it can happen that the transaction timeout is reached. Also in the gui a search with a paged result list becomes slower. We cannot reproduce this on our test systems with heavy load.
We use the standard standalone-full.xml without any modification in thread pool or max-connections. We have a DB connection pool with max. 100 connections (never reached).
- JBoss AS 7.1.1 (also testet with Jboss EAP 6.1.0 alpha)
- OS: Windows Server 2008 R2
- DB: MS-SQL 2008
- JDK 7 (Update 21)
- EJB, Stateless SessionBeans
- JPA, Entities, Hibernate
- Hibernate Search (4.2) and Lucene (3.6)
- JMS (hornetQ) and MDBs for asynchroneous background processes
- User-Transactions for batch processes
- Wicket (6.5) for GUI
I think you should continue in a different thread.
Form my perspective you need to check what is slow, maybe add debug statements to see where the ime is spend. Maybe the DB itself is slow.
We have already added debug statements. We debugged several use cases. If the system becomes slow all sub steps are slower. I think the DB is not slow because if we restart the JBoss the system is fast again.
Are there any information that the Jboss has any problems with standard configuration?
Wolf-Dieter, how i can create a new thread without loosing your and my comments?
You might post a summary with quotes.
Best is to not use existing old threads or some that are 'only similar'