WebSphere Application Server - Transaction related error during WAS startup

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > September 2005 > Transaction related error during WAS startup





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Transaction related error during WAS startup

2005-09-28, 6:04 pm

The WAS server was throwing an error when I was starting the server.
From the logs, I got the exception as:
WTRN0024E: Inconsistent Transaction and XA Resource recovery logs

I got the solution from the IBM support site which says the following:
Remove the serverName folder under Install-Root/tranlog/ folder.Restart the server.

I tried the above and it worked. So my problem is solved.
I am here to know the reason for this problem. Can any one tell me why this error occured?

Thanks.

Paul Ilechko

2005-09-28, 6:04 pm

rohit1183@yahoo.co.in wrote:
> The WAS server was throwing an error when I was starting the server.
> From the logs, I got the exception as:
> WTRN0024E: Inconsistent Transaction and XA Resource recovery logs
>
> I got the solution from the IBM support site which says the following:
> Remove the serverName folder under Install-Root/tranlog/ folder.Restart the server.
>
> I tried the above and it worked. So my problem is solved.
> I am here to know the reason for this problem. Can any one tell me why this error occured?
>
> Thanks.
>


Are you familiar with the XA protocol for coordinating two-phase commit
updates to multiple resources? If not, I suggest you do some background
reading into the topic.

What seems to have happened here is that your server crashed during a
transaction. This would leave entries in the transaction logs of
WebSphere, which is your transaction coordinator, as well as the logs of
your resource manager(s), typically databases, queueing systems, etc.

At startup, WAS looks at his logs to determine if any in-flight
transactions need to be recovered. in this case, it seems that the
answer was "yes", but when he tried to contact the RM to perform
recovery, the RM did not have a matching log entry. Why this would
happen, I don't know - maybe your DBA cleaned up the database logs?

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com