Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Clearing the XA Recover Log in WebSphere

1,191 views
Skip to first unread message

David Murphy

unread,
Dec 10, 2001, 12:43:59 PM12/10/01
to
Hi - we cannot start the Websphere (4.0) app server since it is trying
to process an XA recovery log for a JTA enabled JDBC driver when it
starts up. It loops forever trying to process the log..

We found the article below but we cannot find the file to
delete:-application_server_nameXAResources in the stated folder.

How do we clear the XA log and have Websphere start up without trying
to process the recovery log.

thx
David M

"When a WebSphere application server starts, the product stores
information about any JTA-enabled data sources used by the server.
This information is needed to recover from server failures. The
information is kept in the file:

product_installation_root/properties/application_server_nameXAResources

Every time the server comes up, the server runtime examines this file
and attempts any needed recovery on the resources described in this
file.

In the event that a JTA-enabled DataSource is configured incorrectly,
you might see server startup failures or warning messages due to the
incorrectly-configured resources.

For example, you might see the warning message:

WTRN0025W: Can not create XAResource object

There is a work-around for this problem, if you are sure that you do
not have other JTA-enabled data sources on this server for which
recovery needs to be driven. You can simply remove the
application_server_nameXAResources file from the properties directory,
correct the configuration error, and attempt to start the server
again. The XAResources file will be re-created when the server
starts."

Sanjay

unread,
Dec 11, 2001, 11:06:07 AM12/11/01
to
Hi David

The way the recovery files were cleared in WAS 3.5 was to remove the
transaction log files in the /WAS_HOME/tranlog directory.

You can backup the transaction logs in this directory and remove the
files and restart the admin server and then the application server.
That should work !!

bye sanjay

David Murphy

unread,
Dec 11, 2001, 9:08:32 PM12/11/01
to
Many thankyou's Sanjay - I will check this out and delete any files in
that directory. Thanks again..

sanjay...@7irene.com (Sanjay) wrote in message news:<fe7d0917.01121...@posting.google.com>...

0 new messages