Technical data

Configuring JMS
Administration Guide 17-13
Warning: You cannot configure a transaction (XA) connection pool to be used with
a JDBC database store For more information, see “JMS JDBC
Transactions” on page 17-14.
JMS persistent stores can increase the amount of memory required during initialization
of a WebLogic Server instance as the number of stored messages increases. If
initialization fails due to insufficient memory when you are rebooting WebLogic
Server, increase the heap size of the Java Virtual Machine (JVM) proportionally to the
number of messages that are currently stored in the JMS persistent store. Then, try
rebooting the server again. For more information on setting heap sizes, see “Tuning
WebLogic Server Applications” in the WebLogic Performance and Tuning Guide.
For instructions on creating and configuring a store, see “JMS File Stores” and “JMS
JDBC Stores” for information about file and JDBC database stores, respectively, in the
Administration Console Online Help.
About JMS JDBC Stores
Through the use of JDBC, JMS enables you to store persistent messages in a database,
which is accessed through a designated JDBC connection pool. The JMS database can
be any database that is accessible through a JDBC driver. WebLogic JMS detects some
drivers for the following databases:
n Pointbase
n Microsoft SQL (MSSQL) Server
n Oracle
n Sybase
n Cloudscape
n Informix
n IBM DB2
n Times Ten
The weblogic/jms/ddl directory within the weblogic.jar file contains JMS DDL
files for these databases, which are actually text files containing the SQL commands
that create the JMS database tables. To use a different database, simply copy and edit
any one of these
.ddl files.