Check the server.log for [DEBUG] messages. If you see these, then try changing the log threshold to INFO in conf/log4j.xml.
This is interesting, yet to vague to be useful. Could you get a copy of OptimizeIT and run some timing tests? When you figgure out exactaly what is slower post it.
Well, I've tried both suggestions given above.
Bumping the log threshold so that only INFO messages are written to the server log did not make an appreciable difference.
I'm not entirely certain how to interpret the results of running OptimizeIT. After a fair bit of poking around through the profiler snapshots I came across one glaring difference between 3.0 and 2.4. I'm not sure if this is the culprit but it looks like it might be.
During the processing of a request, a call is made to
This method calls
which ultimately calls the desired method on the bean, and
In JBoss 2.4 the percentage of time taken up by these two calls is about 60% and 10%, respectively. In JBoss 3.0, on the other hand, the percentages are about 55% and 30% respectively. It seems that unmarshalling takes considerably longer in 3.0.
Digging a little deeper, I discovered that the unmarshalling process in 3.0 uses a class that does not exist in 2.4:
whose readExternal method takes a whopping 25% of the time required to process the request.
As I said above, I don't know if this is the cause of the performance hit or not but it does look like it to me.
Ok this is very helpful, but definately not a DB issue. I suggest you post your findings to the jboss-dev list, as they are currently working on tuning for the 3.0 release.
please post the command file used to start up JBoss 3.0 with Optimizeit.
Did you get the startup script to start JBoss 3.0 with OptimizeIt?
I have been told that OptimizeIt comes with a JBoss startup script.
OptimizeIt ships with support for JBoss 2.2.4
I tried to modify the JBoss startup script for 3.0 to do the same things, but the JVM crashes with a hotspot error. The JBoss 2.2.4 script used by optimizeIt uses the -classic option and starts the server.
I use JDK1.4.0 with JBoss 3.0 and I can not disable the hotspot compiler here.
If some one has used JBoss 3.0 with optimizeIt, it would be great if you can share your startup script.
Read the manual that came with OptimizeIt! I was able to get JBoss 3.0 working with OptimizeIt! in less than half an hour.