One of the pretty comprehensive benchmark is XSLTMark
http://www.datapower.com/XSLTMark/
And here is some testing result:
http://www.xml.com/pub/a/2001/03/28/xsltmark/
Looks like XT and Saxon are both significantly faster than Xalan based on
the above benchmark. You can download the test suite f
Also, DataSource is not shared across different VM since DB connection is
bounded to process.
The alternative way is to use JMX connector for DB connection information,
and make a connection to DB to verify it. Here is the code:
import javax.management.ObjectName;
import org.jboss.jmx.interfaces.
Yes, there was memeroy leak (transaction and connection listner object) in
the JBoss JDBC pool implementation before 2.4.5. We were also running out of
memory in the reliability tests, and confirmed the fix in the rerun of the
same tests. Here is the release notes:
http://sourceforge.net/project/s
I don't know a lot about JBoss 3.0, in 2.4, JDBC driver is something you
can't deploy with your ear files if the application uses JBDI based data
source created by JBoss. The driver has to be visible outside the
application. You probably want to copy the driver to JBoss lib/ext directory
instead.
