APAR
PQ90843 was created to reduce the number of JMS recovery objects that
are stored in the transaction logs and is included in WebSphere® 5.1.1.1
A possible work-around is to do the following:
1. Increase the size of the transaction logs.
Add the size to the transaction log path in the configuration of the
Application Server (server.xml):
transactionLogDirectory=".../tranlog/server_name/transaction;xM"
- Where, x denotes the size of the transaction logs in MB (default = 1
MB).
- server_name denotes name of server defined in your configuration.
- Note that in a cluster you need to change the server.xml file for all
cluster members.
- Note also, transactionLogDirectory entry will be added to the
server.xml if you enter a transaction l log directory through the
Administrative Console, otherwise the there will be no
transactionLogDirectory entry in the server.xml file.
(Servers-> Manage Application Servers-> your_app_server. Config tab)
2. Change the Connection Pool setting for "Aged Timeout" to 0.
Note: The default is 0, but is commonly changed during configuration of an
application. |