Technical data

17 Managing JMS
17-32 Administration Guide
Note: JMS persistent stores can increase the amount of memory required during
initialization of WebLogic Server as the number of stored messages increases.
When rebooting WebLogic Server, if initialization fails due to insufficient
memory, 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 and try the reboot again.
If your JMS application uses. . . Perform the following task. . .
Persistent messaging—JDBC Store n If the JDBC database store physically exists on the failed server,
migrate the database to a new server and ensure that the JDBC
connection pool URL attribute reflects the appropriate location
reference.
n If the JDBC database does not physically exist on the failed server,
access to the database has not been impacted, and no changes are
required.
Persistent messaging—File Store Migrate the file to the new server, ensuring that the pathname within the
WebLogic Server home directory is the same as it was on the original
server.
Transactions Migrate the transaction log to the new server by copying all files named
<servername>*.tlog. This can be accomplished by storing the
transaction log files on a dual-ported disk that can be mounted on either
machine, or by manually copying the files.
If the files are located in a different directory on the new server, update
that server’s
TransactionLogFilePrefix server configuration
attribute before starting the new server.
Note: If migrating following a system crash, it is very important that
the transaction log files be available when the server is restarted
at its new location. Otherwise, transactions in the process of
being committed at the time of the crash might not be resolved
correctly, resulting in data inconsistencies.
All uncommitted transactions are rolled back.