I don't know much about your specifics but before changing the drivers it's worth checking your JVM memory allocation. Jboss 3.0.4 comes with standard-jboss.xml configured with a bean cache size of 1000000. This will speed things up if you have allocated enough memory to hold the cache but will seriously slow down operations and eventually bring Jboss to a halt with OutOfMemory Errors if you have not.
To allocate memory to the JVM:
For standalone apps:
java "-Xmx256M" javaoptions classpath mainclass
Set the JAVA_OPTS environment variable so it's available to Jboss statup.bat/sh:
This allocates 256Meg with which I found I still needed to cut the cache size down to 100000 beans. This can be done by overriding container configurations for the type of container (ie Standard CMP 2.x EntityBean) in jboss.xml.
Add this to the top of your jboss.xml (This example is for ejb2.x Entity bean - for other container types copy the relevant fragment from standard-jboss.xml and adjust as necessary)
<container-name>Standard CMP 2.x EntityBean</container-name>
<!-- THIS IS THE NUMBER YOU TWEAK -->
<!-- ************************** -->
Hope this helps,
Well, the app doesn't use entity beans, it does use MDBs but the pools size is limited to 25, during the slow down memory is at ~100-110 MB and CPU is at 80%, the following is the line from my start up script JAVA_OPTS="$JAVA_OPTS -Xincgc -Xms64m -Xmx256m -Dprogram.name=$PROGNAME"
so I assume it has room to grow. Thanks for the reply though, I've come across cache size problem before and it can bite you :)