Application server startup hangs when there are problems with the XAResource object
 Technote (FAQ)
 
Problem
Application server startup hangs when problems with the XAResource object are encountered.
 
Cause
The following notes are from the WebSphere® Application Server v3.5 Information Center; however, the information is applicable to v4.0 releases also.

6.6.14.11: Recovering from data source configuration problems using the XAResources file
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 following file:

Install_Root /properties/application_server_nameXAResources

Every time the server starts up, the server runtime examines this file and attempts any needed recovery on the resources described in it. 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 following warning message:

WTRN0025W: Can not create XAResource object

 
Solution
There is a workaround for this problem. If you are sure that you do not have other JTA-enabled data sources on this server for which recovery must be driven, you can remove the application_server_nameXAResources file from the properties directory, correct the configuration error, and attempt to start the server again. The XAResources file is recreated when the server starts.
  1. Backup the following file:

    Install_Root /properties/application_server_nameXAResources

  2. Delete the XAResources file and try to start the server again.
 
Related information
WebSphere 3.5 infocenter XAResource
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s): Windows
Software version: 4.0.7
Software edition:
Reference #: 1175919
IBM Group: Software Group
Modified date: Mar 28, 2006