To fix the create tables on startup you will need to use lower case "true".
This is something that has been fixed to ignore the case.
Some of your problems is likely to be the lack of indices on the tables.
Get your Oracle DBA to analyse the queries to determine what indices
will improve performance.
I'd be interested to know the results of this, it is something I've been
meaning to look at for the default configuration files.
I don't know enough about Oracle's Blob implementation to answer your
last question. I'd suggest experimenting with this yourself and report back
Achieved some improvements by followings (so far);
1. Use the combination,
Blob Type as;
and Column Type as;
2. Add indexes on the columns DESTINATION, MESSAGEID and TXID (Top SQL queries uses these).
Note: I could also remove DESTINATION from all the queries (since in my application I have only a single destination, but opted to keep this as generic as possible).
3. Use a separate DB instance for JMS (if your main application is also using DB, use a separate instance).
4. Disable Redo-log (if your DBA agrees).
I also wanted to compare the performance by replacing JBoss queueing with IBM MQ; however the instructions I found on the forums all relate to JBoss 2.x, MQ 5.1 (far different than 3.2.x and 5.3 respectively). Anywhere I can find latest instructions for replacing JBoss-MQ with IBM-MQ would be greatly appreciated.