Upon more profiling, I figured that I have lots of apache.axis objects that
are not garbage collected.
The way I am making SOAP calls is through axis1.4 generated stubs. Eg.
MyDAO {
protected MyPortType getAPIConnection() throws Exception {
MyPort port;
try {
MySe
>> If what you're caching is large arrays, you might want to consider
breaking them up into smaller >>chunks of the same size, and pooling those.
Not sure what you mean by pooling those. I am using JBoss cache.
>>You might also think about tracking your cache entries via SoftReference
objects,
>>- what was hanging on to the 0.5Gb of memory in the 15 second period
>>above between the 2nd and 3rd GC.
I have a caching layer which is configured to evict objects from memory
after 3 minutes of idle time. I have profiled and see all those objects in
cache get evicted after some idle time.
Is
I am just trying to learn and understand the GC logs. (I did read the sun's
docs on GC tuning).
jdk1.6.0_07
-Xms2g -Xmx2g -Xss256k
-XX:+UseLargePages -XX:+PrintGCDetails
-verbose:gc -Xloggc:/var/log/gc.log
-XX:PermSize=512m -XX:MaxPermSize=512m
It is running Parallel Collector by default. The
Ok.. adding some info to mod jk logs and doing some thread and heap dumps, I
figured that, during peak traffic hours, the garbage collection gets more
frequest and takes longer. This slows down the overall system and the
threads start piling up. Requests that used to take 2 seconds now take a
coup
The 5 seconds calls are all database or webservice calls. So they all go to
waiting state.
I did some load tests using JMeter, but I had problems coming to a
conclusion with the data. What should I look for exactly? Because as I
increase the no of concurrent requests, the app starts responding sl
Given that each request takes 2 seconds on average. Among them, some of them
take less than 500ms, and some take as long as 5 seconds or even a little
more sometimes.
How many such concurrent request would a tomcat server running on a double
quad-core server handle?
I am trying to understand th
The problem has always occured at the oddest hours for me to do a thread
dump. I have done jmeter load test and tried to recreate the problem in
test, but have never able.
I will upgrade to the latest version and then play with the connection
timeouts.
CrystalCracker wrote:
>
> Apac
Can anyone explain me how exactly prefork works?
StartServers 2
MaxClients 150
MinSpareThreads 25
MaxSpareThreads 75
ThreadsPerChild 25
ServerLimit 16
I think I got confused between the terms - server, process and thread. If
prefork is a single thread process, what does that ThreadsPerChild mean
Apache 2.2
Tomcat 6
Mod_jk 1.2.21
All of them are running on the same box.
I have at any given time around 300 active sessions using the site, and upto
450 at max. Each user on average logs on to the site for around 15 minutes,
and the calls are usually big and slow database or web- service call
10 matches
Mail list logo
